TYPO3 FrankenPHP integration
76%
Total Score
healthy
A very new package with solid project structure but no established maintenance track record
Only one registry publishing account is listed, and the repository owner is an individual rather than an organization. That is a limited publishing and succession base, although it is not evidence of abandonment by itself.
The package is less than 1 day old with only 2 releases, so it has no established release track record yet. The rapid second release shows active initial publishing but does not demonstrate long-term maintenance.
There were 0 commits and 0 active maintainers in the last 3 months, but the repository was pushed on the assessment date and the package is less than 1 day old. The short age explains the missing history, while leaving long-term maintenance unproven.
Composer build tooling is present, but no security-scanning tools are shown. This is a modest transparency gap for a new package, not evidence of unsafe code.
No GitHub Actions workflows were present to audit, so there are no workflow findings; this also provides no evidence of automated CI or release safeguards.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
typo3/cms-core Version ^13.4 || ^14.0 | — | — |
typo3/cms-backend 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.