PkgRadar

Package evidence

@usrivastava92/[email protected]

New Account With Lifecycle Hook: package first published 6 day(s) ago, 4 total version(s), has lifecycle hook

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
4
First published
Jun 2026
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

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.

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":["@usrivastava92/[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":["@usrivastava92/[email protected]"],"fail_on":"high"}'
Artifact bytes23,400
Previous version1.1.0
Published2026-06-10T05:51:17.468Z
SHA-2567e94f7b01f75f9b4a2db7768c1fc9726ce78ebddb033add366a6a887d2392c25

Why flagged

What the scanner saw

New Lifecycle Script Vs Previous: postinstall added in 1.1.1 vs 1.1.0: "playwright install chromium"

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

Availability ledger

available

high
Last checked
highRisk
45Score
1.1.1Version
Status history (1 event)
  1. newavailable · risk high · score 45 · status changed

Evidence

Static findings

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

SeverityKindPathDetailPoints
highNew Lifecycle Script Vs Previouspackage.jsonpostinstall added in 1.1.1 vs 1.1.0: "playwright install chromium"40
highNew Account With Lifecycle Hookpackage.jsonpackage first published 6 day(s) ago, 4 total version(s), has lifecycle hook25
Show all 3 findings (low-signal and informational)
SeverityKindPathDetailPoints
highNew Lifecycle Script Vs Previouspackage.jsonpostinstall added in 1.1.1 vs 1.1.0: "playwright install chromium"40
highNew Account With Lifecycle Hookpackage.jsonpackage first published 6 day(s) ago, 4 total version(s), has lifecycle hook25
lowInstall-time lifecycle scriptpackage.jsonpostinstall="playwright install chromium"5

Manifest

Package metadata

Scripts17
  • buildyarn clean && tsc -p tsconfig.json && chmod +x dist/index.js
  • build:startyarn build && npx .
  • cleannode -e "require('fs').rmSync('dist', {recursive:true,force:true})"
  • devtsx src/index.ts
  • formatprettier --write .
  • format:checkprettier --check .
  • install:browsersnpx playwright install chromium
  • linteslint .
  • lint-stagedlint-staged
  • lint:fixeslint . --fix
  • logintsx src/index.ts --login
  • postinstallplaywright install chromium
  • preparehusky
  • prepublishOnlyyarn build
  • startnode dist/index.js
  • testnode --import tsx --test test/**/*.test.ts
  • test:published-packagesh ./scripts/test-published-package.sh
Dependencies3
  • @modelcontextprotocol/sdk^1.27.1
  • playwright^1.57.0
  • zod^4.3.6