Package evidence

@glomex/[email protected]

Install-time lifecycle script: postinstall="postinstall-build lib --script build"

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: 4
Versions published: 7
First published: Dec 2017
Publisher: klipstein

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":["@glomex/[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":["@glomex/[email protected]"],"fail_on":"high"}'

Publisherklipstein

Artifact bytes9,277

Previous version2.0.0

Published2017-12-18T11:31:01.307Z

SHA-256ef0815d131c4c597149c2edf4f6bb97a925c208dbb51c6e29c72a201bf204843

Why flagged

What the scanner saw

New Lifecycle Script Vs Previous: postinstall added in 2.0.1 vs 2.0.0: "postinstall-build lib --script build"

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

Availability ledger

available

high

4h agoLast checked

highRisk

45Score

2.0.1Version

Status history (1 event)

new → available4h ago · risk high · score 45 · status changed

Evidence

Static findings

1 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 2.0.1 vs 2.0.0: "postinstall-build lib --script build"	40

Show all 2 findings (low-signal and informational)

Severity	Kind	Path	Detail	Points
high	New Lifecycle Script Vs Previous	package.json	postinstall added in 2.0.1 vs 2.0.0: "postinstall-build lib --script build"	40
low	Install-time lifecycle script	package.json	postinstall="postinstall-build lib --script build"	5

Manifest

Package metadata

Scripts6

buildbabel src --out-dir lib --copy-files
bumpbump-version ./ --verify-script "npm run test" --npm-publish
linteslint src test
postinstallpostinstall-build lib --script build
testmocha --recursive --ui tdd test/*
test-cinpm run test && npm run lint

Dependencies3

deep-equal^1.0.1
object-path^0.11.4
traverse^0.6.6

Optional dependencies1

@glomex/vvs-bump-version^1.0.5