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: 13
Versions published: 64Established · −30% score
First published: Dec 2025
Publisher: frasan00

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 tarball Add 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"}'

Publisherfrasan00

Artifact bytes858,678

Previous version0.0.64

Published2026-06-03T19:48:01.696Z

SHA-256efdcd7eca64cccec87fe1576f0af214108fb06561ec9afe4e133323360949bfb

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

14d agoLast checked

reviewRisk

15Score

0.0.65Version

Status history (1 event)

new → available14d ago · risk review · score 15 · status changed

Evidence

Static findings

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

No high-signal findings — see all findings below.

Show all 3 findings (low-signal and informational)

Severity	Kind	Path	Detail	Points
low	Credential file access	package/lib/index.cjs	matched "AWS_ACCESS_KEY"	5
low	Credential file access	package/lib/cli.js	matched "AWS_ACCESS_KEY"	5
low	Credential file access	package/lib/index.js	matched "AWS_ACCESS_KEY"	5

Manifest

Package metadata

Scripts38

benchmarkbash run-benchmarks.sh --quick
benchmark:allbash run-benchmarks.sh --all
benchmark:bunUSE_BUN=1 bash run-benchmarks.sh --quick
benchmark:denoUSE_DENO=1 bash run-benchmarks.sh --quick
benchmark:oldtsx test/benchmark/index.ts
benchmark:pluginsbash run-benchmarks.sh --plugins
benchmark:quicktsx test/benchmark/quick-bench.ts
benchmark:runtimebash run-benchmarks.sh --runtime
benchmark:scenariostsx test/benchmark/all-scenarios.ts
buildrm -rf lib && docker compose exec -T node yarn tsup
build:prodrm -rf lib && docker compose exec -T node yarn tsup --minify
build:testrm -rf lib && docker compose exec -T node yarn tsup && rm -rf lib
build:worktreerm -rf lib && docker compose -f docker-compose.worktree.yml exec -T node yarn tsup
devtsx watch test/server/index.ts
dev:bunbun run --watch test/server/index.ts
dev:denodeno task dev
docker:worktree:downdocker compose -f docker-compose.worktree.yml down
docker:worktree:updocker compose -f docker-compose.worktree.yml up -d --build node redis sqs postgres localstack mqtt azurite mailcatcher
docker:worktree:up:bundocker compose -f docker-compose.worktree.yml up -d --build bun redis sqs postgres localstack mqtt azurite mailcatcher
docker:worktree:up:denodocker compose -f docker-compose.worktree.yml up -d --build deno redis sqs postgres localstack mqtt azurite mailcatcher
formatdocker compose exec -T node yarn prettier --write "**/*.ts"
linteslint .
lint:fixeslint . --fix
lint:worktreedocker compose -f docker-compose.worktree.yml exec -T node yarn eslint .
preparehusky
testdocker compose exec -T node yarn vitest --run
test:alldocker compose exec -T node yarn vitest --run && docker compose exec -T bun bun test && docker compose exec -T deno deno task test
test:all:worktreedocker compose -f docker-compose.worktree.yml exec -T node yarn vitest --run && docker compose -f docker-compose.worktree.yml exec -T bun bun test && docker compose -f docker-compose.worktree.yml exec -T deno deno task test
test:bundocker compose exec -T bun bun test
test:bun:worktreedocker compose -f docker-compose.worktree.yml exec -T bun bun test
…and 8 more.

Dependencies3

ajv^8.18.0
fast-json-stringify^6.3.0
pino^10.3.1