The missing README and absent security safeguards reduce transparency and resilience. Its focused dependencies, declared license, regular releases, and recent repository activity provide useful support.
70%
Total Score
75
100
79
50
A changelog and GitHub release exist for the assessed version, but the package has no README and no tests; the release documentation partly offsets the missing consumer guidance.
All four recent commits came from one contributor, leaving maintenance dependent on a single active person and increasing continuity risk.
Composer is used for builds, but no security scanning tools were detected; this is a hygiene gap rather than evidence that the package is unsafe.
The repository has no security policy, which leaves vulnerability-reporting expectations and response guidance undocumented.
Version 0.2.3 is not a stable major release, so its API may still change, although it is not marked as a prerelease and recent releases are stable.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
contao/conflicts Version @dev | — | — |
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.