PkgRadar

Package evidence

@liflig/[email protected]

Credential file access: matched "GITHUB_TOKEN"

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.

Publisher
GitHub ActionsTrusted automation · −70% score

Effective trust discount applied: 70% (max across signals — discounts don’t stack). New install-lifecycle deltas vs the previous release would clear the discount.

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":["@liflig/[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":["@liflig/[email protected]"],"fail_on":"high"}'
Artifact bytes65,385
Previous version1.1.157
Published2026-05-24T01:57:57.115Z
SHA-256b6caf46f145aeacc5533dff6ca4ff96bb02b317b05635d2d81d7e4c109e0b8fe

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
64Score
1.1.158Version
Status history (1 event)
  1. newavailable · risk high · score 64 · status changed

Related candidates

Linked campaigns and clusters

Repeated static TTPstale

Install Lifecycle Remote Or Exec — prepare="bun run build && husky"

3 members · evidence strength 72

Evidence

Static findings

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

SeverityKindPathDetailPoints
highCredential file accesspackage/.github/workflows/ci.yamlmatched "GITHUB_TOKEN"30
highInstall Lifecycle Remote Or Execpackage.jsonprepare="bun run build && husky"30
Show all 3 findings (low-signal and informational)
SeverityKindPathDetailPoints
highCredential file accesspackage/.github/workflows/ci.yamlmatched "GITHUB_TOKEN"30
highInstall Lifecycle Remote Or Execpackage.jsonprepare="bun run build && husky"30
lowInstall-time lifecycle scriptpackage.jsonprepare="bun run build && husky"4

Manifest

Package metadata

Scripts9
  • buildtsc
  • fmtbiome format --write
  • fmt:checkbiome format
  • lintbiome check
  • lint:fixbiome check --write
  • lint:fix-unsafebiome check --write --unsafe
  • preparebun run build && husky
  • semantic-releasesemantic-release
  • upgrade-depsbun update
Dependencies3
  • @aws-sdk/client-secrets-manager3.1051.0
  • @aws-sdk/client-sts3.1051.0
  • read5.0.1