PkgRadar

Package evidence

[email protected]

no findings

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
434Mature · −50% score
First published
Mar 2018
Publisher
snyk-admin

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

Recommended action

Looks clean — keep monitoring

No 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":["[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":["[email protected]"],"fail_on":"review"}'
Publishersnyk-admin
Artifact bytes217,143
Previous version9.6.5
Published2026-05-07T16:08:45.009Z
SHA-256cb97ee98131fd1659860d0a91ba17398456d5332d0c0161e3d4a59d182a6888e

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

low
Last checked
lowRisk
0Score
9.7.0Version
Status history (1 event)
  1. newavailable · risk low · score 0 · status changed

Evidence

Static findings

No findings stored for this release.

Manifest

Package metadata

Scripts14
  • buildtsc
  • build-watchtsc -w
  • debugtsc-watch --project tsconfig.json --onSuccess 'node --inspect --inspect-brk .'
  • formatprettier --loglevel warn --write '{lib,test}/**/*.ts' && tslint --fix --format stylish '{lib,test}/**/*.ts'
  • lintrun-p --max-parallel=${JOBS:-5} --aggregate-output lint:*
  • lint:commitcommitlint --from=HEAD~1
  • lint:prettierprettier --check "{lib,test}/**/*.ts"
  • lint:tslinttslint --format stylish "{lib,test}/**/*.ts"
  • preparenpm run build
  • testnpm run test-jest
  • test-jestjest --ci --maxWorkers=3 --logHeapUsage --colors
  • test-jest-windowsjest --ci --maxWorkers=3 --config test/windows/jest.config.js --logHeapUsage
  • test:systemjest --ci --maxWorkers=3 --logHeapUsage --colors --testPathPattern='test/system/'
  • test:unitjest --ci --maxWorkers=3 --logHeapUsage --colors --testPathPattern='test/(lib|unit)/'
Dependencies25
  • @snyk/composer-lockfile-parser^1.4.1
  • @snyk/dep-graph^2.12.1
  • @snyk/docker-registry-v2-client^2.24.2
  • @snyk/rpm-parser^3.4.1
  • @snyk/snyk-docker-pull^3.15.1
  • @swimlane/docker-reference^2.0.1
  • adm-zip^0.5.17
  • chalk^2.4.2
  • debug^4.4.3
  • docker-modem^3.0.8
  • dockerfile-ast^0.7.1
  • elfy^1.0.0
  • event-loop-spinner^2.3.2
  • fzstd^0.1.1
  • gunzip-maybe^1.4.2
  • minimatch^9.0.0
  • packageurl-js1.2.0
  • semver^7.7.3
  • shescape^2.1.7
  • snyk-nodejs-lockfile-parser^2.7.0
  • snyk-poetry-lockfile-parser1.9.1
  • snyk-resolve-deps^4.9.1
  • tar-stream^2.2.0
  • tslib^1
  • varint^6.0.0