A clear README, tests, and matching BSD-3-Clause licensing improve transparency. The project has no security policy or automated security scanning, making future issue response less visible.
44%
Total Score
50
88
75
Only one registry account has publish access. That can be normal for a small personal project, but it leaves little visible publishing redundancy alongside the absence of recent activity.
The latest release was in December 2020, with no releases in the last 12 months and only four releases overall. This is a substantial maintenance concern for a library integration.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and raising abandonment risk.
Composer and Phing provide build tooling, which is positive, but no security-scanning tools were detected. The missing scanning is a modest hygiene concern.
The repository has no security policy, so users are given no documented reporting or response process. This is a transparency and maintenance gap, though not a standalone supply-chain verdict.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| 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.