← Home

@img-custom/sharp-libvips-dev

npm Repository Homepage

Header files and C++ sources for libvips and dependencies required when compiling sharp from source

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
bogus-package bogus-package AI (bogus-package): Headers-only dev package; empty JS entry, no deps, and minimal README are expected for this package type. ai
provenance publisher-changed AI (provenance): Transition from ollm to GitHub Actions CI matches the repo owner automating releases; SLSA attestation confirms CI provenance. 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.