Clear documentation, explicit licensing, and a small runtime dependency make adoption straightforward. Repository tests and organization backing help offset the limited recent activity and workflow-security gaps.
72%
Total Score
67
100
94
50
All recent commits came from one contributor. The organization-owned repository provides some handoff capacity, but the observed activity remains concentrated.
Only one commit was recorded in the last 3 months, with one active maintainer. That is limited recent activity and lowers confidence in sustained maintenance.
Composer build tooling is present, but no security-scanning tools were detected. This is a modest transparency and hygiene gap rather than evidence of an unsafe release.
The repository has no security policy. That leaves vulnerability-reporting and response expectations unclear, although it does not by itself indicate abandonment.
The single workflow was fully analyzed with no high- or medium-confidence findings and no untrusted checkout or script-injection sinks. However, its one action reference is unpinned, which weakens build reproducibility.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
typo3/cms-core Version ^13.4.8 | — | — |
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.