The package is narrowly scoped, has a usable README, a declared BSD license, and only one runtime dependency. The repository has no security policy, and its README does not identify the package, making ownership and future support harder to verify.
42%
Total Score
25
100
79
75
The latest release was published in August 2017, with no releases in the last 12 months and only three releases overall. This is strong evidence of abandonment risk for a dependency.
The repository had zero commits and zero active maintainers in the last three months, while its last recorded push was in November 2019. That long inactivity materially lowers confidence in ongoing maintenance.
Three issues and two pull requests remain open, with no new or closed activity in the last month. This supports the broader indication that project support has stalled.
The repository name does not match the package name and its README does not mention the package. Although this can occur with sub-packages, the available evidence makes package ownership harder to verify.
The repository has no published security policy. This is a transparency and vulnerability-reporting gap, though it does not by itself show that the package is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
silverstripe/cms Version ^3.0 | — | — |
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.