Tests, documentation, licensing, and a clean workflow audit provide a solid foundation. The build has no security scanning, and every referenced action is unpinned, leaving avoidable maintenance and workflow-hygiene gaps.
68%
Total Score
67
100
88
67
The package is only 2 days old, despite 10 releases arriving roughly every 39 minutes on median. This shows active initial publishing but provides little evidence of long-term maintenance.
One contributor made all 3 recent commits, concentrating current maintenance responsibility in a single person. With no organizational ownership shown, this raises continuity risk.
Only 3 commits were recorded in the last 3 months, all during this newly published period, so there is not yet enough history to demonstrate sustained maintenance.
Composer is used for the build, but no security-scanning tool was detected. That is a modest process gap rather than evidence of abandonment.
The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities. This is a transparency and maintenance gap for a backend extension.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
typo3/cms-core Version ^13.4 || ^14.3 | — | — |
typo3/cms-fluid Version ^13.4 || ^14.3 | — | — |
georgringer/news Version ^13.0 || ^14.1 | — | — |
typo3/cms-backend Version ^13.4 || ^14.3 | — | — |
typo3/cms-extbase Version ^13.4 || ^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.