Package evidence

@scallop-io/[email protected]

Remote Payload: matched "cUrl "

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.

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

Block this update

Static evidence trips multiple high-signal indicators. Quarantine the release until the publisher validates the change or you can rule out the indicators below.

Inspect tarball Add to CI gate

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":["@scallop-io/[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":["@scallop-io/[email protected]"],"fail_on":"high"}'

PublisherGitHub Actions

Artifact bytes29,808

Previous version0.4.2

Published2026-05-24T20:33:37.179Z

SHA-25650d74b01d2acf09c8ca974b28dcc2e77def5dce7b1f86e56120c61f09239cda6

Why flagged

What the scanner saw

New Lifecycle Script Vs Previous: prepare added in 0.4.3 vs 0.4.2: "husky install"

Not observed: package install, lifecycle script execution, or sandbox execution. PkgRadar only inspects on-disk artifacts.

Availability ledger

available

high

20d agoLast checked

highRisk

68Score

0.4.3Version

Status history (1 event)

new → available20d ago · risk high · score 68 · status changed

Evidence

Static findings

3 static · 1 from release diff · showing high-signal first.

Severity	Kind	Path	Detail	Points
high	New Lifecycle Script Vs Previous	package.json	prepare added in 0.4.3 vs 0.4.2: "husky install"	40
medium	Remote Payload	package/src/config.ts	matched "cUrl "	12
medium	Remote Payload	package/src/toolkit/DeepBookMarginToolkit.ts	matched "cUrl "	12

Show all 4 findings (low-signal and informational)

Severity	Kind	Path	Detail	Points
high	New Lifecycle Script Vs Previous	package.json	prepare added in 0.4.3 vs 0.4.2: "husky install"	40
medium	Remote Payload	package/src/config.ts	matched "cUrl "	12
medium	Remote Payload	package/src/toolkit/DeepBookMarginToolkit.ts	matched "cUrl "	12
low	Install-time lifecycle script	package.json	prepare="husky install"	4

Manifest

Package metadata

Scripts16

buildpnpm run build:prod
build:devtsup
build:prodtsup --env.NODE_ENV production
build:watchtsc --watch
cleanrm -rf dist
example:toolkittsx src/examples/toolkit-demo.ts
formatprettier --write "src/**/*.ts"
format:checkprettier --check "src/**/*.ts"
format:fixprettier --ignore-path 'dist/* docs/*' --write '**/*.{ts,json,md}'
linteslint src --ext .ts
lint:fixeslint src --ext .ts --fix
preparehusky install
prepublishOnlypnpm run clean && pnpm run build:prod
testvitest
test:coveragevitest --coverage
test:watchvitest --watch

Dependencies5

@mysten/bcs1.9.2
@mysten/deepbook-v31.2.2
@mysten/sui1.45.2
bignumber.js9.3.1
dotenv17.2.3