The README, license, and matching repository make setup and ownership clear. The small dependency set and lack of install scripts limit exposure, but the project offers little operational safety tooling.
58%
Total Score
50
100
88
75
Only one registry maintainer is listed, leaving a thin publishing base and increasing continuity risk for an otherwise independently owned project.
The package has had no release in about two years and only three releases overall, which is a meaningful maintenance concern. Its stable v1.0.2 status provides some maturity but does not offset the long inactivity.
There were no commits and no active maintainers in the last three months, consistent with the release history and indicating currently inactive maintenance.
Composer build tooling is present, but no security scanning tools were detected. That weakens automated assurance, though it is a hygiene gap rather than evidence of an unsafe release.
The repository has no security policy, leaving vulnerability reporting and response expectations unspecified. This is a transparency gap for a package handling application validation.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^6.2|^7.2 | — | — |
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.