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
- 4,019Niche · −30% score
- Versions published
- 207Mature · −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
Scripts14
buildecho "building cjs..." && rm -rf dist && pnpm tsc -p ./tsconfig.cjs.build.json && echo "building esm..." && pnpm tsc -p ./tsconfig.esm.build.json && cp -r src/types/ dist/types/src/types/build:test-apprm -rf dist && echo "building test app to esm..." && pnpm tsc -p ./tsconfig.esm.build.test-app.json && echo "building test app to cjs..." && pnpm tsc -p ./tsconfig.cjs.build.test-app.jsonconsoleDREAM_CORE_DEVELOPMENT=1 pnpm dream db:integrity-check && NODE_ENV=${NODE_ENV:-test} DREAM_CORE_DEVELOPMENT=1 tsx ./test-app/app/conf/repl.tsdreamDREAM_CORE_DEVELOPMENT=1 pnpm dreamtsdream:jsnode --experimental-modules dist/test-app/cli/index.jsdreamtsNODE_ENV=${NODE_ENV:-test} tsx ./test-app/cli/index.tsformatpnpm prettier . --writelintpnpm eslint --no-warn-ignored "src/**/*.ts" "spec/**/*.ts" "test-app/**/*.ts" && pnpm prettier . --checkprepackpnpm build && pnpm dream build:docsspecDREAM_CORE_DEVELOPMENT=1 pnpm dream db:integrity-check && DREAM_CORE_DEVELOPMENT=1 DREAM_CORE_SPEC_RUN=1 vitesttypes:cjs:tracerm -rf dist && pnpm tsc -p ./tsconfig.cjs.build.json --generateTrace ./typetrace --diagnostics && pnpm analyze-trace ./typetrace --skipMillis 100 --forceMillis 300types:cjs:trace-test-apprm -rf dist && pnpm tsc -p ./tsconfig.cjs.trace.json --generateTrace ./typetrace --diagnostics && pnpm analyze-trace ./typetrace --skipMillis 100 --forceMillis 300types:esm:tracerm -rf dist && pnpm tsc -p ./tsconfig.esm.build.json --generateTrace ./typetrace --diagnostics && pnpm analyze-trace ./typetrace --skipMillis 100 --forceMillis 300types:esm:trace-test-apprm -rf dist && pnpm tsc -p ./tsconfig.esm.trace.json --generateTrace ./typetrace --diagnostics && pnpm analyze-trace ./typetrace --skipMillis 100 --forceMillis 300
Dependencies4
colorette^2.0.20dotenv^17.2.3luxon^3.7.2yoctocolors^2.1.1