Clear documentation, tests, and a matching repository make the client straightforward to inspect and integrate. Its maintenance record is still thin, with only one release and no recent commits, while security policies and scanning are absent.
57%
Total Score
50
81
83
The package has only one release, published 114 days ago, so there is little evidence of sustained maintenance or release reliability. Its young age partly explains the limited history but does not remove the uncertainty.
There were no commits and no active maintainers in the last 3 months, despite the package being about 114 days old. This leaves little evidence of ongoing maintenance after the initial release.
Composer build tooling is present, but no security scanning tools were detected. For a small client this is a transparency gap rather than a severe risk.
The repository has no security policy, so there is no documented process for reporting or handling vulnerabilities. This modestly lowers transparency for a package that sends authenticated API requests.
Version v0.0.1 is not a stable major release, indicating an early API and greater compatibility risk for dependents. No prerelease labeling provides only limited reassurance because the version remains pre-1.0.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
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.