Package Health/mralaminahamed/squad-modules-lite-stubs

mralaminahamed/squad-modules-lite-stubs

This is a reasonably healthy, actively maintained stub package with a clear MIT license, complete documentation and changelog, reproducible repository scaffolding, no install-time lifecycle scripts, stable releases, and 19 commits in the last 3 months. The main concerns are that all recent commits come from one contributor, the repository has no security policy or automated security scanning, and two workflows use top-level write permissions; these reduce resilience and security transparency but do not outweigh the evidence of active maintenance and coherent package structure.

Latest v5.1.0

Packagist

78%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry account has publishing access. This is a genuine continuity concern, although repository activity shows that the same apparent owner is actively maintaining the project.

Project backing

The repository is owned by an individual user rather than an organization, so the single-maintainer and bus-factor concerns are not offset by visible organizational backing.

Repo bus factor

One contributor made all 19 commits in the last 3 months, creating a high single-maintainer continuity risk with no demonstrated handoff capacity.

Repo popularity

The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these counters provide little external validation.

Repo tooling

Composer build tooling is used, but no security scanning tools are configured. The build tooling supports maintainability while the missing security automation is a transparency gap.