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
4,165Niche · −30% score
Versions published
63
First published
May 2026
Publisher
charliehu

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"}'
Publishercharliehu
Artifact bytes1,811,985
Previous version1.1.37
Published2026-06-03T09:24:52.261Z
SHA-256ee3197ed24bc12cbb02dc39d316587646ec6cdab85d7f62d1b112e9692050739

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
1.1.38Version
Status history (1 event)
  1. new → available · 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)
SeverityKindPathDetailPoints
lowCredential file accesspackage/dist/engine/audit/privacy_patterns.jsmatched "aws_access_key"5
lowCredential file accesspackage/dist/engine/audit/privacy_scanning.jsmatched "aws_access_key"5
lowCredential file accesspackage/dist/engine/pipeline/scope_controller.jsmatched "aws_access_key"5

Manifest

Package metadata

Scripts24
  • audit-depsnode scripts/audit_dependencies.mjs
  • buildnpm run clean && tsc && chmod +x dist/bin/soloforge.js
  • check:commentsnode scripts/check_chinese_comments.mjs
  • check:no-direct-consolenode scripts/check_no_direct_console.mjs
  • check:packnpm pack --dry-run 2>&1 | tee pack-output.txt && node scripts/check_npm_pack.mjs pack-output.txt
  • check:qualitynode scripts/check_lazy_patterns.mjs
  • cleanrm -rf dist
  • devtsc --watch
  • linttsc --noEmit && eslint src/ --max-warnings 0
  • lint:alltsc --noEmit && eslint src/ --max-warnings 0
  • lint:eslinteslint src/
  • lint:fulltsc --noEmit && eslint . --max-warnings 0
  • lint:teststsc -p tsconfig.test.json --noEmit
  • prepublishOnlynpm run build
  • startnode dist/index.js
  • testvitest run --reporter=verbose
  • test:coveragevitest run --coverage
  • test:e2eE2E=1 vitest run tests/e2e/ --reporter=verbose
  • test:unitvitest run --exclude tests/e2e/**
  • test:watchvitest
  • typechecktsc --noEmit
  • typecheck:teststsc -p tsconfig.test.json --noEmit
  • update-workflow-checksumnode -e "const {updateEmbeddedChecksum}=require('./dist/adapters/shared/workflow_template.js');console.log('新校验和:',updateEmbeddedChecksum(process.cwd()));"
  • validate-releasenpm run build && node scripts/validate_release_gate.mjs
Dependencies7
  • @modelcontextprotocol/sdk^1.12.0
  • chokidar^4.0.3
  • execa^9.5.2
  • gray-matter^4.0.3
  • handlebars^4.7.8
  • yaml^2.7.0
  • zod^3.23.0