Package evidence

@trysentinel/[email protected]

Install-time lifecycle script: postinstall="node postinstall.mjs"

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: 2
First published: Jun 2026
Publisher: among_robots

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 tarball Add 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":["@trysentinel/[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":["@trysentinel/[email protected]"],"fail_on":"high"}'

Publisheramong_robots

Artifact bytes194,286

Previous version0.1.0

Published2026-06-06T10:36:47.839Z

SHA-256ba8e3753000e098926de391f7ee5a1a6ee897b22af9c9e27564aa003a1adbeef

Why flagged

What the scanner saw

New Lifecycle Script Vs Previous: postinstall added in 0.1.1 vs 0.1.0: "node postinstall.mjs"

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

Availability ledger

available

high

3h agoLast checked

highRisk

45Score

0.1.1Version

Status history (1 event)

new → available3h ago · risk high · score 45 · status changed

Evidence

Static findings

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

Severity	Kind	Path	Detail	Points
high	New Lifecycle Script Vs Previous	package.json	postinstall added in 0.1.1 vs 0.1.0: "node postinstall.mjs"	40

Show all 2 findings (low-signal and informational)

Severity	Kind	Path	Detail	Points
high	New Lifecycle Script Vs Previous	package.json	postinstall added in 0.1.1 vs 0.1.0: "node postinstall.mjs"	40
low	Install-time lifecycle script	package.json	postinstall="node postinstall.mjs"	5

Manifest

Package metadata

Scripts11

buildtsc -p tsconfig.json
devtsx src/cli.ts
postinstallnode postinstall.mjs
prepublishOnlynpm run typecheck && npm run test:ci && rm -rf dist && tsc -p tsconfig.json --sourceMap false
servenode dist/cli.js serve
smokenpm run build && node dist/cli.js doctor && node dist/cli.js run specs/example.todomvc.json
startnode dist/cli.js
testvitest run
test:civitest run --exclude '**/*.live.test.ts'
test:watchvitest
typechecktsc --noEmit -p tsconfig.json

Dependencies9

@anthropic-ai/sdk^0.69.0
@modelcontextprotocol/sdk^1.29.0
axe-core^4.12.0
dotenv^16.4.7
pixelmatch^5.3.0
playwright^1.50.0
pngjs^7.0.0
yaml^2.7.0
zod^3.24.1