Tests, a changelog, and release notes improve transparency, while installation runs no lifecycle scripts. The organization-backed repository is active and spread across four contributors, but workflow references are unpinned and no security policy is published.
82%
Total Score
100
88
67
Composer build tooling is present, but no security scanning tool was detected, leaving a modest repository hygiene gap.
The repository has no published security policy, which reduces transparency about vulnerability reporting and response.
The release is not marked prerelease, but the project is still below a stable major version, so compatibility maturity is somewhat limited.
The workflow audit completed cleanly with no dangerous triggers, untrusted checkouts, or audit findings, but all four action references are unpinned, weakening build reproducibility.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/log Version ^3.0.0 | — | — |
spryker/oms Version ^11.0.0 | — | — |
spryker/user Version ^3.0.0 | — | — |
spryker/sales Version ^11.0.0 | — | — |
spryker/kernel Version ^3.72.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.