Clear documentation, tests, a changelog, and an explicit license support adoption. The missing security policy and absent security scanning reduce transparency, while the organization-backed repository remains available.
65%
Total Score
75
100
75
50
The artifact includes a license file and the repository also has one, so licensing is documented. The declared GPL-2.0-or-later differs from the detected GPL-2.0 text, creating a minor clarification concern.
The package has 27 releases over nearly 10 years, but no release in nearly three years. That long gap is a meaningful maintenance concern despite its established history.
The repository recorded no commits and no active maintainers in the last three months. This suggests current maintenance has stalled, although the repository is not archived.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning reduces assurance for a package with no recent release activity.
The repository has no security policy, which leaves vulnerability reporting and response expectations unclear. This is a transparency gap, not evidence that the package is unsafe.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
typo3/cms-core Version ^10.4 || ^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.