PkgRadar

Package evidence

[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
31,556Mainstream · −50% score
Versions published
81Mature · −50% score
First published
May 2022
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":["[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":["[email protected]"],"fail_on":"review"}'
Artifact bytes67,939
Previous version2.6.0
Published2026-03-12T23:15:00.289Z
SHA-256b762d1834f73eaa0b176c3a95b8278fe37996e6c9b5f1f28b5703520fee959bf

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
2.7.0Version
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/dist/cjs/providers/amazon-s3/provider.jsmatched "AWS_ACCESS_KEY"5
lowCredential file accesspackage/dist/providers/amazon-s3/provider.jsmatched "AWS_ACCESS_KEY"5

Manifest

Package metadata

Scripts14
  • buildnpm run build:esm && npm run build:cjs
  • build:cjsesbuild "src/**/*.ts*" --outdir=dist/cjs --platform=node --format=cjs --target=es2020 --define:import.meta.url=\"\"
  • build:esmesbuild "src/**/*.ts*" --outdir=dist --format=esm --target=es2020
  • cleanrm -rf dist
  • clinode --loader tsx --no-warnings ./src/cli
  • coveragec8 report --reporter=text-lcov > ./coverage/lcov.info
  • postbuild:cjsnode --eval "fs.writeFileSync('./dist/cjs/package.json', '{\"type\": \"commonjs\"}')"
  • prebuildnpm run clean && npm run types
  • preparenpm run build
  • testglob -c "c8 --src src --exclude 'next.config.js' --exclude 'tests/**' --exclude 'dist/**' node --loader tsx --no-warnings --test" "./tests/**/*.test.{ts,tsx}"
  • typesnpm run types:esm & npm run types:cjs
  • types:cjstsc --outDir dist/cjs
  • types:esmtsc --outDir dist
  • watchnpm run types:esm -- -w & npm run types:cjs -- -w & npm run build:esm -- --watch=forever & npm run build:cjs -- --watch=forever
Dependencies20
  • @aws-sdk/client-s3^3.717.0
  • @inquirer/prompts^7.8.6
  • @mux/mux-node9.0.1
  • @mux/mux-video^0.28.2
  • @mux/playback-core^0.31.4
  • @next/env15.5.9
  • @paralleldrive/cuid2^2.2.2
  • @vercel/blob^2.0.0
  • chalk^4.1.2
  • chokidar^4.0.3
  • dash-video-element^0.3.1
  • hls-video-element^1.5.10
  • magicast^0.3.5
  • media-chrome^4.16.1
  • minimatch^10.0.3
  • player.style^0.3.1
  • resolve^1.22.10
  • symlink-dir^6.0.3
  • undici^5.28.4
  • yargs^17.7.2