The repository has no security policy or automated security scanning, which weakens project hygiene. Clear licensing, substantial documentation, and release notes provide useful transparency despite the small project footprint.
58%
Total Score
50
80
50
Only one registry maintainer is listed, so the publishing base is thin. The linked repository is also owned by an individual, with no organizational backing shown to compensate for that concentration.
The package has made no releases in the last 12 months, and its latest release was on August 27, 2022. Earlier releases were regular enough to show prior maintenance, but the multi-year pause raises abandonment risk.
The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with the release gap. This indicates that maintenance capacity is currently inactive.
Composer build tooling is present, but no security scanning tools were detected. The build setup is appropriate, while the missing security automation is a modest hygiene weakness.
The repository has no security policy. This is a transparency and maintenance-process gap, though it does not by itself show that the package is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version >=6.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.