The package is clearly licensed, documented, and has a small runtime dependency set. Pinned workflow actions and broader contributor coverage would make ongoing maintenance safer.
67%
Total Score
50
100
88
50
All recent commits came from one contributor, giving the project a narrow active maintenance base and increasing abandonment risk if that contributor stops.
The repository had 2 commits in the last 3 months, so maintenance is present but relatively light for an actively evolving dependency.
The repository name matches the package, reducing identity concerns, but the README does not mention the package by name, leaving a minor documentation gap.
Composer build tooling is present, but no security scanning tool was detected, leaving a modest transparency and maintenance gap.
Both workflows were analyzed cleanly with no dangerous triggers, untrusted checkouts, or audit findings, but all 4 action references are unpinned, weakening build reproducibility.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
typo3/cms-core Version ^13.0 || ^14.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.