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: 1,670Niche · −30% score
Versions published: 124
First published: Apr 2026
Publisher: bom0792

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

Publisherbom0792

Artifact bytes1,202,413

Previous version0.8.4

Published2026-06-17T02:09:40.408Z

SHA-25615d3ad9833aa9c4b9c69d905e5e1706cf72012d52bbf158a23a59d4cdfa39a90

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

12h agoLast checked

reviewRisk

10Score

0.8.5Version

Status history (1 event)

new → available12h ago · risk review · score 10 · 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/src/runtime/async-runner.ts	matched "AWS_ACCESS_KEY"	5
low	Credential file access	package/src/utils/env-filter.ts	matched "AWS_ACCESS_KEY"	5
low	Credential file access	package/src/runtime/sensitive-paths.ts	matched ".config/gcloud"	5

Manifest

Package metadata

Scripts17

benchnode scripts/run-bench.mjs
bench:capturenode scripts/run-bench.mjs && node -e "require('node:fs').copyFileSync('test/bench/results.json','test/bench/baseline.json')"
bench:checknode scripts/bench-check.mjs
build:bundlenode scripts/build-bundle.mjs
checknpm run ci
check:lazy-importsnode scripts/check-lazy-imports.mjs
cinpm run typecheck && npm run check:lazy-imports && npm test && npm pack --dry-run
profile:startupnode scripts/profile-startup.mjs
smoke:pipi install .
smoke:releasenode scripts/release-smoke.mjs
testnpm run test:unit && npm run test:integration
test:changednode scripts/test-changed.mjs
test:integrationnode scripts/test-runner.mjs --test-concurrency=1 --test-timeout=120000 test/integration/*.test.ts
test:newtsx --test --test-concurrency=4 --test-timeout=30000 --test-force-exit test/unit/*.test.ts
test:unitnode scripts/test-runner.mjs --test-concurrency=4 --test-timeout=180000 --test-force-exit test/unit/*.test.ts
test:watchtsx --watch --test --test-concurrency=4 --test-timeout=30000 --test-force-exit test/unit/*.test.ts
typechecktsc --noEmit && node --experimental-strip-types -e "await import('./index.ts'); console.log('strip-types import ok')"

Dependencies7

@sinclair/typebox^0.34.49
acorn^8.16.0
ajv^8.20.0
cli-highlight^2.1.11
diff^5.2.0
jiti^2.7.0
typebox^1.1.38