Usable with caveats: it is a licensed, tested, stable client with clear documentation and organization backing. However, the last registry release was about two years ago and the repository has had no commits in the last three months, while security-policy and scanning coverage is limited.
68%
Total Score
88
100
88
80
The package has a history since 2018 with 17 releases, but it has had no release in about two years. That is a meaningful maintenance concern for a client library.
The repository recorded zero commits and zero active maintainers during the last three months. Combined with the roughly two-year-old registry release, this raises concern about responsiveness and future updates.
Composer is used for the build, but no security scanning tools were detected. The missing scanning is a genuine supply-chain hygiene gap, though the small dependency profile reduces its practical exposure.
The repository has no published security policy, leaving vulnerability-reporting and response expectations unclear.
The sole workflow does not declare top-level token permissions. Although no write permissions were explicitly requested, the absence of a restrictive declaration is a workflow-hardening gap.
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.