spryker/category-image-storage
Workflow hygiene is incomplete because two of four actions are unpinned, and no security policy or scanning tool is reported. The package remains clearly documented, tested, and actively maintained by a well-distributed team.
86%
Total Score
100
94
83
Health Score Breakdown
The repository uses Composer for builds, but no security-scanning tool was detected. The missing scan is a modest transparency and hygiene gap, not evidence of abandonment.
No repository security policy was found. For a maintained library this leaves vulnerability-reporting expectations less clear, creating a minor transparency concern.
The sole workflow was fully analyzed with no dangerous triggers, untrusted checkouts, script injection, or audit findings. However, two of four action references are unpinned, which weakens reproducibility and supply-chain hygiene.
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.30.0 | — | — |
spryker/storage Version ^3.4.0 | — | — |
spryker/category Version ^4.23.0 || ^5.8.0 | — | — |
spryker/transfer Version ^3.27.0 | — | — |
spryker/propel-orm 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.