Package Health/devsavage/slim4-authentication

devsavage/slim4-authentication

Risky to adopt: the package appears effectively dormant, with no release or commit activity for nearly two years. It is correctly linked, licensed, and documented, but its unfinished status, lack of tests, and missing security process add maintenance risk.

Latest 0.2.0

Packagist

40%

Total Score

Maintainer Stability

Dependencies

Maturity

Supply Chain

Health Score Breakdown

Repo commit activity

There were zero commits and zero active maintainers in the last three months, consistent with the nearly two-year release gap. This is strong evidence of abandonment risk.

Dependency profile

Nineteen runtime dependencies create a broad maintenance and compatibility surface for a small, early-stage authentication package. The dependency list is visible, but the package's long-term inactivity makes keeping that surface current less credible.

Package scaffolding

The package includes a readable README and release notes for version 0.2.0, which improves transparency. The README describes the project as still in development; the absence of published tests is normal for an artifact, but the repository also reports no tests.

Release history

The package has only three releases and none in the last 12 months; its latest release was nearly two years ago. This is a meaningful maintenance concern for an authentication package.

Repo tooling

Composer build tooling is present, but the repository has no security scanning tools. For authentication software, that is a meaningful transparency and maintenance gap.