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
- 2
- First published
- Jun 2026
- Publisher
- gurgena02
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":["@gurge/[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":["@gurge/[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
Scripts4
buildnx buildlintnx lintprebuildnx prebuild:workerstestnx test
Dependencies22
@coral-xyz/anchor^0.31.0@solana/spl-token^0.4.14@solana/wallet-adapter-react^0.15.39@solana/web3.js^1.98.4async-mutex^0.4.0axios^1.6.8bs58^6.0.0buffer6.0.3circomlibjs-hinkal-fork^0.0.3dotenv^16.4.5ethers^6.15.0idb-keyval6.2.1libsodium-wrappers^0.8.2lodash^4.17.21multiformats^13.4.2node-forge^1.3.1process0.11.10snarkjs0.7.5tronweb^6.2.0tweetnacl^1.0.3ua-parser-js^1.0.37uuid^9.0.1