The repository clearly matches the package, provides release notes for this version, and has a security policy. Unpinned workflow actions add hygiene risk, while the long release gap limits confidence in ongoing maintenance.
61%
Total Score
67
100
83
100
The package declares GPL-3.0-or-later, but its license file is detected as GPL-2.0. This licensing mismatch creates a real transparency and adoption concern despite the presence of license files in both the artifact and repository.
The package has had four releases since April 2021, but none in the last 12 months; the latest release was in December 2022. This is a meaningful maintenance concern for a dependency tied to an evolving framework.
There were no commits and no active maintainers in the three months measured. Together with the absence of releases in the last 12 months, this points to limited current maintenance capacity.
There are two open issues, but no issues or pull requests were opened or closed in the measured month. This is a modest sign of limited current project activity.
Composer is used for the build, but no security scanning tool was detected. The missing scanner is a hygiene gap rather than evidence that the release is unsafe.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
typo3/cms-core Version ^9.5 || ^10.1 || ^11.5 | — | — |
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.