Documentation, tests, changelog, and release notes are present, and the repository clearly belongs to the package. Organization backing and a recent repository push help, but inactive issue and commit activity, no security policy, and a license mismatch reduce confidence.
58%
Total Score
67
100
79
75
The artifact includes license files and the repository has a license file, but the manifest declares MIT while the detected license is BSD-2-Clause. The mismatch reduces transparency despite the release being licensed.
The package has 29 releases over more than 10 years, but no registry releases in the last four years; this indicates a materially slowing maintenance cadence.
The repository recorded zero commits and zero active maintainers in the last three months. Although it was pushed in September 2024, current development activity is inactive.
There are open issues and pull requests, but none were opened, closed, or merged during the last month. This suggests limited current responsiveness.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a modest supply-chain hygiene gap, not evidence of unsafe code.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
silverstripe/cms Version ^4.0 | — | — |
silverstripe/framework Version ^4.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.