Clear documentation, a changelog, and an organization-owned matching repository improve transparency. The package has had no release or repository activity for about two years and eight months, so pinning it carries meaningful maintenance risk.
58%
Total Score
67
100
81
75
The package has had no release in about two years and eight months, with no releases in the last 12 months. Its four-release history shows a real maintenance slowdown.
There were no commits and no active maintainers in the last three months, consistent with the long release gap. This materially raises the risk that fixes and compatibility updates will not arrive.
There were no new or closed issues or pull requests in the last month, while one issue and one pull request remain open. This offers no evidence of current maintenance activity.
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a hygiene weakness, though it is less significant than the observed maintenance gap.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented. This is a transparency gap for a package used in ecommerce integrations.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
contao/core-bundle Version ^4.9 | — | — |
isotope/isotope-core Version ^2.7 | — | — |
heimrichhannot/contao-formhybrid Version ^3.17 | — | — |
heimrichhannot/contao-utils-bundle Version ^2.191 | — | — |
heimrichhannot/contao-request-bundle Version ^1.2 | — | — |
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.