PkgRadar

Package evidence

[email protected]

Credential file access: matched ".npmrc"

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
340Mature · −50% score
First published
Mar 2022
Publisher
GitHub ActionsTrusted automation · −70% score

Effective trust discount applied: −70% (max across signals — discounts don’t stack). New install-lifecycle deltas vs the previous release would clear the discount.

Recommended action

Review before promoting

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

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":["[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":["[email protected]"],"fail_on":"review"}'
PublisherGitHub Actions
Artifact bytes1,544,742
Previous version4.0.0
Published2026-06-11T14:09:20.453Z
SHA-25694317bd56d7a2f0e5710a61f79c655709e80fcd04beb9d03b2f98936b68f8a1a

Why flagged

What the scanner saw

Credential file access: matched ".npmrc"

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

Availability ledger

available

review
Last checked
reviewRisk
1Score
4.1.0Version
Status history (1 event)
  1. new → available · risk review · score 1 · status changed

Evidence

Static findings

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

No high-signal findings — see all findings below.

Show all 2 findings (low-signal and informational)
SeverityKindPathDetailPoints
lowCredential file accesspackage/build/client/assets/util-Cy1DhIdh.jsmatched ".npmrc"5
lowLarge Javascript Payloadpackage/build/server/assets/server-build-CZoDK47O.js2612379 bytes0

Manifest

Package metadata

Scripts38
  • buildcross-env NODE_ENV=production npm run build-vite && npm run build-cli
  • build-clicross-env NODE_ENV=production tsdown --env.NODE_ENV=production
  • build-cli:devcross-env NODE_ENV=development tsdown --env.NODE_ENV=development
  • build-vitereact-router build
  • build:devcross-env NODE_ENV=development npm run build-vite && npm run build-cli:dev
  • changesetbunx @changesets/cli && git add .changeset && git commit -m "chore: add changeset"
  • checkreact-router typegen && npm run knip && npm run lint && npm run format:check
  • check:writereact-router typegen && npm run knip:write && npm run lint:fix && npm run format:write
  • cleannpx -y rimraf build .react-router .cache .temp cli.mjs cli.js cli.cjs
  • commitcz
  • devbun dev:portless
  • dev:bunNODE_ENV=development bun --bun ./src/cli.ts
  • dev:nodecross-env NODE_ENV=development tsx --env-file-if-exists=.env --env-file-if-exists=.env.local ./src/cli.ts
  • dev:portlessbunx --bun portless proxy start --no-tls && bunx --bun portless git-truck bun dev:bun
  • format:checkprettier --check src scripts e2e
  • format:writeprettier --log-level warn --write src scripts e2e
  • knipknip
  • knip:writeknip --fix
  • linteslint --cache
  • lint:fixeslint --fix --cache
  • prepublishOnlynpm run clean && npm run build
  • pretest:e2enpm run build
  • pretest:e2e:headednpm run build
  • pub-expnode ./scripts/publish-experimental
  • pub-prenpm version prerelease && npm publish --tag next
  • pub-premajornpm version premajor && npm publish --tag next
  • pub-preminornpm version preminor && npm publish --tag next
  • pub-prepatchnpm version prepatch && npm publish --tag next
  • releasebun run build && bunx @changesets/cli publish
  • startcross-env NODE_ENV=production node . --env-file-if-exists=.env --env-file-if-exists=.env.local
  • …and 8 more.
Dependencies1
  • @duckdb/node-api1.5.1-r.1