Its README, MIT licensing, and package-to-repository match make the small library understandable to adopt. However, the project has had no release or commit activity for about seven years, and it lacks tests and security scanning.
42%
Total Score
0
100
75
50
The package has only one release, published about seven years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk despite the package remaining non-deprecated.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and indicating no current maintenance capacity.
Composer build tooling is present, but no security scanning tools were found. This is a modest transparency and maintenance concern, especially for a project with no recent activity.
The repository is not archived, which avoids an explicit abandonment marker, but its last push was about seven years ago and does not offset the inactivity shown by release_history and repo_commit_activity.
The repository has no security policy. For a small, inactive library this leaves vulnerability-reporting expectations unclear, though it is not severe on its own.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ~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.