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
- 1
- First published
- Jun 2026
- Publisher
- darkarmy
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":["@interfold/[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":["@interfold/[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
buildtsupcleanrm -rf distcompile:circuitsbash scripts/compile-circuits.shdevtsup --watchprebuildpnpm -C ../interfold-contracts build && pnpm -C ../../ wasm:build && pnpm compile:circuitsprereleasepnpm clean && pnpm buildpretestpnpm compile:circuitsreleasepnpm publish --access=publictestvitest --run
Dependencies10
@aztec/bb.js3.0.0-nightly.20260102@interfold/contracts0.2.0@interfold/wasm0.2.0@noir-lang/noir_js1.0.0-beta.16comlink^4.4.2viem2.30.6vite-plugin-top-level-await^1.5.0vite-plugin-wasm^3.4.1vitest^1.6.1web-worker^1.5.0