PkgRadar

Package evidence

@stackone/[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
1,349Niche · −30% score
Versions published
60Established · −30% score
First published
Oct 2025
Publisher
stackone-publisher

Effective trust discount applied: 30% (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":["@stackone/[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":["@stackone/[email protected]"],"fail_on":"review"}'
Artifact bytes504,495
Previous version1.41.0
Published2026-06-02T08:16:06.716Z
SHA-256091cddcdbe068c53ce0591ab9e624f026bca5c68db8242ee4294a1afb2c7da1e

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
21Score
1.42.0Version
Status history (1 event)
  1. newavailable · risk review · score 21 · status changed

Evidence

Static findings

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

No high-signal findings — see all findings below.

Show all 6 findings (low-signal and informational)
SeverityKindPathDetailPoints
lowCredential file accesspackage/dist/dist-cjs-BEXyl9CE.cjsmatched "aws_access_key"5
lowCredential file accesspackage/dist/dist-cjs-C_zn_i01.cjsmatched "AWS_ACCESS_KEY"5
lowCredential file accesspackage/dist/index.cjsmatched "AWS_ACCESS_KEY"5
lowCredential file accesspackage/dist/dist-cjs-BJejHHw0.mjsmatched "aws_access_key"5
lowCredential file accesspackage/dist/dist-cjs-Cj3NYQtI.mjsmatched "AWS_ACCESS_KEY"5
lowCredential file accesspackage/dist/index.mjsmatched "AWS_ACCESS_KEY"5

Manifest

Package metadata

Scripts17
  • buildtsdown --env.NODE_ENV=production --minify
  • build:devtsdown --env.NODE_ENV=development
  • cleanrimraf dist
  • code:checkbiome check ./src ./*.mjs
  • code:check:fixbiome check --write ./src ./*.mjs
  • code:formatbiome format ./src ./*.mjs
  • code:format:fixbiome format --write ./src ./*.mjs
  • code:lintbiome lint --error-on-warnings ./src ./*.mjs
  • code:lint:fixbiome lint --write ./src ./*.mjs
  • lintnpm run code:check
  • lint:fixnpm run code:check:fix
  • prebuildnpm run clean
  • prebuild:devnpm run clean
  • publish-releasenpm publish --access=public
  • testFORCE_COLOR=1 vitest run
  • test:typechecktsc --noEmit --project tsconfig.tests.json
  • test:watchFORCE_COLOR=1 vitest watch --silent
Dependencies7
  • @aws-sdk/client-s33.1030.0
  • @platformatic/kafka1.31.0
  • @stackone/logger*
  • @stackone/redaction*
  • @stackone/transport*
  • @stackone/utils*
  • zod3.25.76