The long release history and current 7.0.0 release provide useful continuity. Maintenance is concentrated in one contributor, and all six workflow actions are unpinned, while organization backing and complete audit coverage reduce the concern.
78%
Total Score
88
100
94
83
All six recent commits came from one contributor, so maintenance capacity is concentrated and continuity depends heavily on that person. Organization backing provides some handoff capacity but no second active contributor is shown.
Composer build tooling is present, but no security-scanning tooling was detected. The missing scanning layer is a modest transparency and maintenance gap, not evidence of unsafe code.
The repository has no security policy. That weakens the project's documented vulnerability-reporting process, although it does not indicate abandonment on its own.
The sole workflow was fully analyzed with no untrusted checkout, injection, or audit findings, and it has no top-level write permissions. However, all six action references are unpinned, leaving builds exposed to action changes over time.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
psr/container Version ^2.0 | — | — |
nikic/fast-route Version ^1.3 | — | — |
psr/http-factory Version ^1.0 | — | — |
psr/http-message Version ^2.0 | — | — |
psr/simple-cache Version ^3.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.