PkgRadar

Package evidence

@prosopo/[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
93Mature · −50% score
First published
Sep 2023
Publisher
christaylor

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":["@prosopo/[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":["@prosopo/[email protected]"],"fail_on":"review"}'
Publisherchristaylor
Artifact bytes43,283
Previous version3.2.4
Published2026-01-14T17:01:12.808Z
SHA-2569630f7038908e0cbfec81a180e6a5f3a3a7d0bcadd46b13d25fd2c36c5bd782a

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

Scripts8
  • buildnpm run build:cross-env -- --mode ${NODE_ENV:-development}
  • build:cjsNODE_ENV=${NODE_ENV:-development}; vite build --config vite.cjs.config.ts --mode $NODE_ENV
  • build:cross-envvite build --config vite.esm.config.ts
  • build:tsctsc --build --verbose
  • cleandel-cli --verbose dist tsconfig.tsbuildinfo
  • clinode ./dist/js/cli.js
  • testNODE_ENV=${NODE_ENV:-test}; npx vitest run --config ./vite.test.config.ts
  • typechecktsc --project tsconfig.types.json
Dependencies5
  • @noble/hashes1.8.0
  • dotenv16.4.5
  • ip-address10.0.1
  • lodash4.17.21
  • seedrandom3.0.5