A license file, release notes, and a readable package make adoption straightforward. Workflow auditing found no high-risk issues, though no security policy is published.
88%
Total Score
100
94
83
Composer build tooling is present, but no security-scanning tool was detected. This is a modest transparency gap rather than evidence of abandonment.
The repository has no published security policy, leaving vulnerability-reporting expectations unclear. This is a transparency gap, not a direct indication that the release is unsafe.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/store Version ^1.4.0 | — | — |
spryker/kernel Version ^3.30.0 | — | — |
spryker/transfer Version ^3.25.0 | — | — |
spryker/product-storage Version ^1.15.0 | — | — |
spryker/category-storage Version ^1.11.0 || ^2.0.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.