php-comp/lock

Risky to adopt for new projects: the last release and repository update were over seven years ago, with no recent commits or active maintainers. It is clearly licensed, has a usable README, and is not deprecated or archived, but the long inactivity makes maintenance and compatibility a liability.

Latest v1.1.0

Packagist

42%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had only three releases, with the latest published over seven years ago and no releases in the last 12 months. This is strong evidence of abandonment risk for a dependency.

Repo commit activity

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

Project backing

The linked repository is owned by an organization, which provides some backing context, but organizational ownership does not compensate for the observed absence of recent releases and commits.

Repo issue activity

There are no open issues or pull requests and no recent issue or pull-request activity. This is not inherently unhealthy, but it provides no evidence of active project maintenance.

Repo popularity

The repository has five stars and one fork, indicating a small user and contributor footprint. Popularity is supporting evidence rather than decisive, but the limited adoption provides little compensating maintenance signal.