PkgRadar

Package evidence

@rvoh/[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
2,639Niche · −30% score
Versions published
21Mature · −50% score
First published
Mar 2025
Publisher
b_l_u_e_j_a_d_e

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

Looks clean — keep monitoring

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

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":["@rvoh/[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":["@rvoh/[email protected]"],"fail_on":"review"}'
Artifact bytes14,427
Previous version3.1.0
Published2026-06-15T22:23:48.425Z
SHA-2568e76aedcbc8ee0c8655d1c4844061e57d4bde166d2121da4f472dfdb341e123d

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
3.2.0Version
Status history (1 event)
  1. newavailable · risk low · score 0 · status changed

Evidence

Static findings

No findings stored for this release.

Manifest

Package metadata

Scripts16
  • buildecho "building cjs..." && rm -rf dist && npx tsc -p ./tsconfig.cjs.build.json && echo "building esm..." && npx tsc -p ./tsconfig.esm.build.json
  • build:test-apprm -rf dist && echo "building test app to esm..." && npx tsc -p ./tsconfig.esm.build.test-app.json && echo "building test app to cjs..." && npx tsc -p ./tsconfig.cjs.build.test-app.json
  • clientpnpm --cwd=./client start
  • client:fspeccd client && BROWSER=none VITE_PSYCHIC_ENV=test pnpm start
  • devNODE_ENV=development tsx ./test-app/main.ts
  • formatpnpm prettier . --write
  • fspecvitest run --config=./spec/features/vite.config.ts
  • fspec:hangingvitest run --config=./spec/features/vite.config.ts --reporter=hanging-process
  • lintpnpm eslint --no-warn-ignored "src/**/*.ts" && pnpm prettier . --check
  • prepackpnpm build
  • psyNODE_ENV=${NODE_ENV:-test} pnpm psy:ts
  • psy:jsnode ./dist/test-app/src/cli/index.js
  • psy:tstsx ./test-app/src/cli/index.ts
  • uspecvitest --config ./spec/unit/vite.config.ts
  • wsNODE_ENV=development tsx ./test-app/ws.ts
  • ws:fspecNODE_ENV=test tsx ./test-app/ws.ts
Dependencies4
  • commander^14.0.2
  • dotenv^17.2.3
  • pluralize-esm^9.0.5
  • yoctocolors^2.1.1