Healthy and reasonable to use, with a thin recent contributor base. Frequent releases, an active unarchived repository, clear documentation, and organization backing outweigh the lack of security tooling and the repository's low activity.
78%
Total Score
67
100
89
75
All recent repository activity comes from one contributor, creating a meaningful continuity risk; organization ownership provides some ability to hand maintenance to others but does not remove the current concentration.
Only one commit was recorded in the last 3 months, so source activity is currently sparse despite the strong registry release cadence.
The repository has zero stars and forks and only one watcher. This is supporting evidence of a small project, not a health verdict, and is partly offset by its release history and organization backing.
Composer build tooling is present, but no security-scanning tools were detected, leaving a security-process gap for a project that publishes executable extension code.
The repository has no security policy, so users are given no documented channel or process for reporting vulnerabilities.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
b13/container Version ^3.1.10 || ^3.2.0 || ^4.1.0 | — | — |
typo3/cms-core Version ^12.4 || ^13.0 || ^14.3 | — | — |
wtl/hio-typo3-connector Version ^1.4.0 | — | — |
typo3/cms-fluid-styled-content Version ^12.4 || ^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.