Package evidence

@midscene/[email protected]

Install-time lifecycle script: postinstall="fetch-scrcpy-server 3.1"

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: 9,068Niche · −30% score
Versions published: 1,145Mature · −50% score
First published: Mar 2025
Publisher: zhoushaw

Effective trust discount applied: −50% (max across signals — discounts don’t stack). New install-lifecycle deltas vs the previous release would clear the discount.

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

Publisherzhoushaw

Artifact bytes7,095,555

Previous version0.14.3

Published2025-04-14T11:43:12.752Z

SHA-256b88e9256421eeedbd50ddcb2a9e719196376918d0ea2af714015e19d213c8a8e

Why flagged

What the scanner saw

New Lifecycle Script Vs Previous: postinstall added in 0.14.4-beta-20250414114024.0 vs 0.14.3: "fetch-scrcpy-server 3.1"

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

Availability ledger

available

high

35h agoLast checked

highRisk

45Score

0.14.4-beta-20250414114024.0Version

Status history (1 event)

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

Evidence

Static findings

3 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.14.4-beta-20250414114024.0 vs 0.14.3: "fetch-scrcpy-server 3.1"	40

Show all 4 findings (low-signal and informational)

Severity	Kind	Path	Detail	Points
high	New Lifecycle Script Vs Previous	package.json	postinstall added in 0.14.4-beta-20250414114024.0 vs 0.14.3: "fetch-scrcpy-server 3.1"	40
low	Install-time lifecycle script	package.json	postinstall="fetch-scrcpy-server 3.1"	5
low	Large Javascript Payload	package/static/static/js/507.441b8b92.js	2410817 bytes	0
low	Large Javascript Payload	package/static/static/js/index.879b04b8.js	4493090 bytes	0

Manifest

Package metadata

Scripts8

buildmodern build -c ./modern.config.ts
build:watchmodern build -w -c ./modern.config.ts
devmodern dev
dev:servernpm run build && ./bin/playground
postinstallfetch-scrcpy-server 3.1
testvitest --run
test:aiMIDSCENE_CACHE=true npm run test
test:uvitest --run -u

Dependencies14

@midscene/core0.14.4-beta-20250414114024.0
@midscene/shared0.14.4-beta-20250414114024.0
@midscene/web0.14.4-beta-20250414114024.0
@yume-chan/adb^1.1.0
@yume-chan/adb-scrcpy^1.1.0
@yume-chan/adb-server-node-tcp^1.1.0
@yume-chan/fetch-scrcpy-server^1.0.0
@yume-chan/scrcpy^1.1.0
@yume-chan/stream-extra^1.0.0
appium-adb12.12.1
cors2.8.5
express^4.21.2
open10.1.0
socket.io^4.8.1