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
6,449Niche · −30% score
Versions published
79
First published
May 2026
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 bytes335,759
Previous version0.1.110
Published2026-06-01T14:28:33.246Z
SHA-25636fe029a5423d857a6fe55d6e286a9d3add791baa6a7e4ecc285dae8f639bd3d

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
4Score
0.1.111Version
Status history (1 event)
  1. newavailable · risk review · score 4 · 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)
SeverityKindPathDetailPoints
lowCredential file accesspackage/dist/src/redact.jsmatched "aws_access_key"5
lowCredential file accesspackage/dist/src/rules.jsmatched ".ssh/"5
lowCredential file accesspackage/dist/src/sensitiveAudit.jsmatched ".npmrc"5

Manifest

Package metadata

Scripts6
  • buildtsc -p tsconfig.json
  • checknpm run test && node dist/src/cli.js doctor . --format json > /tmp/trace-to-skill-doctor.json && node dist/src/cli.js lint-agents . --format json > /tmp/trace-to-skill-agents-lint.json && node dist/src/cli.js analyze fixtures --format json > /tmp/trace-to-skill-smoke.json && node dist/src/cli.js usage-evidence fixtures --format json > /tmp/trace-to-skill-usage-evidence.json && node dist/src/cli.js issue-map fixtures/github-codex-issues-export.json --format json > /tmp/trace-to-skill-issue-map.json && node dist/src/cli.js duplicate-audit fixtures/codex-duplicate-audit.json --format json > /tmp/trace-to-skill-duplicate-audit.json && node dist/src/cli.js process-audit fixtures/safe-run.md --format json > /tmp/trace-to-skill-process-audit.json && node dist/src/cli.js checkpoint . --output /tmp/trace-to-skill-checkpoint --format json > /tmp/trace-to-skill-checkpoint.json && node dist/src/cli.js sensitive-audit . --format json > /tmp/trace-to-skill-sensitive-audit.json && node dist/src/cli.js lsp-audit . --format json > /tmp/trace-to-skill-lsp-audit.json && node dist/src/cli.js suggest fixtures --target agents-md > /tmp/trace-to-skill-suggest.md && node dist/src/cli.js demo --format json > /tmp/trace-to-skill-demo.json && node dist/src/cli.js benchmark --format json > /tmp/trace-to-skill-benchmark.json && node dist/src/cli.js scorecard . --format json > /tmp/trace-to-skill-scorecard.json && node dist/src/cli.js oss-brief . --format json > /tmp/trace-to-skill-oss-brief.json
  • cleanrm -rf dist coverage
  • prepacknpm run build
  • preparenpm run build
  • testnpm run build && node --test dist/tests/*.test.js