PkgRadar

Package evidence

[email protected]

Install-time lifecycle script: postinstall="tsdown"

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
7
Versions published
5
First published
Aug 2025
Publisher
productdevbook
External confirmation
MAL-2025-191134OSV match · pinned to high regardless of other signals

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 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":"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":["[email protected]"],"fail_on":"high"}'
Publisherproductdevbook
Artifact bytes13,531
Previous version0.1.0
Published2026-02-27T08:20:08.668Z
SHA-2569b3f090b04b853ae070bfb37d7f16850daa61bfbbe824bdfe0143c361c770eb1

Why flagged

What the scanner saw

New Lifecycle Script Vs Previous: postinstall added in 0.2.0 vs 0.1.0: "tsdown"

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

Availability ledger

available

high
Last checked
highRisk
45Score
0.2.0Version
Status history (1 event)
  1. new → available · risk high · score 45 · status changed

Evidence

Static findings

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

SeverityKindPathDetailPoints
highNew Lifecycle Script Vs Previouspackage.jsonpostinstall added in 0.2.0 vs 0.1.0: "tsdown"40
Show all 2 findings (low-signal and informational)
SeverityKindPathDetailPoints
highNew Lifecycle Script Vs Previouspackage.jsonpostinstall added in 0.2.0 vs 0.1.0: "tsdown"40
lowInstall-time lifecycle scriptpackage.jsonpostinstall="tsdown"5

Manifest

Package metadata

Scripts6
  • buildtsdown
  • cleanrm -rf dist
  • devtsdown --watch
  • postinstalltsdown
  • releasebun run build && bun publish --no-git-checks --access public
  • typechecktsc --noEmit