The project is well documented, tested, licensed, and its workflow has no detected dangerous findings. Its short release history, one registry maintainer, and no commits in the last three months leave maintenance capacity and continuity uncertain.
65%
Total Score
67
100
88
75
Only one account has registry publish access. That is normal for an individually owned project, but it leaves limited visible publishing redundancy.
The package is only 151 days old and has two releases, both recorded on the same day, so there is limited evidence of sustained release maintenance.
The repository recorded zero commits and zero active maintainers during the last three months. For a package this new, that weakens evidence of continued maintenance.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a modest transparency and maintenance gap, not evidence of malicious behavior.
The repository has no security policy file. This makes vulnerability reporting and response expectations less transparent for a library that handles API credentials.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
psr/http-message Version ^1.0 || ^2.0 | — | — |
guzzlehttp/guzzle Version ^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.