Strong documentation, tests, licensing, and organization backing reduce adoption friction. The small dependency surface and recent release history are reassuring.
72%
Total Score
67
100
94
67
One contributor made all commits in the last 3 months, creating a concentrated maintenance risk. Organization ownership provides some handoff capacity, but no second recent contributor is shown.
Only two commits were made in the last 3 months by one active maintainer. Recent activity is present, but the low volume leaves some concern about maintenance capacity.
Composer is used for builds, but no security scanning tool was detected. For a small library this is a hygiene gap rather than evidence of abandonment.
The repository has no security policy. This reduces disclosure transparency, although it does not by itself indicate that the package is unsafe to depend on.
All three workflows were analyzed with no injection or high-severity findings, and one scopes permissions at job level. However, 7 of 9 action references are unpinned, which weakens build reproducibility and action supply-chain hygiene.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
horde/argv Version ^3 || dev-FRAMEWORK_6_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.