Clear packaging and stable versioning add confidence. The repository lacks a security policy, and half of workflow actions are unpinned.
88%
Total Score
100
100
94
88
Composer build tooling is present, but no repository security-scanning tools were detected. This is a modest transparency gap, not evidence of unsafe code by itself.
The repository has no SECURITY.md or other security policy, leaving vulnerability-reporting expectations undocumented; the active organization and repository provide partial context but do not replace the policy.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/kernel Version ^3.30.0 | — | — |
spryker/transfer Version ^3.25.0 | — | — |
spryker/uuid-behavior Version ^1.0.0 | — | — |
spryker/glue-application Version ^1.15.0 | — | — |
spryker/discount-promotion Version ^4.4.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.