The repository has no security policy or automated security scanning, while its MIT licensing, README, and stable release are clear. Its small dependency surface and lack of install-time scripts reduce adoption friction.
57%
Total Score
50
100
75
75
The package has 28 releases and a historical median interval of about 13 days, but its latest release was over four years ago and there were no releases in the last 12 months. This strongly lowers confidence in ongoing maintenance.
The repository recorded zero commits and zero active maintainers during the last three months, consistent with the release gap. The repository is not archived, but current maintenance activity is absent.
Composer build tooling is present, but no security scanning tools were detected. The missing automated security checks add a modest maintenance concern for a package handling API authentication and credentials.
The repository has no documented security policy, leaving no clear process for reporting or handling vulnerabilities. This is a transparency and maintenance gap, though it does not by itself make the package unfit.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
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.