The MIT license and focused TYPO3 template structure make its intended use clear. One registry maintainer, no security scanning, and no issue activity leave little evidence of ongoing support.
38%
Total Score
25
100
75
83
Only one release exists, published nearly five years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk for a package a developer would need to maintain over time.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and leaving no observed sign of current maintenance.
The registry lists one maintainer. A single publisher is a limited support base, especially alongside the absent recent release and commit activity.
Composer is used as the build tool, but no security-scanning tooling is present. This is a transparency and maintenance-hygiene gap, though it is less serious than the lack of recent development.
The linked repository has no security policy. That makes vulnerability reporting and response expectations unclear, adding a modest transparency concern.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
typo3/cms-core Version ^10.4 | — | — |
typo3/cms-fluid-styled-content Version ^10.4 | — | — |
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.