The package has a clear README, changelog, license, and minimal runtime dependency footprint. Its source is still available and organization-backed, but the package-to-repository relationship is unclear and repository security documentation is thin.
55%
Total Score
75
100
81
75
The latest release was about 7 years ago, with no releases in the last 12 months. This is a meaningful maintenance concern, although the repository is still present and was pushed more recently.
There were no commits or active maintainers in the last 3 months. Combined with the old package release, this raises a substantial abandonment concern.
The repository name does not match the package name and its README does not mention the package. This weakens confidence that the linked repository is specifically the package source, even though a monorepo or module repository could explain the mismatch.
Composer build tooling is present, but no security scanning tooling was detected. This is a modest transparency and maintenance gap rather than evidence of an unsafe release.
The repository has no security policy. For a small SilverStripe module this is a hygiene gap, but it does not by itself show that maintenance has stopped.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
silverstripe/framework Version ^4.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.