The MIT declaration, matching source repository, and release notes provide basic transparency. Organization backing and a working Composer build help, but the repository lacks a security policy and security scanning.
42%
Total Score
50
79
50
The package has had only two releases, both in 2017, with no releases in the last 12 months. This is strong evidence of abandonment risk for a library dependency.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the package's long release gap. No provided activity signal compensates for this.
Composer is used for the build, which supports reproducible project setup, but no security scanning tools were detected. That is a modest transparency and maintenance weakness.
The repository has no security policy, reducing clarity about vulnerability reporting and response. This is a hygiene concern, not evidence that the package is malicious.
We didn't find any vulnerabilities for this package.
No direct dependencies.
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.