Package Health/frankdejonge/locked-console-command

frankdejonge/locked-console-command

Risky to adopt for new projects: the package has had no release or repository activity since June 2016. It is not deprecated or archived, and the source repository matches the package, but the long abandonment period makes ongoing compatibility and maintenance uncertain.

Latest 3.1.1

Packagist

45%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was in June 2016, with no releases in the last 12 months. A long period without releases is a substantial abandonment and compatibility risk despite the package having an established release history.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the absence of releases for many years. This strongly reduces confidence that bugs or ecosystem changes will be addressed.

Package scaffolding

The published artifact contains no README, while the repository does contain a README; this weakens the documentation available to consumers installing from Packagist. Missing tests and changelog files in the artifact are normal packaging practice and are not treated as gaps here.

Repository archived

The repository is not archived, which is a positive sign, but its last push was still in June 2016. The unarchived status does not compensate for the observed lack of recent maintenance.

Security policy

No security policy was found in the repository. For a small, old package this is a transparency gap, although the absence of workflows limits the operational security exposure shown by the collected signals.