The codebase is tiny and the repository matches the package, while Composer is the only runtime dependency. Its maintenance evidence is weak, and the project provides no security policy or automated security scanning, so long-term support and change review remain uncertain.
45%
Total Score
50
100
75
75
Only two releases were published, with the latest in September 2019 and none in the last 12 months. This is strong evidence of an aging package with limited ongoing maintenance.
The repository had no commits and no active maintainers in the last three months, despite the package still being assessed as a dependency. The last push was in February 2022, which weakens confidence in support and fixes.
Composer is used for the build, but no security-scanning tooling is present. The small package scope limits the concern, but the project offers little automated security assurance.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This is a transparency and maintenance gap for an API client.
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.