PkgRadar

Package evidence

@peterwangze/[email protected]

Obfuscation Density: high encoded/escaped-token density

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
21
First published
Apr 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

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":["@peterwangze/[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":["@peterwangze/[email protected]"],"fail_on":"review"}'
PublisherGitHub Actions
Artifact bytes487,839
Previous version1.9.0
Published2026-05-23T14:12:21.063Z
SHA-25600bb56c97655fd8ae7162c5897b32cf11af0df590b5d0981b6515707abefd644

Why flagged

What the scanner saw

Obfuscation Density: high encoded/escaped-token density

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

Availability ledger

available

review
Last checked
reviewRisk
7Score
1.10.0Version
Status history (1 event)
  1. new → available · risk review · score 7 · status changed

Evidence

Static findings

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

SeverityKindPathDetailPoints
mediumObfuscation Densitypackage/dist/cli.jshigh encoded/escaped-token density12
mediumRemote Payloadpackage/config/deploy/docker-compose.server.yamlmatched "wget "12

Manifest

Package metadata

Scripts16
  • buildnode scripts/build.js
  • devtsx watch src/cli.ts
  • install:local-releasepwsh -NoProfile -ExecutionPolicy Bypass -File scripts/install-local-release.ps1
  • prepublishOnlynpm run build
  • releasenpm run release:publish
  • release:cleanpwsh -NoProfile -ExecutionPolicy Bypass -File scripts/release-package.ps1 -Action clean
  • release:publishpwsh -NoProfile -ExecutionPolicy Bypass -File scripts/release-package.ps1 -Action publish
  • release:stagepwsh -NoProfile -ExecutionPolicy Bypass -File scripts/release-package.ps1 -Action stage
  • release:verifypwsh -NoProfile -ExecutionPolicy Bypass -File scripts/release-package.ps1 -Action verify
  • startnode dist/cli.js start
  • testvitest --exclude src/e2e/**
  • test:e2e:acceptancevitest --run src/e2e/cli-acceptance.test.ts
  • test:e2e:clivitest --run src/e2e/cli-e2e.test.ts
  • test:e2e:cli:entryvitest --run src/e2e/cli-e2e.test.ts -t "init --force generates|doctor can repair|start/status/stop work|code reuses|ui prints|setup can create a fresh config|setup can create a remote-service client config|setup can create a server deployment profile"
  • test:uivitest --run src/ui/workbench.dom.test.ts
  • verify:packagepwsh -NoProfile -ExecutionPolicy Bypass -File scripts/verify-package.ps1
Dependencies10
  • @fastify/static^8.2.0
  • @musistudio/llms^1.0.31
  • dotenv^16.4.7
  • js-yaml^4.1.0
  • json5^2.2.3
  • lru-cache^10.0.0
  • openurl^1.1.1
  • rotating-file-stream^3.2.7
  • tiktoken^1.0.21
  • uuid^11.1.0