spryker/store
Healthy and suitable to depend on. It has a long release history, regular recent releases, active and well-distributed contributors, strong package structure, and an unarchived organization-backed repository; the main caveat is limited repository security-policy and workflow-permission hygiene.
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 is a modest supply-chain transparency gap, though it is not evidence of abandonment.
No repository security policy was found. For an organization-backed package this reduces vulnerability-reporting transparency, but it is a hygiene concern rather than evidence that the release is unfit.
The repository's one workflow has no top-level permissions declaration, so its token scope is not explicitly constrained in the collected metadata. This is a workflow-hardening gap, partially offset by the absence of detected dangerous workflow patterns.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 spryker/log Version ^1.0.0 || ^2.0.0 || ^3.0.0 | — | — |
spryker/kernel Version ^3.30.0 | — | — |
spryker/symfony Version ^3.0.0 | — | — |
spryker/transfer Version ^3.27.0 | — | — |
spryker/propel-orm Version ^1.0.0 | — | — |
Weekly Downloads
Info
- Last Published
- 5 days ago
- Created
- 9 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.