PkgRadar

Package evidence

[email protected]

Install-time lifecycle script: postinstall="node scripts/postinstall.cjs"

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
73Mature · −50% score
First published
Oct 2024
Publisher
petrpatek

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

Review before promoting

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

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":"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"}'
Publisherpetrpatek
Artifact bytes503,114
Previous version0.1.6-beta.29
Published2026-05-28T08:17:14.798Z
SHA-2561f05c09641674cfd56fc2e58ae3d8ea7c6aeb6fddcfea4f87594d73d4757b076

Why flagged

What the scanner saw

Install-time lifecycle script: postinstall="node scripts/postinstall.cjs"

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

Availability ledger

available

review
Last checked
reviewRisk
2Score
0.1.6-beta.30Version
Status history (2 events)
  1. available → available · risk review · score 2 · status available -> available, risk high -> review, score 25 -> 2
  2. new → available · risk high · score 25 · 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.jsonpostinstall="node scripts/postinstall.cjs"5

Manifest

Package metadata

Scripts23
  • buildnpm run clean && npm run compile && npm run copy-extension
  • build:browserbash browser/scripts/build.sh
  • build:browser:dockerbash browser/scripts/docker-build.sh
  • build:browser:linuxbash browser/scripts/docker-build.sh --linux-only
  • build:browser:windowsbash browser/scripts/docker-build.sh --windows-only
  • bundle:browsernode scripts/bundle-browser.cjs
  • ci:buildturbo run build --cache-dir=".turbo"
  • cleanrimraf ./dist
  • compiletsc -p tsconfig.build.json
  • copy-extensioncp -r src/fingerprinting/all-fingerprint-defender dist/fingerprinting/ && cp -r src/fingerprinting/anti-webgpu dist/fingerprinting/ && cp src/fingerprinting/non-apify-profiles.json dist/fingerprinting/
  • coveragevitest --coverage
  • linteslint src/**/*.ts test/**/*.ts
  • lint:fixeslint "src/**/*.ts" "test/**/*.ts" --fix
  • package:browserbash browser/scripts/package-binary.sh
  • postinstallnode scripts/postinstall.cjs
  • prepublishOnlynpm run build && node scripts/check-browser-released.cjs
  • release:browsernode scripts/release-browser.cjs
  • testvitest run --silent
  • test:docker:linuxbash test/docker-linux/run.sh
  • test:docker:linux:diagnosebash test/docker-linux/run.sh --diagnose
  • test:e2enode test/e2e/run.mjs
  • test:fullcross-env vitest run --silent
  • test:unitvitest run unit
Dependencies7
  • chrome-remote-interface^0.33.2
  • crawlee^3.15.3
  • fingerprint-generator^2.1.82
  • header-generator^2.1.82
  • proxy-chain^2.5.3
  • ps-tree^1.2.0
  • tar^7.5.15