Documentation, tests, and licensing support integration, while the project has no security policy and limited public backing. The package is stable but appears effectively inactive, so pinning this release carries maintenance risk.
52%
Total Score
0
75
75
The package has only one release, published about 11 years ago, with no releases in the last 12 months. This is strong evidence of limited ongoing maintenance, although the release is stable rather than experimental.
There were no commits and no active maintainers in the last three months, consistent with a repository whose last push was about six years ago. This materially raises abandonment risk.
The repository name does not match the package name and its README does not mention the package. Although this can occur with older packaging arrangements, the linkage is less transparent and warrants caution.
The repository uses Composer, but no security scanning tools were detected. The missing scanning is a modest supply-chain hygiene gap, not evidence that the package is unsafe.
No security policy was found in the repository. For a library, this weakens vulnerability-reporting transparency, though it does not by itself show poor code quality.
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.