Usable with caveats: the package is licensed, documented, and backed by a matching organization repository, but it has had only one release about five years ago and no active maintainers or commits in the last three months. Install-time scripts and absent security scanning add operational risk.
58%
Total Score
50
100
81
50
There has been only one release, published about five years ago, with no releases in the last 12 months. This is a substantial maintenance and abandonment concern for a dependency.
The repository recorded zero commits and zero active maintainers in the last three months. Combined with the single-release history, this points to weak ongoing maintenance.
The package runs both post-install-cmd and post-update-cmd scripts. Install-time execution increases dependency-installation risk and deserves review before adoption.
Composer is used for build or packaging, but no security scanning tools were detected. For a small SDK this is a hygiene gap rather than proof of unsafe code.
The repository has no security policy. This weakens transparency around vulnerability reporting, although it is not by itself evidence that the package is unsafe.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
psr/log Version * | — | — |
guzzlehttp/guzzle Version ^6.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.