Patch Lifecycle Manager

I Use This!

Inactive

Analyzed 6 days ago. based on code collected 8 days ago.

Project Summary

The Patch Lifecycle Manager (PLM) provides a central point for tracking the lifecycle of patches against a source tree. Regardless of the RCS type system used by the developer to track development of the patch (CVS, Subversion, BitKeeper, or by hand...)

In a Nutshell, Patch Lifecycle Manager...

...
has had 376 commits made by 4 contributors
representing 18,858 lines of code
...
is mostly written in Perl
with a low number of source code comments
...
has a codebase with a long source history
maintained by nobody
with stable Y-O-Y commits
...
took an estimated 5 years of effort (COCOMO model)
starting with its first commit in October, 2002
ending with its most recent commit over 18 years ago

Quick Reference

Homepage

(2 Locations)

Become the first manager for Patch Lifecycle Manager

Project Security

Vulnerabilities per Version ( last 10 releases )

There are no reported vulnerabilities

Project Vulnerability Report

Security Confidence Index

Poor security track-record

Favorable security track-record

Vulnerability Exposure Index

Many reported vulnerabilities

Few reported vulnerabilities

About Project Vulnerability Report

Did You Know...

...
nearly 1 in 3 companies have no process for identifying, tracking, or remediating known open source vulnerabilities
...
by exploring contributors within projects, you can view details on every commit they have made to that project
...
use of OSS increased in 65% of companies in 2016
...
you can embed statistics from Open Hub on your site

About Project Security