PkgRadar

Package evidence

[email protected]

no findings

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
155
Versions published
57
First published
Feb 2026
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

Looks clean — keep monitoring

No high-signal indicators in the stored static report. PkgRadar will re-check on the next ingest pass.

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 bytes455,020
Previous version2.0.1
Published2026-06-10T20:31:58.595Z
SHA-256d1474a2b4e255a94d262c2037ca18fa30a9b2731a4bde666caf7c45bad6d5827

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

review
Last checked
reviewRisk
30Score
2.0.2Version
Status history (2 events)
  1. available → available · risk review · score 30 · status available -> available, risk low -> review, score 0 -> 30
  2. new → available · risk low · score 0 · status changed

Evidence

Static findings

No findings stored for this release.

Manifest

Package metadata

Scripts12
  • benchcargo bench --features bench-md4c && node benchmark/report.mjs
  • buildpnpm build:wasm && node wasm/build.mjs
  • build:devPATH="$PWD/.wasm-tools/bin:$HOME/.cargo/bin:$PATH" cargo build -p ironmark-wasm --target wasm32-unknown-unknown && PATH="$PWD/.wasm-tools/bin:$HOME/.cargo/bin:$PATH" wasm-bindgen --target bundler --out-dir wasm/pkg --out-name ironmark target/wasm32-unknown-unknown/debug/ironmark.wasm && node wasm/build.mjs
  • build:wasmPATH="$PWD/.wasm-tools/bin:$HOME/.cargo/bin:$PATH" cargo build -p ironmark-wasm --profile release-wasm --target wasm32-unknown-unknown && PATH="$PWD/.wasm-tools/bin:$HOME/.cargo/bin:$PATH" wasm-bindgen --target bundler --out-dir wasm/pkg --out-name ironmark target/wasm32-unknown-unknown/release-wasm/ironmark.wasm && wasm-opt --enable-bulk-memory -O3 wasm/pkg/ironmark_bg.wasm -o wasm/pkg/ironmark_bg.wasm
  • checkcargo fmt --check && oxlint && oxfmt --check .
  • cleanrm -rf wasm/pkg .wasm-tools
  • fmtcargo fmt && oxfmt --write .
  • lintoxlint
  • releasesemantic-release
  • release:drysemantic-release --dry-run
  • setup:wasmPATH="$HOME/.cargo/bin:$PATH" rustup target add wasm32-unknown-unknown && TMPDIR=/tmp PATH="$HOME/.cargo/bin:$PATH" cargo install wasm-bindgen-cli --version 0.2.123 --locked --root .wasm-tools
  • testcargo test --offline