@img-custom/sharp-libvips-win32-ia32
Prebuilt libvips and dependencies for use with sharp on Windows x86
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): Package is explicitly a prebuilt libvips binary distribution; DLLs are the intended payload, not backdoors. | ai | |
| provenance | publisher-changed | AI (provenance): Change from ollm to GitHub Actions reflects CI/CD automation; SLSA provenance attestation confirms legitimate pipeline. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Binary platform package; empty index.js, no deps, and sparse README are all expected for this package type. | ai |
v0.0.9
3 findingsPackage contains compiled binaries that could be backdoors: • lib/libaom.dll • lib/libarchive-13.dll • lib/libbrotlicommon.dll • lib/libbrotlidec.dll • lib/libbrotlienc.dll • lib/libc++.dll • lib/libcairo-2.dll • lib/libcfitsio.dll • lib/libcgif-0.dll • lib/libdicom-1.dll ... and 51 more
This version was published by a different npm account than previous versions on 2026-05-04. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.8
3 findingsPackage contains compiled binaries that could be backdoors: • lib/libaom.dll • lib/libarchive-13.dll • lib/libbrotlicommon.dll • lib/libbrotlidec.dll • lib/libbrotlienc.dll • lib/libc++.dll • lib/libcairo-2.dll • lib/libcfitsio.dll • lib/libcgif-0.dll • lib/libdicom-1.dll ... and 51 more
This version was published by a different npm account than previous versions on 2026-05-03. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.