PkgRadar

Package evidence

@burgan-tech/[email protected]

Install-time lifecycle script: postinstall="node setup.js && npm run sync-schema"

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
10
Versions published
9
First published
Aug 2025
Publisher
seal707

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":["@burgan-tech/[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":["@burgan-tech/[email protected]"],"fail_on":"high"}'
Publisherseal707
Artifact bytes18,124
Previous version0.0.4
Published2025-11-29T22:42:54.025Z
SHA-25692d172cb689b2108f049a4fb3059ea3d20079bcd0e3ebe675c9bb9062f8f2903

Why flagged

What the scanner saw

New Lifecycle Script Vs Previous: postinstall added in 0.0.5 vs 0.0.4: "node setup.js && npm run sync-schema"

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.0.5Version
Status history (1 event)
  1. newavailable · 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.0.5 vs 0.0.4: "node setup.js && npm run sync-schema"40
Show all 2 findings (low-signal and informational)
SeverityKindPathDetailPoints
highNew Lifecycle Script Vs Previouspackage.jsonpostinstall added in 0.0.5 vs 0.0.4: "node setup.js && npm run sync-schema"40
lowInstall-time lifecycle scriptpackage.jsonpostinstall="node setup.js && npm run sync-schema"5

Manifest

Package metadata

Scripts9
  • buildnode build.js
  • build:referencenode build.js -t reference
  • build:runtimenode build.js -t runtime
  • postinstallnode setup.js && npm run sync-schema
  • prepublishOnlynpm run sync-schema && npm run validate
  • setupnode setup.js
  • sync-schemanode sync-schema-version.js
  • testnode test.js
  • validatenode validate.js
Dependencies1
  • @burgan-tech/vnext-schema^0.0.23