No commits in the last three months and all eight workflow actions are unpinned, while the repository has no security policy. The recent release, license, README, changelog, and non-archived repository provide useful maintenance and transparency evidence.
61%
Total Score
50
100
88
75
The package has existed since August 2014 and released once in the last 12 months, but its 12-release history reflects a relatively infrequent cadence. This is a modest maintenance concern rather than evidence of abandonment.
The repository recorded zero commits and zero active maintainers in the last three months. For a maintained extension, that lowers confidence in ongoing fixes and support.
Composer is used for the build, but no security scanning tool is configured. The missing scanner is a hygiene gap, not evidence that the package is unsafe by itself.
The repository has no security policy. That leaves vulnerability reporting and response expectations undocumented for consumers.
All four workflows were analyzed successfully with no dangerous audit findings or untrusted sinks, but all eight action references are unpinned. This leaves workflow dependencies exposed to tag or branch changes and is a real supply-chain hygiene concern.
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.