The codebase is very small and has no tests or security policy, which limits confidence for a client handling API credentials. Organization backing, a clear README, an MIT license, and release notes provide useful transparency, but maintenance history is still too short to establish durability.
62%
Total Score
75
79
75
The package is 165 days old and has only one release, so there is little release history to demonstrate sustained maintenance.
There were no commits and no active maintainers in the last three months, while the only recorded push coincides with the initial release; this leaves ongoing maintenance unproven.
Composer build tooling is present, but no security scanning tool was detected, leaving a modest repository hygiene gap for a client that handles credentials.
The repository has no security policy, so there is no documented reporting path for vulnerabilities or credential-handling issues.
Version v0.1.1 is below 1.0, indicating an early-stage API that may change incompatibly even though it is not marked as a prerelease.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^7.10 | — | — |
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.