A dropdown field for SilverStripe that reflects the main regions in Aotearoa New Zealand
35%
Total Score
unhealthy
Risky: no release or commit activity since 2015 signals strong abandonment risk.
Only two releases were published, both in June 2015, with no release in more than 10 years. This is strong evidence of abandonment for a dependency that may need compatibility maintenance.
The repository had zero commits and zero active maintainers in the past three months, consistent with more than a decade without a release. This materially raises abandonment risk.
The package has one registry maintainer, an individual rather than an organization-backed publishing team. That is not inherently unsafe, but it leaves little visible maintenance capacity alongside the inactive repository.
The repository name matches the package, but its README does not mention the package. This weakens transparency about the repository-to-package relationship, although the name match is compensating evidence.
Composer is used for builds, which fits the package ecosystem, but no security scanning tools are present. For this small package the missing scanning is a hygiene gap rather than a standalone severe risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
silverstripe/cms Version ~3.1 | — | — |
silverstripe/framework Version ~3.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.