PkgRadar

Package evidence

@liflig/[email protected]

Credential file access: matched "aws_access_key"

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.

Weekly downloads
3,323Niche · −30% score
Versions published
406Mature · −50% score
First published
May 2020
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

Review before promoting

Mixed signals: the package has indicators worth reading before allowing the update in automated dependency flows.

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":"review"}'

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":"review"}'
Artifact bytes343,367
Previous version3.27.10
Published2026-06-12T12:15:13.230Z
SHA-2562d3567f7f59246f469ef8c88826d231b5f615674eb0efe0587c30cb15aebd635

Why flagged

What the scanner saw

Credential file access: matched "aws_access_key"

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

Availability ledger

available

review
Last checked
reviewRisk
3Score
3.27.11Version
Status history (1 event)
  1. newavailable · risk review · score 3 · status changed

Evidence

Static findings

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

No high-signal findings — see all findings below.

Show all 2 findings (low-signal and informational)
SeverityKindPathDetailPoints
lowCredential file accesspackage/assets/prepare-cdk-source-lambda/index.pymatched "aws_access_key"5
lowMessenger Bot Endpointpackage/assets/slack-error-log-handler-lambda/test_handler.pymatched "hooks.slack.com/services/" — messenger-bot URL without exfil context (likely a notification handler)5

Manifest

Package metadata

Scripts11
  • buildtsc
  • docstypedoc src --out docs
  • formatbiome format --write
  • format:checkbiome format
  • lintbiome check
  • lint:fixbiome check --fix
  • semantic-releasesemantic-release
  • snapshots./scripts/create-snapshots.sh
  • testNODE_OPTIONS='--experimental-vm-modules --enable-source-maps' jest
  • upgrade-dependenciesncu --upgrade --install always --format group
  • watchtsc -w
Dependencies2
  • @capraconsulting/webapp-deploy-lambda2.5.117
  • aws-jwt-verify5.2.1