spryker/availability
Healthy and suitable to depend on. It has a long release history, recent releases, active multi-contributor maintenance, tests, documentation, and an unarchived repository; the main caveats are the missing security policy and unspecified workflow token permissions.
88%
Total Score
100
100
94
80
Health Score Breakdown
The repository uses Composer build tooling, but no security scanning tools were detected. The missing scanning coverage is a modest transparency and maintenance caveat, not evidence that the package is unsafe.
The repository has no security policy. That weakens disclosure transparency, although active maintenance and the absence of dangerous workflow patterns provide some compensating evidence.
The CI workflow does not declare top-level token permissions. This leaves its GitHub token access less explicit than recommended and creates a small workflow-hygiene concern.
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/event Version ^2.3.0 | — | — |
spryker/stock Version ^8.11.0 | — | — |
spryker/store Version ^1.19.0 | — | — |
spryker/touch Version ^3.0.0 || ^4.0.0 | — | — |
Weekly Downloads
Info
- Last Published
- 9 days ago
- Created
- 10 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.