There is no security policy or automated security scanning, reducing transparency around maintenance and vulnerability handling. The package has a clear license and README, but those strengths do not offset its limited safeguards.
42%
Total Score
50
100
75
83
The repository recorded 0 commits and 0 active maintainers in the last 3 months, indicating no observed recent maintenance for a package whose current release is still a release candidate.
The package includes a substantial README, but it explicitly says to use the plugin at your own risk and not in production; the absence of tests and a changelog is normal for a published artifact.
There were 12 releases in the last 12 months, showing an initial burst of publishing, but the zero-day median interval suggests clustered releases rather than a demonstrated steady cadence.
Composer build tooling is present, but no security scanning tools were detected, leaving automated checks for vulnerabilities or unsafe changes unprovided.
The repository has no security policy, so there is no documented process for reporting or handling vulnerabilities.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
contao/core-bundle Version ^5.3 | — | — |
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.