Package evidence

@antv/[email protected]

Install-time lifecycle script: postinstall="npm run schema"

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: 1,141Niche · −30% score
Versions published: 17Established · −30% score
First published: Aug 2021
Publisher: bbsqq

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

Publisherbbsqq

Artifact bytes39,165

Previous version0.1.0-alpha.15

Published2021-11-19T08:24:31.940Z

SHA-25673a79936dd192a591fadefe82ba7e76ba114e833045733239f507fb05321db5c

Why flagged

What the scanner saw

New Lifecycle Script Vs Previous: postinstall added in 0.1.0-alpha.17 vs 0.1.0-alpha.15: "npm run schema"

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

Availability ledger

available

high

27h agoLast checked

highRisk

45Score

0.1.0-alpha.17Version

Status history (1 event)

new → available27h 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 0.1.0-alpha.17 vs 0.1.0-alpha.15: "npm run schema"	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 0.1.0-alpha.17 vs 0.1.0-alpha.15: "npm run schema"	40
low	Install-time lifecycle script	package.json	postinstall="npm run schema"	5

Manifest

Package metadata

Scripts24

buildrun-p build:* && npm run size
build:cjsrimraf ./lib && tsc --module commonjs --outDir lib
build:esmrimraf ./esm && tsc --module ESNext --outDir esm
build:umdrimraf ./dist && rollup -c && npm run size
cirun-s schema lint test build
cleanrimraf lib esm dist
deploy:democd demo && npm run deploy:site
fixeslint ./src/**/*.ts ./__tests__/**/*.ts ./demo/**/*.{ts,tsx} --fix && npm run format
formatprettier --write "src/**/*.ts" "__tests__/**/*.ts" "demo/**/*.{ts,tsx}"
format-check prettier ./src/**/*.ts ./__tests__/**/*.ts ./demo/**/*.{ts,tsx} --check
linteslint ./src/**/*.ts ./__tests__/**/*.ts ./demo/**/*.{ts,tsx} && npm run format-check
lint-stagedlint-staged
one-stop-setupnpm install --package-lock=false && run-s setup:demo ci
postinstallnpm run schema
postversiongit push && git push --tags
preparehusky install
prepublishOnlynpm run ci
preversionnpm run lint
schemamkdir -p build && ts-json-schema-generator -f tsconfig.json -p src/index.ts -t AntVSpec --no-type-check --no-ref-encode > build/antv-spec.json
setup:democd demo && npm install --package-lock=false
sizelimit-size
start:demonpm run setup:demo && cd demo && npm start
testjest
versionnpm run format && git add -A src