The stable release, matching repository, clear README, and MIT license make integration straightforward. Maintenance evidence is currently thin, with no release for about 18 months and no commits in the last 3 months; there is also no security policy.
60%
Total Score
50
100
88
75
The registry namespace and repository are owned by the same individual account, giving direct ownership alignment but no organizational backing to offset a thin maintenance base.
The package has 37 releases over roughly 9 years, but none in the last 12 months; the latest release was about 18 months ago, which raises maintenance and abandonment concerns.
There were zero commits and zero active maintainers in the last 3 months, weakening evidence of ongoing maintenance and increasing abandonment risk.
There were no new or closed issues or pull requests in the last month, with four open pull requests; this adds modest concern about project responsiveness.
Composer is used for builds, but no security scanning tools are detected. The missing scanning is a hygiene gap rather than evidence that the release is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
pimple/pimple Version ~3.0 | — | — |
psr/http-message Version ^1.1|^2.0 | — | — |
guzzlehttp/guzzle Version ^6.2|^7.4 | — | — |
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.