PkgRadar

Package evidence

@brpvieira/[email protected]

Suspicious Publish Context: {"package_age_days":0,"publisher":"brpvieira","burst_same_day":0,"burst_week":0,"lure":null,"version_anomaly":false,"new_account":true}

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
1
First published
Jun 2026
Publisher
brpvieira

Recommended action

Review before promoting

Mixed signals: the package has indicators worth reading before allowing the update in automated dependency flows.

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":["@brpvieira/[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":["@brpvieira/[email protected]"],"fail_on":"review"}'
Publisherbrpvieira
Artifact bytes53,840
Previous versionnone
Published2026-06-15T01:41:44.589Z
SHA-256f20259c167d7d8c5c4b46065216a6d41bf53b8ce04e8f86647f1feb4cb3fddea

Why flagged

What the scanner saw

Suspicious Publish Context: {"package_age_days":0,"publisher":"brpvieira","burst_same_day":0,"burst_week":0,"lure":null,"version_anomaly":false,"new_account":true}

Not observed: package install, lifecycle script execution, or sandbox execution. PkgRadar only inspects on-disk artifacts.

Availability ledger

available

review
Last checked
reviewRisk
10Score
1.0.0Version
Status history (1 event)
  1. newavailable · risk review · score 10 · status changed

Evidence

Static findings

1 static · 0 from release diff · showing high-signal first.

SeverityKindPathDetailPoints
mediumSuspicious Publish Contextmanifest{"package_age_days":0,"publisher":"brpvieira","burst_same_day":0,"burst_week":0,"lure":null,"version_anomaly":false,"new_account":true}10

Manifest

Package metadata

Scripts20
  • buildtsup
  • cleanrm -fr ./dist/* && rm -f .vltx*
  • clinpm run build && ./dist/bin/cli.js
  • commitcommit
  • coveragevitest run --coverage
  • debug-clinpm run build && node --inspect-brk ./dist/bin/cli.js
  • docsnpm run docs:build-ts && npm run docs:generate-md && npm run docs:clean
  • docs:build-tstsc --project tsconfig.json --outDir ./dist-docs
  • docs:cleanrm -fr ./dist-docs/*
  • docs:generate-mdjsdoc2md ./dist-docs/**/*.js > API.md
  • linttsc --noEmit && eslint .
  • lint:fixeslint --fix .
  • postbuildchmod +x dist/bin/cli.js
  • preparehusky
  • prepublishOnlynpm run test && npm run build
  • prereleasenpm test
  • releasestandard-version
  • testnpm run lint && vitest run
  • test:debugvitest --inspect-brk --no-file-parallelism
  • test:fixnpm run lint:fix && vitest run
Dependencies2
  • dotenv^17.4.2
  • yargs^17.7.2