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.
- Versions published
- 4
- First published
- Jan 2022
- Publisher
- kharutyunyan
Recommended action
Looks clean — keep monitoringNo high-signal indicators in the stored static report. PkgRadar will re-check on the next ingest pass.
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":["@labelbox/[email protected]"],"fail_on":"review"}'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":["@labelbox/[email protected]"],"fail_on":"review"}'Why flagged
What the scanner saw
No high-signal static finding in the saved report.
Not observed: package install, lifecycle script execution, or sandbox execution. PkgRadar only inspects on-disk artifacts.
Availability ledger
available
Status history (1 event)
- new → available · risk low · score 0 · status changed
Evidence
Static findings
No findings stored for this release.
Manifest
Package metadata
Scripts10
benchnode bench/bench.jsbuildrollup -c && cp src/polygon-clipping.d.ts dist/polygon-clipping.d.tsdocs:buildvite build docsdocs:devvite docsdocs:eslintcd docs && eslint --ext .js --ext .vue *config.js src/lintnpm-run-all -s lint:eslint docs:eslint lint:prettierlint:eslinteslint .eslintrc.cjs *.config.js bench/ src/ test/lint:prettierprettier --check ./* ./.eslintrc.cjstestnode --experimental-vm-modules node_modules/jest/bin/jest.jstest:debugnode --inspect-brk node_modules/.bin/jest --runInBand
Dependencies1
splaytree^3.1.0