beatswitch/lock

The codebase still has tests, a matching organization-owned repository, and a clear MIT license. However, the last release was over 10 years ago and the repository has had no commits or issue activity for over 8 years, so this legacy dependency carries abandonment risk.

Latest 0.2.0

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had no release in over 10 years, with zero releases in the last 12 months; its short historical release run does not offset this prolonged inactivity.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with the last push being over 8 years ago and indicating serious abandonment risk.

Repo issue activity

There were no new or closed issues or pull requests in the last month, while 20 issues and 3 pull requests remain open; this supports the conclusion that maintenance has stalled.

Repository archived

The linked repository is not archived, which is a positive sign, but its last push over 8 years ago shows that this status does not imply active maintenance.

Security policy

The repository has no security policy, leaving vulnerability-reporting expectations undocumented; this is a secondary transparency gap beside the much larger maintenance concern.