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
- 36
- Versions published
- 9
- First published
- May 2026
- Publisher
- kamalnrf
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":["@quireco/[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":["@quireco/[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
Scripts7
buildvp pack && node scripts/prepare-package-json.mjs && node scripts/verify-package.mjscheckvp checkdevvp pack --watchprepublishOnlyvp check && node scripts/verify-package.mjsquirenode dist/quire.mjsquire:localQUIRE_API_URL=http://localhost:3000 node dist/quire.mjstestvp test
Dependencies8
@clack/prompts^1.4.0@earendil-works/pi-ai^0.74.2@earendil-works/pi-coding-agent^0.74.2@sinclair/typebox^0.34.49agent-browser^0.27.0citty^0.2.2nanoid^3.3.12picocolors^1.1.1