The project is small and has limited operational oversight. Recent release documentation and repository tests provide useful context, but ongoing maintenance is harder to verify.
68%
Total Score
75
100
83
83
The package has existed for about 5 years and 8 months with 10 releases, but only one release in the last 12 months. The current release provides some evidence of continued publishing, while the recent cadence remains sparse.
No commits and no active maintainers were recorded in the last three months. The same-day release and repository push provide some compensation, but sustained maintenance activity is not demonstrated.
The repository has 3 stars, 0 forks, and 1 watcher, indicating a small user and contributor footprint. This is supporting context rather than a decisive health problem because the project is focused and maintained under an organization.
Composer build tooling is present, but no security-scanning tool was detected. This is a modest oversight gap rather than evidence that the package is unsafe.
The repository has no security policy, so its process for receiving and disclosing security issues is unclear.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
psr/container Version ^1.1|^2.0 | — | — |
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.