PkgRadar

Package evidence

[email protected]

Credential file access: matched "GITHUB_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.

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":"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"}'
Publishershridhartl
Artifact bytes48,844
Previous version0.4.4
Published2026-05-23T01:41:23.343Z
SHA-2561b0e3d56bdeb1a2821c062ddcb1742340a390cd311f4cda40fdc071ddb70b991

Why flagged

What the scanner saw

Credential file access: matched "GITHUB_TOKEN"

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

Availability ledger

available

high
Last checked
highRisk
42Score
0.4.7Version
Status history (1 event)
  1. new → available · risk high · score 42 · status changed

Related candidates

Linked campaigns and clusters

Publisher / release actor burststale

shridhartl

4 members · evidence strength 72

Evidence

Static findings

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

SeverityKindPathDetailPoints
highCredential file accesspackage/remove-CR4-OO3A.jsmatched "GITHUB_TOKEN"30
mediumRemote Payloadpackage/remove-CR4-OO3A.jsmatched "raw.githubusercontent.com"12

Manifest

Package metadata

Dependencies3
  • chalk5.6.2
  • prompts2.4.2
  • sass^1.100.0