PkgRadar

Package evidence

[email protected]

Credential File Packaged: package/.env

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
1
First published
Jun 2026
Publisher
nuodbit

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 tarballAdd 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"}'
Publishernuodbit
Artifact bytes86,407
Previous versionnone
Published2026-06-12T16:48:34.931Z
SHA-2560c52a60f479b260a36feca68d926e30bb3571be5424ac26b3d4102ab577f5951

Why flagged

What the scanner saw

Credential File Packaged: package/.env

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

Availability ledger

available

high
Last checked
highRisk
35Score
4.2.1Version
Status history (1 event)
  1. new → available · risk high · score 35 · status changed

Evidence

Static findings

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

SeverityKindPathDetailPoints
highCredential File Packagedpackage/.envpackage/.env35

Manifest

Package metadata

Scripts13
  • buildnode-gyp rebuild --release
  • coverage-smokenode-gyp rebuild -d && npm run lint && nyc --report-dir /coverage --reporter=lcov --reporter=text-lcov mocha --reporter spec --timeout 10000 --check-leaks --exclude='test/nightly/**' test/
  • linteslint index.js lib/*.js test/*.js
  • mocha-listmocha
  • preparebash scripts/fetch-client-from-docker.sh && npm run build
  • shutdownnode-gyp rebuild -d && mocha --reporter spec --timeout 10000 --check-leaks test/shutdown/
  • testnode-gyp rebuild -d && mocha --reporter spec --timeout 10000 --check-leaks test/
  • test-nightlynode-gyp rebuild -d && npm run lint && mocha --reporter spec --timeout 10000 --check-leaks test/nightly/ test/shutdown/
  • test-smokenode-gyp rebuild -d && npm run lint && mocha --reporter spec --timeout 10000 --check-leaks --exclude='test/nightly/**' test/
  • this-coveragenode-gyp rebuild -d && npm run lint && nyc --reporter=lcov --reporter=text-lcov mocha --timeout 10000 --reporter spec --bail --check-leaks
  • this-testnode-gyp rebuild -d && npm run lint && mocha --timeout 10000 --reporter spec --bail --check-leaks
  • valgrindnode-gyp rebuild -d && G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck --leak-check=full --show-reachable=yes --num-callers=40 --log-file=/valgrind/valgrind.log $(which node) valgrind.js
  • valgrind-testnode-gyp rebuild -d && G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck --leak-check=full --show-reachable=yes --num-callers=40 --log-file=/valgrind/valgrind.log mocha --reporter spec --bail --check-leaks test/
Dependencies8
  • bindings^1.5.0
  • express^5.1.0
  • nan^2.23.0
  • nconf^0.13.0
  • node-gyp^11.4.1
  • pino^9.9.0
  • segfault-handler^1.3.0
  • yargs^17.7.2