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: 205Mature · −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 tarball Add 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 bytes882,356

Previous version2.11.1

Published2026-05-20T20:25:34.959Z

SHA-256757af419eb0443bbf68d5f00f79c8e3a4347d0830f83f50c34e84ede54f19fea

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

8d agoLast checked

lowRisk

0Score

2.11.2Version

Status history (1 event)

new → available8d ago · 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.json
consoleDREAM_CORE_DEVELOPMENT=1 pnpm dream db:integrity-check && NODE_ENV=${NODE_ENV:-test} DREAM_CORE_DEVELOPMENT=1 tsx ./test-app/app/conf/repl.ts
dreamDREAM_CORE_DEVELOPMENT=1 pnpm dreamts
dream:jsnode --experimental-modules dist/test-app/cli/index.js
dreamtsNODE_ENV=${NODE_ENV:-test} tsx ./test-app/cli/index.ts
formatpnpm prettier . --write
lintpnpm eslint --no-warn-ignored "src/**/*.ts" "spec/**/*.ts" "test-app/**/*.ts" && pnpm prettier . --check
prepackpnpm build && pnpm dream build:docs
specDREAM_CORE_DEVELOPMENT=1 pnpm dream db:integrity-check && DREAM_CORE_DEVELOPMENT=1 DREAM_CORE_SPEC_RUN=1 vitest
types:cjs:tracerm -rf dist && pnpm tsc -p ./tsconfig.cjs.build.json --generateTrace ./typetrace --diagnostics && pnpm analyze-trace ./typetrace --skipMillis 100 --forceMillis 300
types:cjs:trace-test-apprm -rf dist && pnpm tsc -p ./tsconfig.cjs.trace.json --generateTrace ./typetrace --diagnostics && pnpm analyze-trace ./typetrace --skipMillis 100 --forceMillis 300
types:esm:tracerm -rf dist && pnpm tsc -p ./tsconfig.esm.build.json --generateTrace ./typetrace --diagnostics && pnpm analyze-trace ./typetrace --skipMillis 100 --forceMillis 300
types: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.20
dotenv^16.4.5
luxon^3.7.2
yoctocolors^2.1.1