The package includes tests, a changelog, release notes, and no install-time scripts. A missing security policy and absent security scanning are small transparency gaps; workflow auditing found no dangerous findings.
86%
Total Score
100
94
75
Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a modest supply-chain transparency gap, not evidence of unsafe code.
The linked repository has no security policy. That weakens vulnerability-reporting transparency, although active maintenance and repository tests provide compensating project evidence.
We didn't find any vulnerabilities for this package.
No maintainer information available.
| Dependency | Last Release | Score |
|---|---|---|
spryker/log Version ^3.0.0 | — | — |
spryker/quote Version ^2.20.0 | — | — |
spryker/sales Version ^11.59.0 | — | — |
spryker/kernel Version ^3.52.0 | — | — |
spryker/locale Version ^4.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.