PkgRadar

Package evidence

[email protected]

Credential file access: matched "NPM_TOKEN"

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":["[email protected]"],"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":["[email protected]"],"fail_on":"high"}'
Artifact bytes5,929
Previous version2.1.2
Published2023-04-03T13:37:48.789Z
SHA-256b91b1f4e2fd60d6cd218dad67f1b8aefb24c77bcc78ed456a1047f2ac61b05ab

Why flagged

What the scanner saw

Credential file access: matched "NPM_TOKEN"

Not observed: package install, lifecycle script execution, or sandbox execution. PkgRadar only inspects on-disk artifacts.

Availability ledger

available

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

Evidence

Static findings

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

SeverityKindPathDetailPoints
highCredential file accesspackage/.github/workflows/npm-publish.ymlmatched "NPM_TOKEN"30

Manifest

Package metadata

Scripts1
  • testecho "Error: no test specified" && exit 1
Dependencies5
  • combine-source-map0.8.0
  • commander2.20.3
  • fs-extra8.1.0
  • glob7.1.6
  • javascript-obfuscator^4.0.2