Package evidence

[email protected]

Install Lifecycle Remote Or Exec: install="node -e \"\""

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: 7,568Niche · −30% score
Versions published: 17Established · −30% score
First published: Jan 2024
Publisher: wudidapaopao

Effective trust discount applied: −30% (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"}'

Publisherwudidapaopao

Artifact bytes43,410

Previous version3.1.0-rc.1

Published2026-06-15T07:41:06.789Z

SHA-256c0b60e9203467078f83c5c59b4d692540813fbb6c467ffa921dea2e42576cac3

Why flagged

What the scanner saw

New Lifecycle Script Vs Previous: install added in 3.1.0-rc.2 vs 3.1.0-rc.1: "node -e \"\""

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

Availability ledger

available

high

2d agoLast checked

highRisk

75Score

3.1.0-rc.2Version

Status history (1 event)

new → available2d ago · risk high · score 75 · 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	install added in 3.1.0-rc.2 vs 3.1.0-rc.1: "node -e \"\""	40
high	Install Lifecycle Remote Or Exec	package.json	install="node -e \"\""	30

Show all 3 findings (low-signal and informational)

Severity	Kind	Path	Detail	Points
high	New Lifecycle Script Vs Previous	package.json	install added in 3.1.0-rc.2 vs 3.1.0-rc.1: "node -e \"\""	40
high	Install Lifecycle Remote Or Exec	package.json	install="node -e \"\""	30
low	Install-time lifecycle script	package.json	install="node -e \"\""	5

Manifest

Package metadata

Scripts12

benchnode bench/bench.js
buildnode-gyp configure build --verbose && npm run fixloaderpath && npm run build:ts
build:platformbash ./scripts/build-platform-pkg.sh
build:tstsc -p tsconfig.build.json
fixloaderpathbash ./fix_loader_path.sh
installnode -e ""
libchdbbash ./update_libchdb.sh
prepacknpm run build:ts
testmocha test_basic.js test_connection.js --timeout 15000
test:allnpm run test && npm run test:v3
test:v3vitest run
typechecktsc -p tsconfig.json

Dependencies2

node-addon-api^6.1.0
node-gyp-build^4.6.0

Optional dependencies4

@chdb/lib-darwin-arm6426.5.1-rc.1
@chdb/lib-darwin-x6426.5.1-rc.1
@chdb/lib-linux-arm64-gnu26.5.1-rc.1
@chdb/lib-linux-x64-gnu26.5.1-rc.1