Healthy and suitable to depend on, with strong project backing, extensive release history, and clear repository hygiene. Recent repository activity is narrow and the workflows lack consistent permission hardening, so monitor maintenance before adopting it in a critical system.
78%
Total Score
63
100
94
88
All recent repository commits came from one contributor, creating concentration risk. Organization ownership provides some handoff capacity, so this is a caution rather than a severe dependency risk.
Only one commit from one active maintainer was recorded in the last three months, indicating sparse recent development activity despite the recent package release.
There are 17 open issues and 3 open pull requests, but no issues or pull requests were opened or closed in the last month. This suggests limited current interaction and is a maintenance caution, though the recent release history compensates somewhat.
The repository uses Make and Composer for builds, but no security scanning tools were detected. The established build tooling and other repository controls partly compensate for this coverage gap.
Three workflows omit top-level token permissions and one workflow requests top-level write access. This weakens least-privilege transparency even though dangerous workflow patterns were not detected.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
psr/container Version ^1.1 || ^2.0 | — | — |
psr/http-client Version ^1.0.3 | — | — |
psr/http-factory Version ^1.1.0 | — | — |
psr/http-message Version ^1.0.1 || ^2.0.0 | — | — |
laminas/laminas-stdlib Version ^3.19 | — | — |
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.