Package evidence
@algorandfoundation/[email protected]
Suspicious Publish Context: {"package_age_days":4,"publisher":"GitHub Actions","burst_same_day":0,"burst_week":0,"lure":{"kind":"token_affix","target":"open"},"version_anomaly":false,"new_account":false}
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
- 3
- First published
- Jun 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
Review before promotingMixed signals: the package has indicators worth reading before allowing the update in automated dependency flows.
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":["@algorandfoundation/[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":["@algorandfoundation/[email protected]"],"fail_on":"review"}'Why flagged
What the scanner saw
Suspicious Publish Context: {"package_age_days":4,"publisher":"GitHub Actions","burst_same_day":0,"burst_week":0,"lure":{"kind":"token_affix","target":"open"},"version_anomaly":false,"new_account":false}
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 review · score 10 · status changed
Evidence
Static findings
1 static · 0 from release diff · showing high-signal first.
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| medium | Suspicious Publish Context | manifest | {"package_age_days":4,"publisher":"GitHub Actions","burst_same_day":0,"burst_week":0,"lure":{"kind":"token_affix","target":"open"},"version_anomaly":false,"new_account":false} | 10 |
Manifest
Package metadata
Scripts8
buildnode scripts/bundle.mjs && tsc -p tsconfig.build.json && node scripts/bundle.mjs --flatten-dtsinstall:pluginnode scripts/bundle.mjs && tsc -p tsconfig.build.json && node scripts/bundle.mjs --flatten-dts && TGZ="$(node scripts/pack-plugin.mjs --pack-destination /tmp | tail -n1)" && openclaw plugins install "file:$TGZ" --dangerously-force-unsafe-install --force && npm rebuild --prefix "${OPENCLAW_HOME:-$HOME/.openclaw}/extensions/ac2-open-claw-reference" node-datachannel @napi-rs/keyring && openclaw plugins enable ac2-open-claw-referencereleasepackage-releaserrelease:dry-runpackage-releaser --dry-runtestvitest runtest:watchvitesttype-checktsc --noEmituninstall:pluginopenclaw plugins uninstall ac2-open-claw-reference
Dependencies9
@algorandfoundation/ac2-sdk1.0.0-canary.1@algorandfoundation/keystore1.0.0-canary.16@algorandfoundation/liquid-client1.0.0-canary.8@napi-rs/keyring^1.3.0@sinclair/typebox^0.32.0@tanstack/store^0.9.1node-datachannel^0.32.3qrcode-terminal^0.12.0socket.io-client^4.7.5