PkgRadar

Package evidence

@datadog/[email protected]

Install-time lifecycle script: install="exit 0"

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
8,681,588Ubiquitous · −70% score
Versions published
104Mature · −50% score
First published
Jul 2021
Publisher
GitHub ActionsTrusted automation · −70% score

Effective trust discount applied: 70% (max across signals — discounts don’t stack). New install-lifecycle deltas vs the previous release would clear the discount.

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":["@datadog/[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":["@datadog/[email protected]"],"fail_on":"review"}'
Artifact bytes5,183,866
Previous version5.14.1
Published2026-05-20T08:59:45.546Z
SHA-2563c99b9c3cc6011343d7356a3d0688560a435fa21d63ec40ad5011493d7d8e2d8

Why flagged

What the scanner saw

Install-time lifecycle script: install="exit 0"

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

Availability ledger

available

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

Evidence

Static findings

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

No high-signal findings — see all findings below.

Show all 1 findings (low-signal and informational)
SeverityKindPathDetailPoints
lowInstall-time lifecycle scriptpackage.jsoninstall="exit 0"5

Manifest

Package metadata

Scripts21
  • buildnode-gyp configure build --jobs=max
  • build:asannode-gyp configure build --jobs=max --address_sanitizer
  • build:tsannode-gyp configure build --jobs=max --thread_sanitizer
  • codecovnyc report --reporter=json && codecov -f coverage/*.json
  • compiletsc -p .
  • fixgts fix
  • formatclang-format --style file -i --glob='bindings/**/*.{h,hh,cpp,cc}'
  • installexit 0
  • lintjsgl --local . && gts check && clang-format --style file -n -Werror --glob='bindings/**/*.{h,hh,cpp,cc}'
  • preparenpm run compile && npm run rebuild
  • pretestnpm run compile
  • pretest:js-asannpm run compile && npm run build:asan
  • pretest:js-tsannpm run compile && npm run build:tsan
  • pretest:js-valgrindnpm run pretest
  • rebuildnode-gyp rebuild --jobs=max
  • testnpm run test:js
  • test:cppnode scripts/cctest.js
  • test:jsnyc mocha -r source-map-support/register out/test/test-*.js
  • test:js-asanLSAN_OPTIONS='suppressions=./suppressions/lsan_suppr.txt' LD_PRELOAD=`gcc -print-file-name=libasan.so` mocha out/test/test-*.js
  • test:js-tsanLD_PRELOAD=`gcc -print-file-name=libtsan.so` mocha out/test/test-*.js
  • test:js-valgrindvalgrind --leak-check=full mocha out/test/test-*.js
Dependencies3
  • node-gyp-build<5.0
  • pprof-format^2.2.1
  • source-map^0.7.4