Usable with caveats: it has a long release history, frequent recent releases, a stable version, and a matching maintained repository. Adoption carries some maintenance risk because no commits were recorded in the last three months, the project has one publisher, and there is no security policy or scanning.
68%
Total Score
50
100
94
75
One registry account has publish access, which limits publishing redundancy. The matching user-owned repository and recent release activity provide some compensation, but the project remains dependent on one maintainer.
The registry namespace and repository owner match, and the project is clearly user-owned rather than backed by an organization. This supports ownership continuity but offers limited organizational redundancy.
No commits and no active maintainers were recorded in the last three months. Frequent registry releases partly offset this, but the recent source-activity gap is a maintenance concern.
Composer is used as a build tool, but no security scanning tools are configured. This is a transparency and maintenance gap rather than evidence that the package is unsafe.
The repository has no published security policy, leaving vulnerability-reporting expectations unclear.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
typo3/cms-core Version ^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.