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.
- Weekly downloads
- 213
- Versions published
- 2
- First published
- Jun 2026
- Publisher
- merceas
- External confirmation
- MAL-2026-6509OSV match · pinned to high regardless of other signals
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":["@merceas/[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":["@merceas/[email protected]"],"fail_on":"high"}'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 (2 events)
- available → available · risk high · score 0 · status available -> available, risk low -> high, score 0 -> 0
- new → available · risk low · score 0 · status changed
Evidence
Static findings
No findings stored for this release.
Manifest
Package metadata
Dependencies13
@coral-xyz/anchor-errors^0.31.1@coral-xyz/borsh^0.31.1@noble/hashes^1.3.1@solana/web3.js^1.69.0bn.js^5.1.2bs58^4.0.1buffer-layout^1.2.2camelcase^6.3.0cross-fetchnpm:@merceas/[email protected]eventemitter3^4.0.7pako^2.0.3superstruct^0.15.4toml^3.0.0