spryker/asset-storage
Workflow hardening is incomplete, and the repository has no security policy or automated security-scanning tool. Tests, release notes, organization backing, and five active contributors provide useful maintenance evidence.
82%
Total Score
100
88
67
Health Score Breakdown
The package has six releases over about four years, with no release in the past 12 months and a median interval of about 253 days. This slows confidence in registry delivery, but recent repository commits provide compensating maintenance evidence.
Composer build tooling is present, but no security-scanning tools were detected. The missing scanning is a modest supply-chain hygiene gap rather than evidence of abandonment.
No repository security policy was found. This weakens transparency for reporting and handling vulnerabilities, though it does not by itself show that the package is unsafe.
The single workflow was fully analyzed with no dangerous triggers, untrusted checkouts, script injection, or audit findings. However, two of four action references are unpinned, so workflow reproducibility and update integrity are only partly strong.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
No maintainer information available.
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 spryker/asset Version ^1.4.0 | — | — |
spryker/store Version ^1.0.0 | — | — |
spryker/kernel Version ^3.30.0 | — | — |
spryker/storage Version ^3.0.0 | — | — |
spryker/transfer Version ^3.27.0 | — | — |
Weekly Downloads
Info
- Last Published
- 1 year ago
- Created
- 4 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.