PkgRadar

Package evidence

[email protected]

Large Javascript Payload: 4439842 bytes

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
892
Versions published
26Established · −30% score
First published
Aug 2025
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

Review before promoting

Mixed signals: the package has indicators worth reading before allowing the update in automated dependency flows.

Inspect tarballAdd 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":["[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":["[email protected]"],"fail_on":"review"}'
PublisherGitHub Actions
Artifact bytes4,168,052
Previous version2.0.0-alpha.110
Published2026-05-26T23:40:12.321Z
SHA-2562dba05966d3721a55c3146babc0cbeb63adb39a85d804be79494836df5ef761a

Why flagged

What the scanner saw

Large Javascript Payload: 4439842 bytes

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

Availability ledger

available

review
Last checked
reviewRisk
6Score
2.0.0-alpha.111Version
Status history (1 event)
  1. new → available · risk review · score 6 · status changed

Evidence

Static findings

2 static · 0 from release diff · showing high-signal first.

SeverityKindPathDetailPoints
mediumLarge Javascript Payloadpackage/dist/alizarin.inline-full.js4439842 bytes10
mediumLarge Javascript Payloadpackage/dist/alizarin.inline.js4439819 bytes10

Manifest

Package metadata

Scripts20
  • benchNODE_OPTIONS='--experimental-wasm-modules' node benchmarks/compare.mjs
  • bench:wasmNODE_OPTIONS='--experimental-wasm-modules' vitest bench --run --config benchmarks/vitest.bench.wasm.config.js
  • buildnpm run build:wasm && echo '⚠ NAPI not built by default — run napi separately' && npm run build:js
  • build:allnpm run build:wasm && npm run build:js
  • build:jsNODE_OPTIONS='--experimental-wasm-modules' vite build && node scripts/create-inline.mjs && tsc -p tsconfig.build.json
  • build:releasenpm run build:wasm:release && npm run build:js
  • build:wasmwasm-pack build crates/alizarin-wasm --target web --out-dir ../../pkg --out-name alizarin --release
  • build:wasm:devwasm-pack build crates/alizarin-wasm --target web --out-dir ../../pkg --out-name alizarin --dev
  • build:wasm:releasenpm run build:wasm && wasm-opt -Os -o pkg/alizarin_bg.wasm pkg/alizarin_bg.wasm
  • devNODE_OPTIONS='--experimental-wasm-modules' vite serve .
  • linteslint js --ext .ts
  • prepublishOnlynpm run build:release
  • testNODE_OPTIONS='--experimental-wasm-modules' vitest --run && echo '⚠ NAPI tests not run by default — test napi separately'
  • test:allNODE_OPTIONS='--experimental-wasm-modules' vitest --run
  • test:uiNODE_OPTIONS='--experimental-wasm-modules' vitest --ui
  • test:watchNODE_OPTIONS='--experimental-wasm-modules' vitest
  • validateNODE_OPTIONS='--experimental-wasm-modules' node validate-graphs.mjs
  • validate:csvsNODE_OPTIONS='--experimental-wasm-modules' node scripts/validate-model-csvs.mjs
  • version:set./scripts/sync-version.sh
  • version:sync./scripts/sync-version.sh
Dependencies5
  • ajv^8.17.1
  • ajv-formats^3.0.1
  • geojson^0.5.0
  • uuid^11.1.0
  • wasm-opt^1.4.0