The MIT license, readable documentation, tests, and release notes support transparency. Maintenance has stopped, the project has little adoption, and it lacks a security policy, so long-term dependency risk is high.
43%
Total Score
25
75
50
The package has made no release in more than three years, with zero releases in the last 12 months. This is strong evidence of abandonment risk for an API client that may need updates as the service changes.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the absence of recent releases. The repository is not archived, but there is no observed current maintenance.
Only one account has registry publish access, which creates a thin publishing base. The repository is user-owned rather than organization-backed, so there is no provided evidence of broader maintainer capacity to compensate.
The repository has 0 stars, 1 fork, and 0 watchers, providing little evidence of external adoption or community support. Popularity is supporting evidence rather than decisive on its own, but it reinforces the maintenance concern.
The repository has no security policy, leaving vulnerability-reporting and response expectations undocumented. This is a transparency gap, especially for a package that handles authentication and service API access.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
pimple/pimple Version ^3.0 | — | — |
symfony/cache Version ^3.3 || ^4.0 || ^5.0 | — | — |
monolog/monolog Version ^1.23 || ^2.0 | — | — |
psr/simple-cache Version ^1.0 | — | — |
guzzlehttp/guzzle Version ^6.3 || ^7.0 | — | — |
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.