@img/sharp-linux-s390x
Prebuilt sharp for use with Linux (glibc) s390x
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| npm-metadata | bundled-binaries | AI (npm-metadata): Prebuilt native .node binary is the entire purpose of this sharp platform sub-package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Platform-specific binary packages legitimately lack code examples and keywords. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 0.35.3 | 0 / 0 | |
| 0.35.2 | 0 / 0 | |
| 0.35.1 | 0 / 0 | |
| 0.35.0 | 0 / 0 | |
| 0.34.5 | 0 / 0 | |
| 0.34.4 | 0 / 0 | |
| 0.34.3 | 0 / 0 | |
| 0.34.2 | 0 / 0 | |
| 0.34.1 | 0 / 0 | |
| 0.34.0 | 0 / 0 | |
| 0.33.5 | 0 / 0 |
v0.35.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.34.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.33.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.