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.

Weekly downloads
62,639Mainstream · −50% score
Versions published
21Mature · −50% score
First published
Apr 2011
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.

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"}'
Artifact bytes3,611,040
Previous version0.6.0-beta.12
Published2026-06-11T16:30:29.673Z
SHA-256d3b8ad6f0aabc132774e6014fd4190561c10b11b35bad094bb2546314fa4f604

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
0.6.0-beta.13Version
Status history (1 event)
  1. newavailable · 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/dist/src/internal/nitro/dev-runtime-source-snapshot.jsmatched ".npmrc"5
lowObfuscation Densitypackage/dist/src/compiled/gray-matter/index.jshigh encoded/escaped-token density0

Manifest

Package metadata

Scripts15
  • buildpnpm run build:js && node ./scripts/copy-docs.mjs && node ./scripts/stamp-version-tokens.mjs
  • build:compilednode ./scripts/vendor-compiled.mjs
  • build:jspnpm run build:compiled && pnpm run clean && pnpm run build:types && node ./scripts/copy-compiled-assets.mjs && node ./scripts/build-rolldown.mjs
  • build:typespnpm run build:compiled && tsgo -p tsconfig.build.json
  • check:web-templatenode src/setup/build.ts --check
  • cleannode -e "fs.rmSync('dist', { recursive: true, force: true })"
  • devpnpm run build:compiled && tsgo -p tsconfig.dev.json --watch --preserveWatchOutput
  • generate:web-templatenode src/setup/build.ts --write
  • testpnpm run test:unit && pnpm run test:integration
  • test:e2evitest run --config vitest.e2e.config.ts
  • test:integrationpnpm run build:js && vitest run --config vitest.integration.config.ts
  • test:scenariopnpm run build:compiled && vitest run --config vitest.scenario.config.ts
  • test:unitpnpm run build:compiled && vitest run --config vitest.unit.config.ts
  • test:watchpnpm run build:compiled && vitest --config vitest.unit.config.ts
  • typecheckpnpm run check:web-template && pnpm run build:compiled && tsgo -p tsconfig.json --noEmit
Dependencies1
  • nitro3.0.260610-beta