The package has a long release history, regular recent releases, and clear organization backing. Missing security policy and scanning, plus the repository's lack of an explicit package reference, reduce transparency.
68%
Total Score
75
100
86
75
No commits and no active maintainers were recorded in the last three months. Although recent releases and a recent repository push provide some compensation, this still lowers confidence in ongoing development activity.
The repository name does not match the package name and its README does not mention the package, so the link between this artifact and its source is less transparent. The matching organization provides only partial reassurance.
Composer build tooling is present, but no security scanning tools were detected. That is a transparency and hygiene gap, not evidence that the package is unsafe.
The repository has no security policy, leaving vulnerability reporting and response expectations undocumented.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
pimcore/pimcore Version ^2026.2 | — | — |
coreshop/taxation Version ^2026.1 | — | — |
coreshop/money-bundle Version ^2026.1 | — | — |
coreshop/resource-bundle Version ^2026.1 | — | — |
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.