lostmilky/locallock

The package is small and has no security policy or automated security scanning. Its MIT license, README, and release notes help, but the source has been inactive for nearly six years, leaving maintenance risk unresolved.

Latest v1.3.0

Packagist

40%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

Only three releases were recorded, all ending in October 2020, with no releases in the last 12 months. That long release gap is strong evidence of abandonment risk.

Repo commit activity

There were no commits and no active maintainers in the last three months, consistent with the nearly six-year release gap and indicating substantial abandonment risk.

Project backing

The repository is owned by the same individual namespace as the package, so the source linkage is coherent. Individual ownership offers less visible organizational backing than an established project, but the signal alone is not severe.

Repo popularity

The repository has only 2 stars, 0 forks, and 1 watcher. Popularity is supporting evidence rather than a verdict, but these figures provide little evidence of a broad support base.

Repo tooling

Composer is used for builds, but no security scanning tools were detected. For a package handling application locking, this is a meaningful maintenance and transparency gap.