The MIT license, release notes, and Composer build support basic transparency. The missing security policy and absent security scanning reduce assurance for a package that has seen no recent project activity.
35%
Total Score
0
71
83
This package has only one release, published about 10 years ago, with no releases in the last 12 months. That strongly indicates abandonment risk, although it is not marked deprecated.
The repository has had zero commits and zero active maintainers in the last three months, consistent with the last push being about 10 years ago. No provided maintenance signal compensates for this inactivity.
The repository name matches the package, reducing the risk of an unrelated repository being used. The package name is not mentioned in the README, leaving a minor documentation gap.
Composer build tooling is present, but no security-scanning tools are configured. For an otherwise long-inactive project, that leaves an additional maintenance and assurance gap.
The repository has no security policy, which weakens vulnerability-reporting transparency. This is a supporting concern rather than evidence that the package is unsafe by itself.
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.