PkgRadar

Package evidence

@saasbase-io/[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":["@saasbase-io/[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":["@saasbase-io/[email protected]"],"fail_on":"high"}'
Publishermsoltany
Artifact bytes18,631
Previous version2.2.9
Published2026-05-24T07:36:57.297Z
SHA-256df623e8e7148b97bf36c50ebb9364749224695a21d989aa31f2a74cb5e76ab1f

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
2.3.0Version
Status history (1 event)
  1. new → available · risk high · score 30 · status changed

Related candidates

Linked campaigns and clusters

Publisher / release actor burststale

msoltany

2 members · evidence strength 50

Evidence

Static findings

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

SeverityKindPathDetailPoints
highCredential file accesspackage/.github/workflows/publish_elements.yamlmatched "GITHUB_TOKEN"30

Manifest

Package metadata

Scripts1
  • buildvite build
Dependencies2
  • @lit/react^1.0.8
  • url^0.11.4