Clear documentation, tests, licensing, and a small runtime dependency base support adoption. The project has had no releases or commits for more than 11 years, with no security policy and minimal repository activity.
42%
Total Score
50
100
75
75
The latest release was over 11 years ago, and there have been no releases in the last 12 months. This is strong evidence of abandonment for an API client, despite a short early release interval.
The repository recorded zero commits and zero active maintainers in the last 3 months, with its last push in 2015. That leaves compatibility and defect fixes unsupported.
There was no issue or pull-request activity in the last month, and one issue remains open. This reinforces the lack of active maintenance, though the small project size limits how much activity would be expected.
The repository has 2 stars, 0 forks, and 10 watchers, providing little evidence of broad community support or a backup maintainer base. Popularity is supporting evidence rather than a verdict by itself.
The linked repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This matters for a client that handles API credentials and business data.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version 5.2 | — | — |
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.