The small project has basic tests, a clear MIT license, and no install-time scripts. Its maintenance record is still thin, and the README contains placeholder package names and examples that reduce confidence in integration quality.
55%
Total Score
0
100
69
75
The repository recorded zero commits and zero active maintainers during the last three months. Combined with the short release history, this is evidence of stalled maintenance.
The package includes a README and tests, and the repository also has tests and uses GitHub Releases. The README's placeholder installation and namespace examples weaken its value for consumers, while the missing changelog is not a concern because release notes are not required in the package artifact.
Only two releases were published, both on the same day, and there have been no further releases over roughly seven and a half months. That is a limited maturity and maintenance record for a library.
The repository name matches the package, but the README does not mention the package name. That mismatch raises some uncertainty about how clearly the repository documents this published package.
Composer is used for the build, but no security scanning tooling is present. This is a modest transparency and maintenance gap rather than evidence that the package is unsafe.
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.