Healthy and suitable to use, with a small maintenance and security-hygiene caveat. It has frequent releases, current repository activity, tests, documentation, and organization backing, but recent commits come from one contributor and the workflows lack explicit token permissions and security scanning.
82%
Total Score
75
100
94
80
All three recent commits came from one contributor, creating continuity risk; organization ownership provides some ability to hand maintenance off, but no second active contributor is shown.
The repository received three commits in the last three months from one active maintainer, confirming recent work but showing a relatively thin maintenance capacity.
Composer build tooling is present, but no security scanning tools were detected, leaving a genuine security-hygiene gap for a package with release automation.
The repository has no security policy, reducing transparency about how vulnerabilities should be reported and handled.
All three workflows lack top-level token permission declarations. Although none declares top-level write access, explicit least-privilege permissions would provide stronger workflow hygiene.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
typo3/cms-core Version ^12.4 || ^13.0 || ^14.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.