PkgRadar

Package evidence

@keruyun/[email protected]

Install Lifecycle Remote Or Exec: postinstall="node -e \"console.log('安装完成')\""

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
494
Versions published
13
First published
May 2026
Publisher
keruyun

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":["@keruyun/[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":["@keruyun/[email protected]"],"fail_on":"high"}'
Publisherkeruyun
Artifact bytes186,447
Previous version1.0.9
Published2026-05-28T02:54:22.640Z
SHA-2562077fc0a40d42b131e99625df406b9c77b49542ba4eb095ccba94fcfd4533928

Why flagged

What the scanner saw

New Lifecycle Script Vs Previous: postinstall added in 1.1.0 vs 1.0.9: "node -e \"console.log('安装完成')\""

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

Availability ledger

available

high
Last checked
highRisk
75Score
1.1.0Version
Status history (2 events)
  1. availableavailable · risk high · score 75 · status available -> available, risk high -> high, score 45 -> 75
  2. 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.0 vs 1.0.9: "node -e \"console.log('安装完成')\""40
highInstall Lifecycle Remote Or Execpackage.jsonpostinstall="node -e \"console.log('安装完成')\""30
Show all 3 findings (low-signal and informational)
SeverityKindPathDetailPoints
highNew Lifecycle Script Vs Previouspackage.jsonpostinstall added in 1.1.0 vs 1.0.9: "node -e \"console.log('安装完成')\""40
highInstall Lifecycle Remote Or Execpackage.jsonpostinstall="node -e \"console.log('安装完成')\""30
lowInstall-time lifecycle scriptpackage.jsonpostinstall="node -e \"console.log('安装完成')\""5

Manifest

Package metadata

Scripts19
  • betatnpm publish --tag beta --force-publish-registry
  • buildrm -rf dist && tsc -b && rm -rf dist/pack dist/test dist/run
  • changelogconventional-changelog -p angular -i CHANGELOG.md -s
  • commitgit-cz
  • cpcp -f ./bin/kry-cli /Users/lh/.real/.bin/node/bin/kry-cli
  • dev./bin/dev.js
  • docnode dist/schema/gen.js
  • lint:fix-scripteslint --fix . --ext js,jsx,ts,tsx
  • lint:fix-stylestylelint "**/*.less" --fix
  • lint:scripteslint . --ext js,jsx,ts,tsx
  • lint:stylestylelint "**/*.less"
  • packnode dist/pack/index.js
  • postinstallnode -e "console.log('安装完成')"
  • precommitlint-staged
  • releaseyarn build && tnpm publish
  • rmrm -f /Users/lh/.real/.bin/node/bin/kry-cli
  • testvitest run
  • tsctsc --watch
  • wbcp -f /Users/lh/.kry-cli/comment-v1.json /Users/lh/.real/users/user-048911581b50b8719511c585c3a6f77f/.kry-cli/comment-v1.json
Dependencies6
  • @oclif/core^4
  • @puppeteer/browsers^3.0.3
  • dayjs^1.11.20
  • fs-extra^11.3.5
  • puppeteer-core^25.0.4
  • zod^4.4.3