Add tagging to notifications going out of a Silverstripe project
72%
Total Score
caution
Recent maintenance and organization backing are offset by unpinned workflow actions, no security policy, and a single active contributor.
All 7 recent commits came from one contributor, leaving maintenance dependent on a single active developer despite the project's organizational ownership.
Composer build tooling is present, but no security-scanning tool was detected, leaving security-process coverage limited.
The repository has no security policy, reducing transparency about how vulnerabilities should be reported and handled.
The single workflow was fully audited with no dangerous triggers or audit findings, but both of its 2 action references are unpinned, weakening build reproducibility.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
silverstripe/tagfield Version ^4 | — | — |
silverstripe/taxonomy Version ^4 | — | — |
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.