The small codebase is clearly identified, licensed, and has a focused dependency set without install-time scripts. It lacks tests and a security policy, leaving little evidence to offset its age.
48%
Total Score
64
50
Only two releases were published, both about five years ago, with no releases in the last 12 months. This is strong evidence of abandonment for a library that may need API and platform updates.
The project uses Composer, but no security-scanning tools were detected. For a small package this is a modest hygiene gap, and it does not outweigh the maintenance evidence by itself.
The repository is not archived, but its last push was about five years ago, matching the stale registry history. The lack of archival status is a small compensating signal, not evidence of active maintenance.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This is a transparency gap, though it is less severe than the long maintenance pause.
Version 0.1.1 is not a stable major release, so the API may still be immature or subject to breaking changes. The absence of prereleases does not compensate for the very limited release history.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^7.3 | — | — |
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.