The declared Unlicense conflicts with the Apache-2.0 license file, and the repository has no security policy. A substantial README, tests, Composer metadata, and a non-archived repository provide useful supporting evidence.
54%
Total Score
50
79
75
The package declares the Unlicense, while its included and repository license files are detected as Apache-2.0. The release is licensed, but the mismatch creates avoidable legal and transparency uncertainty.
The repository is owned by an individual account rather than an organization, so there is no organizational backing shown to compensate for the thin maintenance record.
The package has only one release, published about 2 years and 6 months ago, with no releases in the last 12 months. This is meaningful evidence of limited maintenance, though the repository is not archived.
The repository recorded zero commits and zero active maintainers in the last 3 months. Combined with the single historical release, this is a clear abandonment concern.
Composer build tooling is present, supporting reproducible project setup. No security scanning tools are configured, leaving a modest transparency and maintenance gap.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/guzzle Version ^6.2 || ^7.4 | — | — |
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.