The package is licensed, documented, and backed by repository tests and a changelog. Its tiny audience and single publisher reduce confidence that future fixes will arrive, while the repository identity does not clearly match the package.
43%
Total Score
33
100
72
75
The latest release was on May 2, 2018, and there have been no releases in the last 12 months. A package first released in 2016 with only eight releases now shows substantial abandonment risk.
The repository recorded zero commits and zero active maintainers in the last three months, after last being pushed in 2018. This is strong evidence that fixes and compatibility updates are unlikely.
Only one account has registry publish access. That is a limited publishing base for a user-owned project and increases continuity risk, although access records alone do not establish actual maintenance activity.
There are no new issues or pull requests in the last month, no merged pull requests, and four open pull requests. This provides no evidence of current community maintenance.
The repository name does not match the package name and its README does not mention the exact package. Although subpackages can use different names, both indicators together leave uncertainty about whether this repository is the intended source.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
silverstripe/cms Version ~3.6 | — | — |
silverstripe/framework Version ~3.6 | — | — |
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.