The package has a clear README, tests, a license, and a small dependency footprint. Its source is identifiable and not archived, but there is no security policy or security scanning.
42%
Total Score
100
64
50
Only two releases were published, with the latest on June 6, 2017 and none in the last 12 months. This is strong evidence of abandonment risk for a dependency released at version 1.0.0.
The repository has zero stars and forks and one watcher. This is weak supporting evidence of limited adoption, though popularity alone does not determine health.
Composer build tooling is present, but no security scanning tools were detected. That is a transparency and maintenance gap, though it is secondary to the long inactivity.
The repository is not archived, which leaves the project technically maintainable, but its last push was also on June 6, 2017 and does not offset the prolonged inactivity.
The repository has no documented security policy. This modestly reduces transparency for a package that integrates with TYPO3, but it is not severe on its own.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
typo3/cms-core Version >8.7.0 || <9 | — | — |
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.