@img/sharp-linuxmusl-x64
Prebuilt sharp for use with Linux (musl) x64
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 |
|---|---|---|---|---|
| — | bundled-binaries | platform-specific prebuilt libvips binary from @lovell (HIGH trust); bundled native binary is the package's intended purpose | sean |
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.35.2
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.33.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.