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
- 430
- First published
- Apr 2026
- Publisher
- clawos_dev
Recommended action
Looks clean — keep monitoringNo high-signal indicators in the stored static report. PkgRadar will re-check on the next ingest pass.
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":["@clawos-dev/[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":["@clawos-dev/[email protected]"],"fail_on":"review"}'Why flagged
What the scanner saw
No high-signal static finding in the saved report.
Not observed: package install, lifecycle script execution, or sandbox execution. PkgRadar only inspects on-disk artifacts.
Availability ledger
available
Status history (1 event)
- new → available · risk low · score 0 · status changed
Evidence
Static findings
No findings stored for this release.
Manifest
Package metadata
Scripts8
buildtsup && node scripts/copy-defaults.mjsdepcruisedepcruise --config .dependency-cruiser.cjs srcdevtsx src/cli.tsdev:watchtsx watch --clear-screen=false src/cli.tstestvitest runtest:changedvitest run --changed origin/releasetest:watchvitesttypechecktsc -p tsconfig.json --noEmit
Dependencies6
@lydell/node-pty1.2.0-beta.12@modelcontextprotocol/sdk^1.29.0@xterm/addon-serialize^0.14.0@xterm/headless^6.0.0jszip^3.10.1undici^6