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
- 46
- Versions published
- 11
- First published
- May 2026
- Publisher
- pswitala
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":["@curie-agent/[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":["@curie-agent/[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
Scripts6
buildtsc --project tsconfig.jsoncleannpx rimraf distdevtsc --watch --project tsconfig.jsonlinteslint src/testvitest runtypechecktsc --noEmit --project tsconfig.json
Dependencies12
@curie-agent/core0.3.0@curie-agent/daemon0.3.1@curie-agent/mcp0.3.0@curie-agent/protocol0.3.0@curie-agent/providers0.3.0@curie-agent/render0.3.0@curie-agent/tools0.3.0@curie-agent/tui0.3.0@curie-agent/wiki0.3.0@types/react^19.0.0ink^7.0.1react^19.2.5