← Home

@img-custom/sharp-libvips-dev-wasm32

npm Repository Homepage

Header files and static wasm32 libraries for libvips and dependencies to build sharp as wasm32

3
Versions
LGPL-3.0-or-later
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

ollm

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition from ollm to GitHub Actions CI is consistent with the repo's automated release pipeline and backed by SLSA provenance. ai
bogus-package bogus-package AI (bogus-package): Dev-headers/static-libs package legitimately has no runtime deps, empty JS entry points, and minimal README. ai

Versions (showing 3 of 3)

Version Deps Published
0.0.9 0 / 0
0.0.8 0 / 0
0.0.1 0 / 0

v0.0.9

2 findings
HIGH Publisher changed: ollm → GitHub Actions (on 2026-05-04) provenance

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.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.0.8

2 findings
HIGH Publisher changed: ollm → GitHub Actions (on 2026-05-03) provenance

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.

INFO Has SLSA provenance attestation provenance

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 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.