Tests, a clear README, and release notes provide useful consumer support. The MIT declaration, stable versioning, and non-archived repository are reassuring, but security practices are undocumented.
72%
Total Score
50
100
94
50
Only one registry account can publish the package, leaving limited publishing redundancy. The linked repository is user-owned rather than organization-backed, so no compensating project-backing evidence is present.
The repository recorded zero commits and zero active maintainers in the last three months. A recent release offsets this somewhat, but the lack of current development activity raises maintenance risk.
Composer build tooling is present, but no security-scanning tools were detected. This is a modest transparency and maintenance-process gap rather than evidence that the package is unsafe.
No repository security policy was found, leaving vulnerability reporting and response expectations undocumented. This lowers transparency but is not severe enough to make the release unfit by itself.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
psr/log Version ^1.1 | — | — |
beberlei/assert Version ^3.2 | — | — |
guzzlehttp/guzzle Version ^6.5 | ^7.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.