The package is clearly identified, licensed, documented, and has a small dependency surface with no install-time scripts. Its repository remains unarchived and has tests, but the very old SilverStripe requirement and absent security scanning add maintenance uncertainty.
42%
Total Score
63
100
71
83
The package has had no release in over eight years: its latest release was in April 2018, with none in the last 12 months. This is strong evidence of abandonment risk despite nine historical releases.
There were zero commits and zero active maintainers in the last three months. Combined with the last release being over eight years ago, this materially increases abandonment risk.
Two issues remain open and there has been no issue or pull-request activity in the last month. This is a modest sign of low ongoing attention, but not severe on its own.
The repository uses Composer for builds, which fits the package ecosystem, but no security scanning tools are configured. The missing scanner is a hygiene gap rather than proof of unsafe code.
The repository has no security policy. For a small extension this is a transparency gap, though it is less significant than the long absence of releases and commits.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
silverstripe/cms Version ^3.0 | — | — |
silverstripe/framework 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.