PkgRadar

Package evidence

openrag==0.5.0

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.

Versions published
93Established · −30% score
First published
Oct 2025

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

Block this update

Static evidence trips multiple high-signal indicators. Quarantine the release until the publisher validates the change or you can rule out the indicators below.

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":["openrag==0.5.0"],"fail_on":"high"}'

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":["openrag==0.5.0"],"fail_on":"high"}'
Publisherunknown
Artifact bytes7,267,406
Previous versionnone
Published2026-05-29T13:15:18
SHA-2562b0b30a9388699fb00aeb08ac2f171515f02a7020305b0df58d973ff3f302c9f

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

high
Last checked
highRisk
59Score
0.5.0Version
Status history (1 event)
  1. newavailable · risk high · score 59 · status changed

Evidence

Static findings

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

SeverityKindPathDetailPoints
highCredential file accessopenrag-0.5.0/src/tui/managers/env_manager.pymatched "aws_access_key"30
mediumRemote Payloadopenrag-0.5.0/src/tui/utils/startup_checks.pymatched "curl "12
mediumCredential file accessopenrag-0.5.0/src/connectors/connection_manager.pymatched "aws_secret_access_key"10
Show all 10 findings (low-signal and informational)
SeverityKindPathDetailPoints
highCredential file accessopenrag-0.5.0/src/tui/managers/env_manager.pymatched "aws_access_key"30
mediumRemote Payloadopenrag-0.5.0/src/tui/utils/startup_checks.pymatched "curl "12
mediumCredential file accessopenrag-0.5.0/src/connectors/connection_manager.pymatched "aws_secret_access_key"10
lowCredential file accessopenrag-0.5.0/src/api/upload.pymatched "AWS_ACCESS_KEY"5
lowCredential file accessopenrag-0.5.0/src/connectors/aws_s3/api.pymatched "AWS_ACCESS_KEY"5
lowCredential file accessopenrag-0.5.0/src/connectors/aws_s3/auth.pymatched "AWS_ACCESS_KEY"5
lowCredential file accessopenrag-0.5.0/src/connectors/aws_s3/support.pymatched "AWS_ACCESS_KEY"5
lowCredential file accessopenrag-0.5.0/src/connectors/ibm_cos/auth.pymatched "aws_access_key"5
lowCredential file accessopenrag-0.5.0/src/tui/config_fields.pymatched "aws_access_key"5
lowCredential file accessopenrag-0.5.0/src/tui/_assets/docker-compose.ymlmatched "AWS_ACCESS_KEY"3