Some minor silverstripe tweaks that I use repeatedly on projects
42%
Total Score
33
100
63
75
The latest release was published in May 2016, and there have been no releases in more than 10 years. That strongly raises abandonment and compatibility risk for a framework extension.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with a project that has been inactive for years.
The registry lists one maintainer. That is a narrow support base for an already inactive package and increases bus-factor risk.
There are three open pull requests, but no new or merged pull requests in the last month, suggesting that outstanding maintenance work is not being addressed.
The repository name matches the package, but its README does not mention the package name. That creates some uncertainty about package ownership or documentation linkage.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
silverstripe/cms Version >=3.1 | — | — |
silverstripe/framework Version >=3.1 | — | — |
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.