PkgRadar

Package evidence

@rue-js/[email protected]

no findings

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":["@rue-js/[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":["@rue-js/[email protected]"],"fail_on":"review"}'
Publisherxiangminliu1990
Artifact bytes1,488,626
Previous version0.0.39
Published2026-05-18T23:29:25.668Z
SHA-256e0edcc67b95bb4d4c38fecf827d4f3b838c482dcf00858516e6be2243604e720

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

low
Last checked
lowRisk
0Score
0.1.1Version
Status history (1 event)
  1. new → available · risk low · score 0 · status changed

Evidence

Static findings

No findings stored for this release.

Manifest

Package metadata

Scripts8
  • buildcargo fmt --all && cargo build --release --target wasm32-wasip1
  • checkcargo check
  • docscargo doc --no-deps
  • fmtcargo fmt
  • formatcargo fmt --all
  • postbuildnode -e "const fs=require('fs');fs.copyFileSync('target/wasm32-wasip1/release/swc_plugin_rue.wasm','swc-plugin-rue.wasm')"
  • testcargo test
  • test-coveragecargo llvm-cov --html --open