The package is licensed and has a small, clear artifact, but its repository has no security policy or scanning and no recent issue activity. The linked repository does not identify the package in its README, which weakens confidence in provenance.
32%
Total Score
0
60
75
The package has had only two releases, both in January 2016, with no release in roughly 10 years. That strongly indicates abandonment risk for a dependency.
The repository recorded no commits or active maintainers in the last three months, consistent with the long release gap and providing no evidence of current maintenance.
The linked repository name does not match the package name and its README does not mention the package, so the package-to-source relationship is less trustworthy than usual.
Composer is used as the build tool, which fits the package ecosystem, but no security scanning tools are present. The missing scanning is a modest hygiene concern.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a maintenance and transparency gap, though not severe on its own.
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.