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.

Versions published
173Mature · −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.

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":["@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"}'
Publisherb_l_u_e_j_a_d_e
Artifact bytes233,276
Previous version3.5.0
Published2026-06-16T16:51:18.697Z
SHA-2563055642ce7ee86956504196a9475e2da8a684a9557dd20a2f6a75acb2d0d1660

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.6.0Version
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

Scripts16
  • buildecho "building cjs..." && rm -rf dist && tsc -p ./tsconfig.cjs.build.json && echo "building esm..." && tsc -p ./tsconfig.esm.build.json
  • build:test-apprm -rf dist && echo "building test app to esm..." && tsc -p ./tsconfig.esm.build.test-app.json && echo "building test app to cjs..." && tsc -p ./tsconfig.cjs.build.test-app.json
  • clientcd client && pnpm start
  • client:fspeccd client && VITE_PSYCHIC_ENV=test BROWSER=none pnpm start
  • consoletsx ./test-app/src/conf/repl.ts
  • devnodemon --quiet --no-stdin
  • formatpnpm prettier . --write
  • fspecvitest run --config=./spec/features/vite.config.ts
  • gpsytsx ./global-cli/main.ts
  • lintpnpm eslint --no-warn-ignored "src/**/*.ts" "spec/**/*.ts" "test-app/**/*.ts" && pnpm prettier . --check
  • prepackpnpm build
  • psyNODE_ENV=${NODE_ENV:-test} pnpm psyts
  • psyjsnode ./dist/test-app/src/cli/index.js
  • psytsNODE_ENV=${NODE_ENV:-test} tsx ./test-app/src/cli/index.ts
  • types:esm:tracerm -rf dist && tsc -p ./tsconfig.esm.build.json --generateTrace ./typetrace --diagnostics && pnpm analyze-trace ./typetrace --skipMillis 100 --forceMillis 300
  • uspecvitest --config ./spec/unit/vite.config.ts
Dependencies4
  • ajv^8.17.1
  • ajv-formats^3.0.1
  • fast-json-stringify^6.3.0
  • yoctocolors^2.1.1