Clear documentation and a small dependency surface make the package understandable to adopt. Its one-person ownership and complete lack of activity since April 2022 leave maintenance and compatibility risks unresolved.
45%
Total Score
38
100
72
83
The package has only one release, published about 4 years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk for a library intended for ongoing server integrations.
The repository recorded zero commits and zero active maintainers in the last 3 months, matching the long release gap. No provided maintenance signal compensates for this inactivity.
One registry maintainer limits the observable publishing base and increases the risk that maintenance stops if that person becomes unavailable. The linked repository is user-owned rather than organization-backed, so there is no provided backing evidence to offset it.
The repository is owned by an individual user account, not an organization. Combined with one registry maintainer and no recent activity, this provides little evidence of durable project backing.
There are no open issues or pull requests and no recent issue or pull request activity. While a quiet issue tracker is not inherently negative, it offers no evidence of ongoing maintenance.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
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.