PkgRadar

Package evidence

@sebastian-prokesch/[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.

Versions published
7
First published
May 2026
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":["@sebastian-prokesch/[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":["@sebastian-prokesch/[email protected]"],"fail_on":"review"}'
Artifact bytes165,317
Previous version0.1.7
Published2026-06-11T19:43:07.308Z
SHA-2567ca3f26219676355ca2ddda1fbe9a10faf94c8c1a44bd15d0d6f2e9e4d503230

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
0.1.10Version
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/out/main/index.jsmatched "AWS_ACCESS_KEY"5
lowCredential file accesspackage/out/renderer/index.jsmatched "AWS_ACCESS_KEY"5

Manifest

Package metadata

Scripts32
  • biomecorepack pnpm dlx @biomejs/[email protected]
  • biome:checkcorepack pnpm biome check
  • biome:fixcorepack pnpm biome check --fix
  • biome:migratecorepack pnpm biome migrate --write
  • buildelectron-vite build
  • bump-versioncorepack pnpm version --no-commit-hooks --no-git-tag-version
  • cleancorepack pnpm clean:out
  • clean:allcorepack pnpm "/^clean:(dts|node_modules|out|tgz)$/"
  • clean:dtscorepack pnpm dlx [email protected] rm -f "src/**/*.scss.d.ts"
  • clean:node_modulescorepack pnpm dlx [email protected] rm -rf node_modules
  • clean:outcorepack pnpm dlx [email protected] rm -rf out
  • clean:tgzcorepack pnpm dlx [email protected] rm -f "*.tgz"
  • knipcorepack pnpm dlx [email protected] --dependencies
  • knip:checkcorepack pnpm "/^knip:(development|production)$/"
  • knip:developmentcorepack pnpm knip
  • knip:productioncorepack pnpm knip --production --strict
  • lintcorepack pnpm lint:check
  • lint:checkcorepack pnpm "/^(biome|prettier):check$/"
  • lint:fixcorepack pnpm "/^(biome|prettier):fix$/"
  • postupdatecorepack pnpm biome:migrate
  • prebuildcorepack pnpm type:check
  • prettierpnpm dlx [email protected]
  • prettier:checkpnpm prettier --check .
  • prettier:fixpnpm prettier --write .
  • testcorepack pnpm test:unit
  • test:integrationjest -c jest.integration.config.cjs
  • test:unitjest -c jest.unit.config.cjs
  • test:watchcorepack pnpm test:unit --watch
  • trunkpnpm dlx @trunkio/[email protected]
  • trunk:checkpnpm trunk check
  • …and 2 more.