The package has a short README, a release note, and a matching source repository, but its maintenance evidence is very old. The license files disagree, and the repository has no security policy or scanning tools.
32%
Total Score
0
71
75
The package has only two releases, with the latest activity in February 2018 and no releases in the last 12 months. This is strong evidence of abandonment risk for a dependency.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history showing no recent maintenance.
The artifact declares MIT, but its detected LICENSE file is Apache-2.0; the repository also has a license file, so this is a concrete licensing inconsistency rather than an absent-license problem.
Composer is used as a build tool, but no security scanning tools are present. That weakens supply-chain hygiene without proving the release is unsafe.
The linked repository has no security policy. This is a transparency gap, though the small six-file project and its long inactivity make it secondary to the maintenance risk.
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.