The repository has no security policy or automated security scanning. Two of four workflow actions are unpinned, while release notes, a license file, and active contributors provide useful transparency and continuity.
72%
Total Score
100
88
75
Only two releases exist, with none in the last 12 months and the latest release over a year ago; this raises maintenance and freshness concerns.
Composer build tooling is present, but no security-scanning tooling was detected, leaving a modest transparency and assurance gap.
The repository has no security policy, so reporting and handling of vulnerabilities is less transparent for consumers.
The single workflow was fully audited with no injection or high-severity findings; two of four actions are unpinned, which is a minor reproducibility and supply-chain hygiene gap.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/store Version ^1.19.0 | — | — |
spryker/kernel Version ^3.30.0 | — | — |
spryker/symfony Version ^3.0.0 | — | — |
spryker/transfer Version ^3.27.0 | — | — |
spryker/flysystem Version ^3.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.