A clear README, release notes, license, and matching source tree make the package straightforward to evaluate and integrate. Its single release and no observed commits leave maintenance continuity unproven, while the repository has no security policy or automated security scanning.
68%
Total Score
50
100
86
88
The registry namespace and repository are owned by the same individual account, providing consistent ownership context. A single-user owner also means the project has no demonstrated organizational backing or maintainer redundancy.
This is the package's first release, published today, so there is no release history or cadence to demonstrate sustained maintenance. That is a meaningful maturity gap, but not evidence of abandonment for a brand-new package.
No commits or active maintainers were observed in the last three months. Because the repository was created and released today, this is inconclusive rather than proof of abandonment, but continued maintenance is not established.
Composer build tooling is present, showing the project has a defined build ecosystem. No security scanning tools were detected, leaving a modest repository-hygiene gap.
The repository has no security policy, so there is no published process for reporting or handling vulnerabilities. This lowers transparency but is not severe enough to make the release unfit on its own.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
contao/core-bundle Version ^4.9 || ^5.0 | — | — |
contao/news-bundle Version ^4.9 || ^5.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.