Documentation is present and the dependency surface is small. The source remains identifiable and unarchived, but there is no security policy or automated security scanning.
58%
Total Score
50
100
75
83
The latest registry release was published nearly six years ago, with no releases in the last 12 months and only four releases overall. This materially raises abandonment and compatibility risk despite the repository being updated later.
The repository had no commits and no active maintainers in the last three months. A push in November 2024 shows it is not archived, but current development activity is still absent.
Composer is used for the build, but no security-scanning tooling was detected. That reduces evidence of ongoing vulnerability hygiene without proving a security defect.
The linked repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a transparency gap, though it does not by itself show unsafe code.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
curl/curl Version ^1.6 | — | — |
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.