The project has a long release history and a stable major version. Its repository shows no commits or active maintainers in the last three months, and it has no security policy or scanning.
62%
Total Score
50
88
67
The repository recorded zero commits and zero active maintainers in the last three months. That is concrete evidence of slowing maintenance and raises abandonment risk despite the recent release.
The package runs a post-autoload-dump lifecycle script. This adds install-time behavior that should be understood before adoption, but the signal does not show a dangerous action by itself.
The package has been released since 2019 with 36 releases, but only one release appeared in the last 12 months. The recent release keeps this from being a severe concern, though the cadence is now slow.
Composer build tooling is present, but no security-scanning tooling was detected. This is a modest transparency and maintenance gap, not evidence that the package is unsafe.
The repository has no security policy. That makes vulnerability reporting and response expectations less clear, lowering maintenance transparency.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
typo3/cms-core Version ^11.5 || ^12.4 | — | — |
typo3/cms-install Version ^11.5 || ^12.4 | — | — |
typo3/cms-scheduler Version ^11.5 || ^12.4 | — | — |
sjbr/static-info-tables Version * | — | — |
localizationteam/l10nmgr Version ^12.2 | — | — |
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.