msp/phpids

The codebase is small and easy to inspect, with a declared license and a clean dependency setup. Its last release and repository activity were about nine years ago, with no security policy or scanning, so maintenance risk is substantial.

Latest 1.0.2

Packagist

40%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had no release in about nine years; only three releases exist, all clustered in 2017. This strongly raises abandonment risk despite the short early release interval.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and indicating no observed ongoing maintenance.

Repo popularity

The repository has only 3 stars and 1 fork, providing little supporting evidence of broad community review or shared maintenance. Low popularity alone is not decisive, but it does not compensate for inactivity.

Repo tooling

Composer is used for builds, which is appropriate, but no security scanning tool is configured. For a security-oriented component, that is a meaningful transparency and maintenance gap.

Security policy

The linked repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This adds a modest transparency concern alongside the stale activity.