Package evidence

[email protected]

Install Lifecycle Suppresses Failure: postinstall="if pkg-config vips 2>/dev/null; then npm explore sharp -- npm run build; fi"

Trust signals

Why this verdict

PkgRadar discounts a release’s score when public reputation argues against novel malware. The verdict above already reflects these — the panel just explains what was applied.

Weekly downloads: 414
Versions published: 60Mature · −50% score
First published: Jun 2019
Publisher: mbklein

Effective trust discount applied: −50% (max across signals — discounts don’t stack). New install-lifecycle deltas vs the previous release would clear the discount.

Recommended action

Block this update

Static evidence trips multiple high-signal indicators. Quarantine the release until the publisher validates the change or you can rule out the indicators below.

Inspect tarball Add to CI gate

Block this release in CIcurl · GitHub Actions

Fail the build when this package version is added or upgraded. Replace $PKGRADAR_TOKEN with a Pro / Team API key from your dashboard.

curl -fsS https://pkgradar.com/gate/npm \
  -H "Authorization: Bearer $PKGRADAR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"specs":["[email protected]"],"fail_on":"high"}'

GitHub Actions step:

- name: PkgRadar gate
  run: |
    curl -fsS https://pkgradar.com/gate/npm \
      -H "Authorization: Bearer ${{ secrets.PKGRADAR_TOKEN }}" \
      -H "Content-Type: application/json" \
      -d '{"specs":["[email protected]"],"fail_on":"high"}'

Publishermbklein

Artifact bytes68,081

Previous version8.0.1

Published2026-06-10T20:36:33.326Z

SHA-256e837e83985eeee331624a4577b6ff990533b059a05b59f7091761d0483aea6c5

Why flagged

What the scanner saw

New Lifecycle Script Vs Previous: postinstall added in 8.0.2 vs 8.0.1: "if pkg-config vips 2>/dev/null; then npm explore sharp -- npm run build; fi"

Not observed: package install, lifecycle script execution, or sandbox execution. PkgRadar only inspects on-disk artifacts.

Availability ledger

available

high

19h agoLast checked

highRisk

65Score

8.0.2Version

Status history (1 event)

new → available19h ago · risk high · score 65 · status changed

Evidence

Static findings

2 static · 1 from release diff · showing high-signal first.

Severity	Kind	Path	Detail	Points
high	New Lifecycle Script Vs Previous	package.json	postinstall added in 8.0.2 vs 8.0.1: "if pkg-config vips 2>/dev/null; then npm explore sharp -- npm run build; fi"	40
high	Install Lifecycle Suppresses Failure	package.json	postinstall="if pkg-config vips 2>/dev/null; then npm explore sharp -- npm run build; fi"	20

Show all 3 findings (low-signal and informational)

Severity	Kind	Path	Detail	Points
high	New Lifecycle Script Vs Previous	package.json	postinstall added in 8.0.2 vs 8.0.1: "if pkg-config vips 2>/dev/null; then npm explore sharp -- npm run build; fi"	40
high	Install Lifecycle Suppresses Failure	package.json	postinstall="if pkg-config vips 2>/dev/null; then npm explore sharp -- npm run build; fi"	20
low	Install-time lifecycle script	package.json	postinstall="if pkg-config vips 2>/dev/null; then npm explore sharp -- npm run build; fi"	5

Manifest

Package metadata

Scripts13

buildtsup
build:watchtsup --watch
cleanrm -rf node_modules/ vendor/ coverage/ dist/
linteslint "{src,tests}/**/*.{js,ts}"
lint:examplescd examples/tiny-iiif && npm run lint
lint:fixeslint --fix "{src,tests}/**/*.{js,ts}"
postinstallif pkg-config vips 2>/dev/null; then npm explore sharp -- npm run build; fi
preparenpm run build
testnode scripts/test.js --env=node
test:coveragenode scripts/test.js --env=node --coverage
typechecktsc -p tsconfig.json --noEmit
typecheck:stricttsc -p tsconfig.strict.json --noEmit
validatenpm run build && concurrently -s !command-server -k -n server,iiif --hide server -c blue,green "cd examples/tiny-iiif && npm run validator" "cd validator && sleep 2 && uv run ./run-validator.sh"

Dependencies2

debug^4.3.4
mime-types2.x

Optional dependencies1

sharp^0.35.0