Stable packaging, a maintained repository, and organization ownership support continued use. The small recent contributor base, absent security policy, and unpinned workflow actions leave meaningful maintenance and build-hygiene concerns.
72%
Total Score
67
100
88
67
The package has existed for about four years and published one release in the last 12 months, with a median interval of about 131 days; this indicates deliberate but modest maintenance cadence.
All two recent commits came from one contributor, leaving the recent maintenance path concentrated despite the repository being owned by an organization.
There were two commits in the last three months, showing recent activity but only a light maintenance pace.
Composer build tooling is present, but no security scanning tools were detected, leaving a modest verification gap.
The repository has no security policy, reducing transparency for vulnerability reporting and response expectations.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
typo3/cms-core Version ^11.5 || ^12.0 || ^13.0 || ^14.0 || 14.*.*@dev | — | — |
typo3/cms-backend Version ^11.5 || ^12.0 || ^13.0 || ^14.0 || 14.*.*@dev | — | — |
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.