PkgRadar

Package evidence

@nirs4all/[email protected]

Suspicious Publish Context: {"package_age_days":5,"publisher":"gbeurier","burst_same_day":1,"burst_week":2,"lure":{"kind":"token_affix","target":"methods"},"version_anomaly":false,"new_account":false}

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
138
Versions published
3
First published
Jun 2026
Publisher
gbeurier

Recommended action

Review before promoting

Mixed signals: the package has indicators worth reading before allowing the update in automated dependency flows.

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":["@nirs4all/[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":["@nirs4all/[email protected]"],"fail_on":"review"}'
Publishergbeurier
Artifact bytes674,340
Previous version1.0.0
Published2026-06-16T16:27:31.443Z
SHA-2564037c5c1557005afc5ce57c14649d726eefc6b8f4e527ddf585bdf1a31ab4d89

Why flagged

What the scanner saw

Suspicious Publish Context: {"package_age_days":5,"publisher":"gbeurier","burst_same_day":1,"burst_week":2,"lure":{"kind":"token_affix","target":"methods"},"version_anomaly":false,"new_account":false}

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

Availability ledger

available

review
Last checked
reviewRisk
10Score
1.0.1Version
Status history (1 event)
  1. newavailable · risk review · score 10 · status changed

Evidence

Static findings

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

SeverityKindPathDetailPoints
mediumSuspicious Publish Contextmanifest{"package_age_days":5,"publisher":"gbeurier","burst_same_day":1,"burst_week":2,"lure":{"kind":"token_affix","target":"methods"},"version_anomaly":false,"new_account":false}10

Manifest

Package metadata

Scripts5
  • buildnpm run clean && tsc -p .
  • cleannode -e "require('fs').rmSync('dist',{recursive:true,force:true})"
  • prepacknpm run build && npm run stage:wasm
  • stage:wasmnode -e "const fs=require('fs'),p='../../build/emscripten/bindings/js/';fs.mkdirSync('dist',{recursive:true});for(const f of ['n4m.js','n4m.wasm']){if(!fs.existsSync(p+f))throw new Error('missing WASM artifact '+p+f+' — run: cmake --preset emscripten && cmake --build --preset emscripten --target pls4all_wasm');fs.copyFileSync(p+f,'dist/'+f)}console.log('staged n4m.js + n4m.wasm into dist/')"
  • testnode --experimental-vm-modules test/run_smoke.mjs && node --experimental-vm-modules test/run_api.mjs && node --experimental-vm-modules test/run_generic_method.mjs && node --experimental-vm-modules test/run_pop_aom.mjs