This check works by comparing the composer.lock against an open vulnerability database. A clean check does not mean there are absolutely no security problems whatsoever.
42%
Total Score
0
75
50
The package has had no releases in the last 12 months, and its latest release was over 8 years ago. Its 17-release history shows prior activity but does not compensate for the prolonged current inactivity.
The repository had 0 commits and 0 active maintainers in the last 3 months, reinforcing the long release gap and indicating no current maintenance capacity.
The project uses Composer build tooling, but no security scanning tools were detected. That is a meaningful hygiene gap for an extension whose purpose is security-advisory checking.
The repository has no security policy, reducing transparency for reporting and handling vulnerabilities in a security-focused package.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
contao/core Version >=3.2,<4.0-dev | — | — |
guzzlehttp/guzzle Version ~6.0 | — | — |
contao-community-alliance/composer-plugin Version ~2.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.