PkgRadar

Package evidence

[email protected]

Credential file access: matched "AWS_ACCESS_KEY"

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
7,733Niche · −30% score
Versions published
228
First published
Jan 2026
Publisher
kernelvoid

Effective trust discount applied: −30% (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"}'
Publisherkernelvoid
Artifact bytes366,102
Previous version2.8.7
Published2026-06-10T15:13:50.486Z
SHA-25646ecf7691ffbab30b2a1367d9e38738866ae54d1751764a71b3a09f9169b44d4

Why flagged

What the scanner saw

Credential file access: matched "AWS_ACCESS_KEY"

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

Availability ledger

available

review
Last checked
reviewRisk
7Score
2.8.8Version
Status history (1 event)
  1. new → available · risk review · score 7 · 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/config/resolve.jsmatched "AWS_ACCESS_KEY"5
lowCredential file accesspackage/dist/infrastructure/backup/s3BackupConfig.jsmatched "AWS_ACCESS_KEY"5

Manifest

Package metadata

Scripts18
  • benchbun run bench/throughput.ts && bun run bench/latency.ts
  • bench:comparebun run bench/comparison/run.ts
  • bench:internalbun run benchmarks/index.ts
  • bench:latencybun run bench/latency.ts
  • bench:throughputbun run bench/throughput.ts
  • buildbun build --compile --minify src/main.ts --outfile dist/bunqueue
  • build:libtsc -p tsconfig.build.json
  • checkbun run typecheck && bun run lint && bun run format:check
  • devbun run --watch src/main.ts
  • formatprettier --write "src/**/*.ts"
  • format:checkprettier --check "src/**/*.ts"
  • linteslint src/
  • lint:fixeslint src/ --fix
  • preparegit config core.hooksPath .husky
  • prepublishOnlybun run build:lib
  • startbun run src/main.ts
  • testBUNQUEUE_EMBEDDED=1 bun test
  • typechecktsc --noEmit
Dependencies2
  • croner10.0.1
  • msgpackr^1.11.8