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
649
Versions published
48
First published
Feb 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 bytes348,127
Previous version0.18.2
Published2026-06-08T14:27:35.252Z
SHA-2568d9854410538e448ba2fd5fbd102658e1e2a48480aa315b21c7cfb06a274fec0

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.18.3Version
Status history (1 event)
  1. newavailable · risk review · score 10 · status changed

Evidence

Static findings

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

No high-signal findings — see all findings below.

Show all 7 findings (low-signal and informational)
SeverityKindPathDetailPoints
lowCredential file accesspackage/dist/scope/aws.jsmatched "AWS_ACCESS_KEY"5
lowCredential file accesspackage/dist/mcp/classify.jsmatched "AWS_ACCESS_KEY"5
lowCredential file accesspackage/dist/backends/gcp-sm.jsmatched "GOOGLE_APPLICATION_CREDENTIALS"5
lowCredential file accesspackage/dist/init.jsmatched ".aws/"5
lowCredential file accesspackage/dist/patterns.jsmatched "AWS_ACCESS_KEY"5
lowCredential file accesspackage/dist/scan.jsmatched "AWS_ACCESS_KEY"5
lowCredential file accesspackage/dist/commands/vault.jsmatched "AWS_SECRET_ACCESS_KEY"5

Manifest

Package metadata

Scripts5
  • buildtsc
  • cleanrm -rf dist
  • devtsc --watch
  • prepublishOnlynpm run build && npm test
  • testvitest run
Dependencies4
  • @opena2a/cli-ui0.4.0
  • @opena2a/credential-patterns0.1.2
  • @opena2a/telemetry0.1.2
  • canonicalize2.1.0
Optional dependencies3
  • @nanomind/engine^0.1.1
  • @nanomind/guard^0.1.1
  • @opena2a/aim-core>=0.2.0