protect access to pages or content elements via frontend groups that are only added when specific access restrictions are matching
58%
Total Score
50
100
94
83
A post-autoload-dump Composer script is present. This is a normal integration point, but it adds install-time behavior that should be understood before deployment.
The registry namespace and repository are owned by the same individual account, so the source linkage is consistent, but there is no observed organization backing to compensate for a small maintainer base.
The latest registry release was in January 2023, with no releases in the following 12 months and only four releases overall. This indicates slow publishing activity, although the linked repository was updated more recently.
There were no commits and no active maintainers in the three months before collection. Combined with the old latest registry release, this raises maintenance and abandonment concerns.
All eight analyzed action references are unpinned, and the auto-approve workflow combines pull_request_target with top-level write permissions and a high-confidence bot-condition finding. The audit completed fully, but this workflow configuration is a meaningful supply-chain hygiene concern.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
typo3/cms-frontend Version ^10.4 || ^11.5 | — | — |
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.