PkgRadar

Package evidence

@sap/[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.

Versions published
236Mature · −50% score
First published
Jun 2020
Publisher
sap_extncrepos

Effective trust discount applied: 50% (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":["@sap/[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":["@sap/[email protected]"],"fail_on":"review"}'
Artifact bytes6,748,249
Previous version8.0.0
Published2020-06-15T19:40:53.898Z
SHA-256dd24d049a1ccd2bcd9878fc3eda2522e7122fd4276768bc1fe9d46490a4d2fe3

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
3Score
8.1.0Version
Status history (1 event)
  1. newavailable · risk review · score 3 · 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 access./node_modules/@sap/audit-logging/node_modules/aws4/aws4.jsmatched "AWS_ACCESS_KEY"5
lowCredential file access./node_modules/aws4/aws4.jsmatched "AWS_ACCESS_KEY"5

Manifest

Package metadata

Scripts1
  • testmake test
Dependencies2
  • options>=0.0.5
  • ultron1.0.x