The repository is active and unarchived, the package includes substantial documentation and release notes, and it has no install-time scripts. A single maintainer, no recorded commit activity beyond initial publication, and no security policy leave longer-term support unproven.
72%
Total Score
50
100
86
75
One registry maintainer account is responsible for publishing. That is a thin publishing base for a production extension, although the repository ownership is aligned with the same account.
Only two releases appeared within about one day, so there is not enough history to demonstrate sustained maintenance. The recent second release is a small positive but does not establish durability.
There were no commits or active maintainers in the last three months. Because the repository and package are only about one day old, this primarily means maintenance history is unproven rather than demonstrating abandonment.
Composer build tooling is present, but no security scanning tool was detected. This is a modest transparency and hygiene gap, not evidence that the release is unsafe.
The linked repository has no security policy. That leaves vulnerability reporting and response expectations unclear for a package intended to run in TYPO3 applications.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
typo3/cms-core Version ^13.4 || ^14.0 | — | — |
typo3/cms-fluid Version ^13.4 || ^14.0 | — | — |
typo3/cms-backend Version ^13.4 || ^14.0 | — | — |
typo3/cms-extbase Version ^13.4 || ^14.0 | — | — |
typo3/cms-frontend Version ^13.4 || ^14.0 | — | — |
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.