Clear the TYPO3 caches via a queue instead of doing it directly
61%
Total Score
75
100
88
67
A post-autoload-dump install-time script is present. This adds some installation complexity, but the signal does not show that the script is unsafe or unusually broad.
The package has made seven releases since June 2023, but none in the last 12 months and the latest registry release was about 17 months ago. This is meaningful evidence of slowing maintenance for a maintained integration package.
There were no commits and no active maintainers in the last three months. Combined with no registry releases in the last year, this raises abandonment risk, though it does not prove the package is unmaintained.
Composer build tooling is present, but no security-scanning tool was detected. This is a modest transparency and maintenance gap, not a severe dependency risk by itself.
The repository has no security policy. That makes vulnerability reporting less transparent, although the package's small scope and organization ownership partly reduce the concern.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
typo3/cms-core Version ^12.4 || ^13.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.