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.

Weekly downloads
40
Versions published
114Mature · −50% score
First published
Jun 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 bytes30,568
Previous version3.2.10
Published2026-01-14T17:00:45.698Z
SHA-256434fe3e71d67eefccf9185ce88eae6b5102f3b950a25375ee84b21110d0758ce

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.3.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

Scripts11
  • 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
  • bundleNODE_ENV=${NODE_ENV:-development}; vite build --config vite.config.ts --mode $NODE_ENV
  • bundle:webpackNODE_ENV=${NODE_ENV:-development}; MODE=${MODE:-$NODE_ENV}; webpack build --config webpack.config.cjs --mode $MODE
  • cleandel-cli --verbose dist tsconfig.tsbuildinfo
  • serveNODE_ENV=${NODE_ENV:-development}; vite serve --config vite.serve.config.ts --mode $NODE_ENV --host
  • startNODE_ENV=${NODE_ENV:-development}; vite serve --mode $NODE_ENV --host
  • testNODE_ENV=${NODE_ENV:-test}; npx vitest run --config ./vite.test.config.ts
  • typechecktsc --project tsconfig.types.json
Dependencies16
  • @emotion/cache11.11.0
  • @emotion/react11.11.1
  • @prosopo/dotenv3.0.33
  • @prosopo/locale3.1.28
  • @prosopo/procaptcha-common2.9.23
  • @prosopo/procaptcha-frictionless2.8.31
  • @prosopo/procaptcha-pow2.8.31
  • @prosopo/procaptcha-react2.9.27
  • @prosopo/types3.8.0
  • @prosopo/util3.2.5
  • @prosopo/widget-skeleton2.7.13
  • dotenv16.4.5
  • fast-glob3.3.2
  • jsdom25.0.0
  • react18.3.1
  • react-dom18.3.1