The module includes tests, release notes, and recent work from five contributors under an active organization. There is no repository security policy and two of four workflow actions are unpinned, so keep normal dependency controls in place.
86%
Total Score
100
94
75
Composer build tooling is present, but no security-scanning tools were detected. The missing scanning automation is a minor transparency and hygiene gap, not evidence of unsafe code.
The repository has no security policy. This leaves vulnerability-reporting and response expectations undocumented, which is a modest transparency gap for a maintained package.
The single workflow was fully analyzed with no untrusted checkouts, script injection, high- or medium-severity findings, and no broad write permissions. Two of four actions are unpinned, which is a minor reproducibility and supply-chain hygiene concern.
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/merchant Version ^3.0.0 | — | — |
spryker/transfer Version ^3.27.0 | — | — |
spryker/propel-orm 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.