skeeks/cms-backend-admin

This is a mature, actively maintained release with a history since 2017, 104 releases, 16 releases in the last 12 months, a stable non-prerelease version, and no registry deprecation. The package is well-scaffolded, licensed, modestly dependent, and backed by a matching organization-owned repository that has recent commits and tests. The main concerns are concentrated maintenance: one contributor made all 16 commits in the last 3 months, the repository has no security scanning or security policy, and its popularity is very low. These issues warrant monitoring and contingency planning, but the recent release and commit activity substantially reduce abandonment risk.

Latest 2.1.1.10

Packagist

82%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo bus factor

One contributor accounts for all 16 commits in the last 3 months, creating a real continuity risk. Organization ownership partly mitigates handoff risk but does not eliminate dependence on the current contributor.

Repo popularity

The repository has zero stars, one fork, and one watcher, so external adoption and community validation are very limited; this is supporting caution rather than evidence of abandonment because releases and commits remain active.

Repo tooling

Composer build tooling is present, but no security-scanning tools are configured. The missing scanning reduces supply-chain transparency, while the package's other structural and activity signals provide partial compensation.

Security policy

The repository has no security policy, leaving vulnerability-reporting and response expectations undocumented. This is a transparency gap, though it does not by itself indicate the package is unsafe to depend on.