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
180
Versions published
56
First published
Mar 2026
Publisher
mua_vtuber

Recommended action

Review before promoting

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

Inspect tarballAdd to CI gate
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"}'
Publishermua_vtuber
Artifact bytes409,089
Previous version4.14.2
Published2026-05-13T14:58:16.971Z
SHA-25693319c7a7c0d2433d2fbeefae2940a8ecdf043a9e27b3d8f75b12dbbfc82e282

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
10Score
4.14.3Version
Status history (1 event)
  1. new → available · risk review · score 10 · status changed

Evidence

Static findings

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

SeverityKindPathDetailPoints
mediumCredential file accesspackage/dist/bundle.jsmatched "aws_access_key"10

Manifest

Package metadata

Scripts31
  • buildturbo build
  • bundlenode scripts/bundle.mjs
  • cleanturbo clean
  • devturbo dev
  • install:claudenode scripts/install-host-mcp.mjs claude
  • install:claude:globalnode scripts/install-host-mcp.mjs claude --source global --scope user
  • install:codexnode scripts/install-host-mcp.mjs codex --assets --scope user
  • install:codex:assetsnode scripts/install-host-mcp.mjs codex --assets --scope project
  • install:codex:globalnode scripts/install-host-mcp.mjs codex --source global --assets --scope user
  • install:codex:mcpnode scripts/install-host-mcp.mjs codex
  • install:codex:mcp:globalnode scripts/install-host-mcp.mjs codex --source global
  • install:gemininode scripts/install-host-mcp.mjs gemini --assets --scope user
  • install:gemini:assetsnode scripts/install-host-mcp.mjs gemini --assets --scope user
  • install:gemini:globalnode scripts/install-host-mcp.mjs gemini --source global --assets --scope user
  • install:gemini:mcpnode scripts/install-host-mcp.mjs gemini
  • install:gemini:mcp:globalnode scripts/install-host-mcp.mjs gemini --source global
  • lintnpm run lint:root && turbo lint
  • lint:rooteslint "scripts/**/*.mjs"
  • prebuildnpm run sync:metadata
  • prebundlenpm run sync:metadata
  • prepublishOnlynpm run build && npm run bundle
  • sync:metadatanode scripts/sync-metadata.mjs
  • testturbo test && npm run test:host-assets
  • test:host-assetsvitest run scripts/__tests__
  • uninstall:claudenode scripts/uninstall-host-mcp.mjs claude
  • uninstall:codexnode scripts/uninstall-host-mcp.mjs codex --assets --scope user
  • uninstall:codex:assetsnode scripts/uninstall-host-mcp.mjs codex --assets --scope project
  • uninstall:codex:mcpnode scripts/uninstall-host-mcp.mjs codex
  • uninstall:gemininode scripts/uninstall-host-mcp.mjs gemini --assets --scope user
  • uninstall:gemini:assetsnode scripts/uninstall-host-mcp.mjs gemini --assets --scope user
  • …and 1 more.