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
- 137
- First published
- Apr 2026
- Publisher
- dohapark81
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":["@crewx/[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":["@crewx/[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
Scripts4
buildtsc -p tsconfig.jsonlintecho 'CLI lint pending' && exit 0testvitest run --config ./vitest.config.tstest:watchvitest --config ./vitest.config.ts
Dependencies13
@crewx/adapter-slack0.1.4@crewx/chromex0.1.0-rc.39@crewx/cron0.1.10-rc.37@crewx/doc0.1.8@crewx/memory0.1.23-rc.19@crewx/sdk0.8.8-rc.38@crewx/search0.1.9@crewx/shared0.0.5@crewx/skill0.1.20@crewx/wbs0.1.10-rc.32@crewx/wi0.1.10@crewx/workflow0.3.22-rc.19better-sqlite3*