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
713
Versions published
8
First published
May 2026
Publisher
0kim0bos

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"}'
Publisher0kim0bos
Artifact bytes149,152
Previous version0.1.6
Published2026-06-12T02:00:42.520Z
SHA-25627701db81158198a80c5b89348836ce39f69215e4531799e4ecf9243c3733fd3

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
10Score
0.1.7Version
Status history (1 event)
  1. new → available · risk review · score 10 · 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/bin/yam.jsmatched "aws_access_key"5
lowCredential file accesspackage/src/bin/yam.tsmatched "aws_access_key"5

Manifest

Package metadata

Scripts33
  • budgetnode ./dist/bin/yam.js budget
  • buildnpm run clean && tsc -p tsconfig.json
  • cleannode -e "require('node:fs').rmSync('dist',{recursive:true,force:true})"
  • cli-smokenode ./scripts/cli-smoke.mjs
  • detectnode ./dist/bin/yam.js detect
  • dist:freshnessnode ./scripts/check-dist-freshness.mjs
  • doctornode ./dist/bin/yam.js doctor
  • examplesnode ./dist/bin/yam.js examples
  • forbidden-names:checknode ./scripts/check-forbidden-names.mjs
  • init-projectnode ./dist/bin/yam.js init-project
  • install:skillsnode ./dist/bin/yam.js install
  • listnode ./dist/bin/yam.js list
  • measurenode ./dist/bin/yam.js measure
  • memorynode ./dist/bin/yam.js memory
  • packnode ./dist/bin/yam.js pack
  • pack:dry-runnpm pack --dry-run
  • package-boundary:checknode ./scripts/check-package-boundary.mjs
  • prepacknpm run verify:self
  • preparenpm run build
  • prepublishOnlynpm run verify:self
  • proofnode ./dist/bin/yam.js proof
  • publish:drynpm publish --dry-run --access public
  • registry:checknode ./scripts/check-registry-version.mjs
  • release:checknpm run typecheck && npm run forbidden-names:check && npm run verify:self && npm run dist:freshness && npm run package-boundary:check && npm run registry:check && npm run cli-smoke
  • safetynode ./dist/bin/yam.js safety
  • statusnode ./dist/bin/yam.js status
  • templatenode ./dist/bin/yam.js template
  • toolsnode ./dist/bin/yam.js tools
  • tune-lognode ./dist/bin/yam.js tune-log
  • typechecktsc -p tsconfig.json --noEmit
  • …and 3 more.