The project has a long release history, recent repository activity, tests, documentation, and organization backing. Its single active contributor and weak workflow pinning leave meaningful maintenance and build-integrity concerns.
62%
Total Score
67
100
94
50
A post-autoload-dump lifecycle script runs during installation. This adds execution during dependency setup and warrants care, but the signal does not show a dangerous script or an unusual number of lifecycle hooks.
One contributor made 100% of the five recent commits. Organization backing reduces the risk somewhat, but no second active contributor is visible in this period.
Five commits were made in the last 3 months, showing current activity. However, all recent activity comes from one active maintainer, limiting observable maintenance depth.
Composer is used for builds, but no security-scanning tool was detected. This is a modest supply-chain hygiene gap, not evidence that the package is unsafe by itself.
The repository has no published security policy. That reduces transparency for reporting and handling vulnerabilities, though it does not demonstrate a maintenance failure on its own.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
typo3/cms-core Version ^12.4 || ^13.4 | — | — |
digedag/rn-base Version ~1.20.0 | — | — |
typo3/cms-scheduler Version ^12.4 || ^13.4 | — | — |
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.