The package has a clear README, a matching repository, a stable 1.0.0 release, and no install-time scripts. Its single-release history and zero recent commits provide little evidence of ongoing maintenance, while the repository has neither security scanning nor a security policy.
68%
Total Score
50
100
88
83
One registry maintainer publishes the package. This is a limited publishing base, though the repository is owned by the same named individual, so the evidence supports continuity rather than an unexplained mismatch.
The registry namespace and repository owner match, but the owner is an individual account rather than an organization. This supports package identity while leaving the project with a narrow backing base.
This is the package's first release and it was published less than a day ago, so there is no release track record yet. That is a meaningful maturity gap, but not evidence of abandonment for a newly published package.
There were no commits and no active maintainers during the last three months. Because the repository was created and released less than a day ago, this mainly means maintenance capacity is unproven rather than demonstrably abandoned.
Composer is used as the build tool, but no security scanning tools were detected. The missing scanning is a hygiene and transparency gap, not a severe risk by itself.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
contao/core-bundle Version ^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.