The MIT license, README, tests, and matching source repository provide useful transparency. There is no security policy or scanning, and the project has minimal community activity.
38%
Total Score
50
75
88
The latest release was in April 2017, about nine years ago, and there were no releases in the last 12 months. This is strong evidence that maintenance has stopped.
The repository recorded no commits and no active maintainers in the last three months, reinforcing the long release gap and increasing abandonment risk.
The repository has 0 stars and 1 fork, indicating limited adoption and a small external feedback base. Popularity is supporting evidence rather than a verdict on its own.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning reduces maintenance assurance, though it is not severe on its own.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a transparency gap for a client library.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
rmccue/requests Version ^1.6.1|dev-master | — | — |
tokenly/api-client Version ^1 | — | — |
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.