Recent maintenance is thin, with one commit from one contributor in three months, and the workflows use six unpinned actions. The established project backing, regular releases, release notes, tests in the repository, and clean workflow audit offset these concerns.
78%
Total Score
75
100
94
67
All three-month commit activity came from one contributor, creating concentration risk. Organization backing provides some handoff capacity, but no second active contributor is shown in this period.
Only one commit was recorded in the last three months, indicating thin recent maintenance despite the current release activity.
Composer build tooling is present, but no security scanning tool was detected, leaving a modest transparency and maintenance gap.
The repository has no security policy, so the process for reporting and handling vulnerabilities is not documented.
All six workflows were analyzed without audit findings, and five use read-only permissions; however, all six action references are unpinned, weakening build reproducibility and update control. The pull_request_target trigger has no untrusted checkout or script-injection sink.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
silverstripe/framework Version ^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.