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,079Niche · −30% score
- Versions published
- 172Mature · −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 monitoringNo 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"}'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
Status history (1 event)
- 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.jsonbuild: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.jsonclientcd client && pnpm startclient:fspeccd client && VITE_PSYCHIC_ENV=test BROWSER=none pnpm startconsoletsx ./test-app/src/conf/repl.tsdevnodemon --quiet --no-stdinformatpnpm prettier . --writefspecvitest run --config=./spec/features/vite.config.tsgpsytsx ./global-cli/main.tslintpnpm eslint --no-warn-ignored "src/**/*.ts" "spec/**/*.ts" "test-app/**/*.ts" && pnpm prettier . --checkprepackpnpm buildpsyNODE_ENV=${NODE_ENV:-test} pnpm psytspsyjsnode ./dist/test-app/src/cli/index.jspsytsNODE_ENV=${NODE_ENV:-test} tsx ./test-app/src/cli/index.tstypes:esm:tracerm -rf dist && tsc -p ./tsconfig.esm.build.json --generateTrace ./typetrace --diagnostics && pnpm analyze-trace ./typetrace --skipMillis 100 --forceMillis 300uspecvitest --config ./spec/unit/vite.config.ts
Dependencies4
ajv^8.17.1ajv-formats^3.0.1fast-json-stringify^6.3.0yoctocolors^2.1.1