rodneyrehm/plist

Clear licensing, tests, release notes, and a recent release make the package understandable to adopt. Maintenance is currently quiet, and its two workflow actions are unpinned; the missing security policy adds a smaller transparency concern.

Latest v2.0.5

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package is mature, but it has only 6 releases over roughly 14 years and none in the last 12 months. The latest release was published about 19 months ago, so maintenance appears slow.

Repo commit activity

There were no commits and no active maintainers in the last 3 months. Combined with the slow release history, this is a meaningful maintenance concern.

Repo tooling

Composer is used for builds, but no security scanning tools were detected. That reduces automated security assurance, although it is a transparency gap rather than evidence of unsafe code.

Security policy

The repository has no security policy, leaving no stated process for reporting and handling vulnerabilities. This is a modest transparency concern for a library dependency.

Workflow audit

The single workflow was fully analyzed with no dangerous triggers or audit findings, but both of its 2 action references are unpinned. That leaves the build exposed to moving action revisions.