No commits were recorded in the last three months, and the repository has no security scanning or security policy. The MIT declaration, matching source repository, and lack of install-time scripts reduce transparency and execution concerns, but do not offset the stale release line.
45%
Total Score
0
64
75
The latest release was published in October 2018, with no releases in the last 12 months despite a package age of about 8 years and 10 months. This is strong abandonment evidence.
The repository recorded zero commits and zero active maintainers in the last three months. That reinforces the long gap since the last package release and raises maintenance risk.
The artifact has no README, tests, or changelog, while the repository also reports no tests or changelog. Missing tests and changelog are normal packaging gaps here, but the absent README modestly hurts consumer guidance.
Composer build tooling is present, but no security-scanning tools were detected. For a bundle handling shop and payment integrations, that is a meaningful hygiene gap.
The repository has no security policy or documented reporting path. This weakens transparency and makes vulnerability response less clear.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
contao/core-bundle Version ~4.4 | — | — |
setasign/fpdi-fpdf Version ^2.0 | — | — |
2do/contao-basic-bundle Version ~0.5 | — | — |
paypal/rest-api-sdk-php Version ^1.13 | — | — |
symfony/framework-bundle Version ~2.8|~3.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.