Healthy and suitable to depend on. It has a long release history, a release published yesterday, active contributions from six maintainers, and complete package and repository documentation. The repository lacks a security policy and automated security scanning, so review those controls separately.
88%
Total Score
100
100
94
80
The repository uses Composer build tooling, but no security scanning tools were detected. The missing scanning is a genuine supply-chain hygiene gap, though it does not outweigh the strong maintenance evidence.
No repository security policy was found. That weakens vulnerability-reporting transparency, although the active organization-backed repository and recent maintenance partly compensate for the gap.
The only workflow lacks top-level token permissions. No write permissions were detected, but explicitly declaring restrictive permissions would provide stronger workflow hygiene.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/oms Version ^6.0.0 || ^7.0.0 || ^8.0.0 || ^10.0.0 || ^11.0.0 | — | — |
spryker/sales Version ^5.0.0 || ^6.0.0 || ^7.0.0 || ^8.0.0 || ^10.0.0 || ^11.0.0 | — | — |
spryker/kernel Version ^3.31.0 | — | — |
spryker/refund Version ^4.0.0 || ^5.0.0 | — | — |
spryker/payment Version ^3.0.0 || ^4.0.0 || ^5.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.