Documentation and licensing are clear, and the organization-owned repository matches the package. All five workflow actions are unpinned, with a high-confidence template-injection finding, while maintenance activity has stopped. The release remains stable and non-deprecated, but adoption carries maintenance risk.
58%
Total Score
50
100
75
67
The package has had no registry release in roughly three years, and there were no releases in the last 12 months despite a previously regular median interval of about 83 days. This is strong evidence of stalled maintenance.
There were zero commits and zero active maintainers in the last three months. Combined with the long release gap, this indicates current maintenance capacity is weak.
Composer build tooling is present, but no security scanning tools were detected. This is a modest transparency and maintenance-hygiene gap rather than evidence that the package is unsafe.
The repository is not archived, but its last push was in June 2024, which only partly offsets the absence of recent releases and commits.
The repository has no security policy, leaving vulnerability-reporting expectations unclear. This lowers transparency, although the organization-owned project backing provides some context.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
typo3/cms-core Version ^10.4 || ^11.0 || ^12.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.