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
- 93
- First published
- Feb 2026
- Publisher
- boudra
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":["@getpaseo/[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":["@getpaseo/[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
Scripts9
buildtsc -p tsconfig.json --incremental falsebuild:cleannpm run clean && npm run buildcleannode ../../scripts/clean-package-dist.mjsprepacknpm run build:cleantestnpm run test:localtest:e2enpm run test:localtest:e2e:lifecyclenpx tsx tests/e2e/agent-lifecycle.test.tstest:localtsx tests/run-all.tstypechecktsgo --noEmit
Dependencies10
@clack/prompts^1.0.0@getpaseo/client0.1.97-beta.2@getpaseo/protocol0.1.97-beta.2@getpaseo/server0.1.97-beta.2chalk^5.3.0commander^12.0.0mime-types^2.1.35tree-kill^1.2.2ws^8.14.2yaml^2.8.4