The repository has no security policy, no security scanning, and only one registry maintainer. The package is small and clearly identified, but its maintenance signals do not support long-term confidence.
45%
Total Score
25
100
81
83
The package has had only two releases, with the latest on January 21, 2019, and none in the following more than seven years. This is strong evidence of abandonment risk despite the stable 1.0.1 version.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history showing no update for more than seven years. The repository is not archived, but that does not compensate for the absent activity.
Only one account has registry publishing access. Because the project is user-owned rather than organization-backed, this leaves limited visible publishing capacity if that maintainer stops supporting it.
Composer is used for builds, but no security scanning tools are present. That reduces automated coverage for dependency or repository issues, adding a modest maintenance concern.
The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This is a transparency gap for a package intended to be integrated into applications.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
silverstripe/framework Version ^4 | — | — |
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.