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
- May 2026
- Publisher
- vk.tiamo
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":["@jpool/[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":["@jpool/[email protected]"],"fail_on":"review"}'Why flagged
What the scanner saw
Remote Payload: matched "curL "
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 12 · status changed
Evidence
Static findings
1 static · 0 from release diff · showing high-signal first.
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| medium | Remote Payload | package/dist/index.iife.js | matched "curL " | 12 |
Manifest
Package metadata
Scripts7
buildtsc && cross-env NODE_ENV=production rollup -cbuild:programcargo build-sbf --manifest-path=../program/Cargo.tomlcleanrimraf ./distdevtsc -w & cross-env NODE_ENV=development rollup -c -wlinteslint --max-warnings 0 .lint:fixeslint . --fixtestjest
Dependencies7
@coral-xyz/borsh^0.29.0@solana/spl-token^0.3.10@solana/web3.js^1.87.6bn.js^5.2.1buffer^6.0.3buffer-layout^1.2.2superstruct^1.0.3