The repository has one recent contributor and no security policy, leaving limited evidence of ongoing resilience. Clear documentation, an MIT license, organization backing, and a recent repository push provide useful support.
62%
Total Score
67
100
86
75
The package has six releases over about 2 years and 9 months, but none in the last 12 months. That is a meaningful maintenance concern, though the repository was pushed recently.
All recent commit activity comes from one contributor. Organization ownership offers some capacity to hand off maintenance, but no second active contributor is shown.
Only one commit was recorded in the last 3 months, with one active maintainer. The recent activity is positive but too sparse to demonstrate strong ongoing maintenance.
Composer is used as a build tool, which fits the package ecosystem, but no security scanning tools are present. The missing scanning is a modest transparency gap rather than a severe risk.
The repository has no security policy. For a small integration plugin this is a meaningful governance gap, although it does not by itself indicate unsafe code.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
silverstripe/cms Version ^5.1 || ^6.0 | — | — |
silverstripe/framework Version ^5.1 || ^6.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.