PkgRadar

Package evidence

@ebay/[email protected]

no findings

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
172
Versions published
10Established · −30% score
First published
Nov 2025
Publisher
supnate

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

Looks clean — keep monitoring

No high-signal indicators in the stored static report. PkgRadar will re-check on the next ingest pass.

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":["@ebay/[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":["@ebay/[email protected]"],"fail_on":"review"}'
Publishersupnate
Artifact bytes2,683,834
Previous version2.0.4
Published2026-06-11T08:12:24.472Z
SHA-2568a69a362adad3b0037c05cf6d8ae5c0a82e4260f656b4e717f5b3aad75964bae

Why flagged

What the scanner saw

No high-signal static finding in the saved report.

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

Availability ledger

available

low
Last checked
lowRisk
0Score
2.0.5Version
Status history (1 event)
  1. new → available · risk low · score 0 · status changed

Evidence

Static findings

No findings stored for this release.

Manifest

Package metadata

Scripts8
  • buildvite build
  • build:devcross-env NODE_ENV=development vite build --mode development
  • build:testcross-env MUSE_TEST_BUILD=true NODE_ENV=production vite build --mode e2e-test
  • deploypnpm build && pnpm build:dev && muse release && muse deploy musemanager staging
  • postbuildcp MUSE_README.md ./build
  • prestart2muse-dev-utils check-updates
  • startvite
  • testreact-scripts test
Dependencies2
  • @tailwindcss/postcss^4.2.4
  • @tailwindcss/vite^4.3.0