The MIT license, tiny dependency surface, release notes, and matching repository make the package easy to inspect. Its single-author project has no visible security policy and shows little support for a very old API client.
38%
Total Score
0
100
71
50
Only two releases exist, with none in the last 12 months; the latest release was published in April 2017, about 9 years ago. This is strong evidence of abandonment risk for a client library.
The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with the package's long release hiatus. No provided activity signal shows ongoing maintenance.
Composer is used for the build, but no security scanning tool was detected. The small codebase limits the significance of this gap, though it provides little evidence of active security maintenance.
The repository has no security policy, reducing transparency about vulnerability reporting and response. This matters more for an API client handling authentication tokens.
Version v0.2.0 is not a prerelease, but it remains below 1.0, so the API may be less mature or stable than a major release. The long period without newer versions makes this a secondary concern.
We didn't find any vulnerabilities for this package.
No direct dependencies.
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.