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
- 7
- First published
- May 2026
- Publisher
- GitHub ActionsTrusted automation · −70% score
Effective trust discount applied: −70% (max across signals — discounts don’t stack). New install-lifecycle deltas vs the previous release would clear the discount.
Recommended action
Block this updateStatic evidence trips multiple high-signal indicators. Quarantine the release until the publisher validates the change or you can rule out the indicators below.
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":["@circlesac/[email protected]"],"fail_on":"high"}'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":["@circlesac/[email protected]"],"fail_on":"high"}'Why flagged
What the scanner saw
New Lifecycle Script Vs Previous: postinstall added in 26.5.0 vs 0.0.0: "node bin/install.js"
1 candidate cluster(s) currently reference this release.
Not observed: package install, lifecycle script execution, or sandbox execution. PkgRadar only inspects on-disk artifacts.
Availability ledger
available
Status history (2 events)
- available → available · risk high · score 57 · status available -> available, risk high -> high, score 87 -> 57
- new → available · risk high · score 87 · status changed
Related candidates
Linked campaigns and clusters
GitHub Actions
110 members · evidence strength 84Install Lifecycle Remote Or Exec — postinstall="node bin/install.js"
12 members · evidence strength 87GitHub Actions
110 members · max score 283Evidence
Static findings
2 static · 1 from release diff · showing high-signal first.
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| high | New Lifecycle Script Vs Previous | package.json | postinstall added in 26.5.0 vs 0.0.0: "node bin/install.js" | 40 |
| medium | Remote Payload | package/bin/install.sh | matched "curl " | 12 |
Show all 3 findings (low-signal and informational)
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| high | New Lifecycle Script Vs Previous | package.json | postinstall added in 26.5.0 vs 0.0.0: "node bin/install.js" | 40 |
| medium | Remote Payload | package/bin/install.sh | matched "curl " | 12 |
| low | Install-time lifecycle script | package.json | postinstall="node bin/install.js" | 5 |
Manifest
Package metadata
Scripts7
buildbun build --compile --external playwright --outfile=dist/clova src/index.tsdevbun run src/index.tslintnpx @circlesac/lint --allpostinstallnode bin/install.jspre-mergebun run lint && bun run type-check && bun run test && bun run buildtestvitest runtype-checknpx tsc --noEmit
Dependencies1
citty^0.2.1