Package evidence

@mainsail/[email protected]

Install-time lifecycle script: postinstall="node scripts/postinstall.mjs"

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: 552
Versions published: 60Mature · −50% score
First published: Jul 2024
Publisher: itsanametwo

Effective trust discount applied: −50% (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":["@mainsail/[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":["@mainsail/[email protected]"],"fail_on":"high"}'

Publisheritsanametwo

Artifact bytes108,433

Previous version0.0.1-evm.52

Published2026-06-12T12:14:26.099Z

SHA-2563aee51d51d1988bf93e1c426e9b8a06b6ee3a2800709cbc2fac78816f7e76f3a

Why flagged

What the scanner saw

New Lifecycle Script Vs Previous: postinstall added in 0.0.1-evm.53 vs 0.0.1-evm.52: "node scripts/postinstall.mjs"

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

Availability ledger

available

high

9h agoLast checked

highRisk

45Score

0.0.1-evm.53Version

Status history (1 event)

new → available9h ago · risk high · score 45 · status changed

Evidence

Static findings

1 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 0.0.1-evm.53 vs 0.0.1-evm.52: "node scripts/postinstall.mjs"	40

Show all 2 findings (low-signal and informational)

Severity	Kind	Path	Detail	Points
high	New Lifecycle Script Vs Previous	package.json	postinstall added in 0.0.1-evm.53 vs 0.0.1-evm.52: "node scripts/postinstall.mjs"	40
low	Install-time lifecycle script	package.json	postinstall="node scripts/postinstall.mjs"	5

Manifest

Package metadata

Scripts12

artifactsnapi artifacts
build-napinapi build --platform --output-dir ./ --manifest-path bindings/Cargo.toml --release
build-napi:debugnapi build --platform --output-dir ./ --manifest-path bindings/Cargo.toml
build-rspnpm run clean && pnpm run build-napi
cleanrm -f index.js && rm -f index.d.ts && rm -f evm.*.node && rm -rf target
postinstallnode scripts/postinstall.mjs
releasepnpm publish --access public
release:preparenapi prepublish -t pnpm --skip-optional-publish --no-gh-release
testcargo test --release
test:coveragemkdir -p coverage && cargo llvm-cov --lcov --output-path coverage/lcov.info --remap-path-prefix
test:coverage:htmlmkdir -p coverage && cargo llvm-cov --html --output-dir coverage/ --remap-path-prefix
versionnapi version

Dependencies1

@napi-rs/cli3.6.2

Optional dependencies2

@mainsail/evm-linux-arm64-gnu0.0.1-evm.53
@mainsail/evm-linux-x64-gnu0.0.1-evm.53