Package evidence
@extra-wallet/[email protected]
Install-time lifecycle script: postinstall="patch-package"
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
- 87
- Versions published
- 8
- First published
- Jan 2026
- Publisher
- paul2905
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":["@extra-wallet/[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":["@extra-wallet/[email protected]"],"fail_on":"high"}'Why flagged
What the scanner saw
New Lifecycle Script Vs Previous: postinstall added in 1.0.0-beta.5 vs 1.0.0-beta.4: "patch-package"
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 high · score 45 · status changed
Evidence
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 1.0.0-beta.5 vs 1.0.0-beta.4: "patch-package" | 40 |
Show all 3 findings (low-signal and informational)
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| high | New Lifecycle Script Vs Previous | package.json | postinstall added in 1.0.0-beta.5 vs 1.0.0-beta.4: "patch-package" | 40 |
| low | Install-time lifecycle script | package.json | postinstall="patch-package" | 5 |
| low | Large Javascript Payload | package/build/browser/cardano_serialization_lib-CUQYtJ2C.js | 4009608 bytes | 0 |
Manifest
Package metadata
Scripts15
buildyarn build:browser && yarn build:nodebuild:browservite buildbuild:graphnpx madge src/ --ts-config ./tsconfig.json --warning --extensions ts,tsx --image dependency-graph.svgbuild:nodetsc --project ./tsconfig.build.json && npx tsc-alias --project ./tsconfig.build.json --resolve-full-paths --resolve-full-extension .jslintyarn lint:prettify:check && yarn lint:fs && yarn lint:type && yarn lint:jslint:fsnpx tsx scripts/check-filesystem.script.tslint:jseslint .lint:prettifyprettier ./ --write "**/*.{ts,json,md}"lint:prettify:checkprettier --check "**/*.{ts,tsx,json,md,css,html}"lint:typenpx tsc --noEmitpostinstallpatch-packageprepublishyarn lint && npm publish --tag beta --dry-run > publish-logs.log 2>&1 && yarn testpublish:packagenpm publish --registry https://registry.npmjs.org --tag betastarttsx src/index.tstestvitest run --coverage --testTimeout=10000
Dependencies25
@aptos-labs/ts-sdk6.0.0@binance-chain/javascript-sdk4.2.2@emurgo/cardano-serialization-lib-nodejs14.1.2@mysten/sui2.1.0@noble/curves2.0.1@noble/hashes2.0.1@polkadot/util-crypto14.0.1@scure/bip321.6.2@scure/sr255191.0.0@ton/core0.62.0@ton/crypto3.3.0@ton/ton16.1.0bchaddrjs0.5.2bech322.0.0bip325.0.0bip393.1.0bitcoinjs-lib7.0.1bs586.0.0bs58check4.0.0ecpair3.0.0ed25519-hd-key1.3.0ethereumjs-util7.1.5got14.6.5tiny-secp256k12.2.3xrpl4.4.3