The repository matches the package and contains tests and a changelog; licensing is clearly documented. A single registry maintainer and no security policy leave less evidence of long-term support.
63%
Total Score
50
88
75
Only one account has registry publishing access, creating a limited publishing base. This is a caution rather than a severe risk because repository ownership and package identity match.
The repository recorded zero commits and zero active maintainers in the last three months. That weakens evidence of active maintenance, although the recent registry release partially offsets it.
The repository has zero stars, forks, and watchers, so there is little public adoption evidence. Popularity is supporting evidence only, and the package's release history and repository structure provide some compensation.
The repository uses Make and Composer for builds, but no security-scanning tools were detected. This is a modest transparency and maintenance gap, not evidence that the package is unsafe.
The repository has no SECURITY.md or other detected security policy, leaving vulnerability reporting and response practices unclear.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
guzzlehttp/psr7 Version ~1.0 | — | — |
guzzlehttp/guzzle Version ~6.0 | — | — |
guzzlehttp/promises Version ^1.1 | — | — |
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.