spryker/customer-access-storage
Clear documentation, tests, and release notes make integration easier. The CI audit found no dangerous workflow findings, though two of four actions are unpinned and no security policy is published.
87%
Total Score
100
94
83
Health Score Breakdown
Composer is used as the build tool, but no security scanning tool was detected. The missing scanning automation is a minor transparency and hygiene gap, not evidence of abandonment.
The repository has no published security policy. This weakens vulnerability-reporting transparency, although recent commits and organization ownership partly compensate for the 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/kernel Version ^3.37.0 | — | — |
spryker/storage Version ^3.0.0 | — | — |
spryker/propel-orm Version ^1.5.0 | — | — |
spryker/customer-access Version ^1.0.0 | — | — |
spryker/synchronization Version ^1.0.0 | — | — |
Weekly Downloads
Info
- Last Published
- 5 months ago
- Created
- 7 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.