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.

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"}'
Publishermasa-dev
Artifact bytes15,260
Previous version0.8.0
Published2026-05-24T06:11:30.972Z
SHA-256fb7be05ed101c10a31065ee2f768358bd1240425159bbdd6d7096470e44da359

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
30Score
0.8.2Version
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/package.jsonmatched "GITHUB_TOKEN"30

Manifest

Package metadata

Scripts7
  • buildtsc
  • devtsc --watch
  • prepublishOnlybun run build
  • releaseGITHUB_TOKEN="$(gh auth token)" node ./node_modules/release-it/bin/release-it.js
  • testvitest run
  • test:watchvitest
  • type-checktsc -p . --noEmit