ernestdefoe/garrison

Usable with caveats: the release is licensed, documented, tested, and actively being published, but the project is only one day old and has no recorded three-month commit activity or community adoption. Treat it as an early-stage dependency until a longer maintenance track record emerges.

Latest v1.3.0

Packagist

64%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health checks

Release history

The package is only 1 day old, with 9 releases compressed into roughly 25 hours. That shows active initial development but provides almost no long-term maintenance evidence.

Repo commit activity

No commits or active maintainers were recorded in the preceding 3 months. Because the repository is only 1 day old, this mainly reflects insufficient history rather than demonstrated abandonment, but it remains a material maturity gap.

Repo popularity

The repository has zero stars, forks, and watchers. A new package need not be popular, but these counters provide no external adoption or community support evidence.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. This is a modest supply-chain transparency gap, partly offset by the repository's CI and other workflow checks.

Security policy

The repository has no SECURITY.md or other detected security policy. That weakens vulnerability-reporting transparency, though it is not by itself evidence that the release is unsafe.