The README, changelog, and release notes give consumers useful documentation, while the package is clearly tied to its source repository. A missing security policy and two unpinned workflow actions leave modest transparency and build-reproducibility gaps.
84%
Total Score
100
94
67
Composer is used as the build tool, but no security-scanning tooling was detected. The missing scanning automation is a modest repository-hygiene gap, not evidence of unsafe code.
The repository has no published security policy. That reduces transparency for reporting and handling vulnerabilities, although it does not by itself indicate abandonment.
The sole workflow was fully analyzed with no audit findings or untrusted-trigger sinks. Two of four action references are unpinned, which is a minor reproducibility gap rather than a severe workflow risk.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/kernel Version ^3.30.0 | — | — |
spryker/symfony Version ^3.0.0 | — | — |
spryker/transfer Version ^3.42.0 | — | — |
spryker/container Version ^1.10.0 | — | — |
spryker/cart-reorder Version ^1.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.