team-a/lock

The narrow scope, clear README, MIT license, and minimal dependency set reduce adoption friction. Its long inactivity means you may need to maintain fixes and compatibility yourself.

Latest 1.2.1

Packagist

43%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only four releases and none in the last 12 months; its latest release was in December 2020, over five years ago, which is a significant abandonment concern.

Repo commit activity

There were no commits and no active maintainers in the last three months, consistent with several years without a release and indicating strong abandonment risk.

Repo issue activity

There was no issue or pull-request activity in the last month. With no recent commits or releases, this adds to the evidence that maintenance has stopped.

Repo popularity

The repository has only 1 star, 2 forks, and 1 watcher. Low adoption is supporting evidence of limited project maturity, but it is not decisive by itself.

Repo tooling

Composer is used for the build, but no security scanning tools are present. This is a hygiene gap that modestly reduces transparency rather than proving the release is unsafe.