Documentation and release packaging are solid, with a matching organization-owned repository. The roughly annual release cadence and no commits in the last three months suggest limited ongoing maintenance; no security tooling adds a smaller transparency concern.
68%
Total Score
75
100
88
67
The package has only two releases across about 22 months, with one release in the last 12 months and a median interval of about 12 months. This indicates a slow but not clearly abandoned cadence for a focused plugin.
There were zero commits and zero active maintainers in the last three months. Although the repository was updated with the release, the lack of subsequent activity lowers confidence in ongoing maintenance.
Composer is used as a build tool, but no security scanning tools were detected. For a small plugin this is a modest transparency and maintenance concern, not evidence of an unsafe release.
The repository has no security policy. This weakens vulnerability-reporting transparency, though it is a smaller concern than the maintenance signals.
No GitHub Actions workflows were present, so there were no workflow risks or unpinned actions to flag. Continuous integration and automated checks are also not evidenced.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
shopware/core Version ~6.7.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.