spryker/product-packaging-unit
Tests, release notes, and a matching source tree improve day-to-day confidence. Six recent contributors provide resilience, while missing security scanning and a repository security policy leave modest process gaps.
86%
Total Score
100
100
94
83
Health Score Breakdown
Composer build tooling is present, but no security-scanning tooling was detected. This is a modest process gap, not a direct release-quality failure.
The repository has no security policy. That weakens vulnerability-reporting transparency, although the active organization-backed project and other maintenance evidence partly compensate.
The single workflow was fully analyzed with no findings, no untrusted checkout or script-injection paths, and no top-level write permissions. Two of four action references are unpinned, which is a minor reproducibility and supply-chain hygiene gap.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 spryker/oms Version ^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/store Version ^1.4.0 | — | — |
spryker/kernel Version ^3.30.0 | — | — |
spryker/locale Version ^3.0.0 || ^4.0.0 | — | — |
Weekly Downloads
Info
- Last Published
- 2 months ago
- Created
- 8 years ago
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.