It has a clear MIT license, a focused dependency set, and an organization-backed repository. No security policy or scanning is present, limiting transparency and confidence in future maintenance.
58%
Total Score
67
100
81
75
Only two releases were published, with the latest in September 2017 and none in the last 12 months. This is substantial evidence of abandonment risk for a library dependency.
The repository had no commits and no active maintainers in the last three months, reinforcing the long release gap and reducing confidence that issues will be addressed.
There were two open issues and one open pull request, but no issues or pull requests were opened or merged in the last month. This supports a picture of limited current activity.
Composer build tooling is present, but no security-scanning tools were detected. The missing scanning is a modest maintenance and transparency concern for a reusable API client.
The repository has no security policy, which leaves vulnerability-reporting and response expectations undocumented. This is a transparency gap, though not evidence of a security incident.
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.