The package is small, clearly documented, licensed, and has a steady release history. Recent repository inactivity, one maintainer, missing security scanning, and unpinned workflow actions leave meaningful maintenance and build-hygiene concerns.
68%
Total Score
67
100
89
50
Only one account has registry publish access. That is a thin publishing base for continuity, although the repository and package are consistently tied to the same individual.
The repository recorded zero commits and zero active maintainers in the last three months. Although the release history shows recent publishing, the lack of recent source activity lowers confidence in ongoing maintenance.
The repository has no stars, forks, or watchers. This provides little external validation, but popularity is supporting evidence only and does not outweigh the package's release and source signals.
Composer build tooling is present, but no security scanning tools were detected. For a small extension this is a hygiene gap, though it is not evidence of unsafe code by itself.
The repository has no security policy. This weakens vulnerability-reporting transparency, but the package's small scope and otherwise clear source and release history partly limit the concern.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
typo3/cms-core Version ^13.4 || ^14.3 | — | — |
typo3/cms-frontend 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.