The README, MIT declaration, and package-to-repository match make the package easy to understand. Its small dependency set is reasonable, but the project lacks tests, security scanning, and a security policy.
42%
Total Score
25
100
75
50
This package has only one release, published about 4 years ago, with no releases in the last 12 months. That provides strong evidence of abandonment risk for a library dependency.
The repository recorded 0 commits and 0 active maintainers in the last 3 months, consistent with the package's long release gap and indicating no recent maintenance capacity.
Only one registry maintainer is listed. A single-person project can be healthy, but here it increases continuity risk alongside the absence of recent activity.
Composer build tooling is present, but no security scanning tools were detected. That weakens automated oversight for a package intended to manage infrastructure resources.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This is a transparency gap, although it is less severe than the maintenance concerns.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
ramsey/uuid Version ^4.2 | — | — |
guzzlehttp/guzzle Version ^7.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.