The package has clear documentation, tests, release notes, and a well-supported organization behind it. Its repository lacks a security policy, and two of four workflow actions are not pinned, but maintenance and ownership signals are strong.
88%
Total Score
100
100
94
75
The repository uses Composer build tooling, but no security-scanning tool was detected. This is a minor transparency and process gap, not evidence of unsafe code.
No repository security policy was found. That weakens the project's documented vulnerability-reporting process, though it does not outweigh the active, organization-backed maintenance evidence.
The single workflow was fully analyzed with no reported audit findings, no untrusted checkout or script-injection paths, and no broad top-level write permissions. 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/kernel Version ^3.37.0 | — | — |
spryker/storage Version ^3.0.0 | — | — |
spryker/event-behavior Version ^1.8.0 | — | — |
spryker/synchronization Version ^1.0.0 | — | — |
spryker/product-quantity Version ^1.3.0 || ^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.