It includes clear documentation, repository tests, a license, and no install-time scripts. Workflow hygiene and the missing security policy add review work.
68%
Total Score
70
100
94
50
Only one account has registry publishing access. That is a modest publishing-capacity concern, and the repository activity confirms the same individual is currently maintaining it.
The repository is owned by an individual rather than an organization, so the single-contributor concentration is not visibly offset by organizational backing.
All 31 recent commits came from one contributor, leaving a high handoff and abandonment risk despite the strong commit volume.
Composer build tooling is present, but no security-scanning tools were detected, leaving a transparency and automated-checking gap.
The repository has no published security policy, so vulnerability reporting and response expectations are not documented.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
typo3/cms-core Version ^13.4.31 || ^14.3.3 | — | — |
typo3/cms-fluid Version ^13.4.31 || ^14.3.3 | — | — |
typo3/cms-backend Version ^13.4.31 || ^14.3.3 | — | — |
typo3/cms-extbase Version ^13.4.31 || ^14.3.3 | — | — |
typo3/cms-install Version ^13.4.31 || ^14.3.3 | — | — |
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.