PkgRadar

Package evidence

@t2000/[email protected]

Large Javascript Payload: 5678440 bytes

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,951Niche · −30% score
Versions published
403
First published
Mar 2026
Publisher
funkii

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":["@t2000/[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":["@t2000/[email protected]"],"fail_on":"review"}'
Publisherfunkii
Artifact bytes8,429,909
Previous version4.2.2
Published2026-06-08T08:21:11.090Z
SHA-256a32f216d693ad82563c0568f548145b4a27ed0588d38682d944e4fed8ea714cf

Why flagged

What the scanner saw

Large Javascript Payload: 5678440 bytes

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

Availability ledger

available

low
Last checked
lowRisk
0Score
4.3.0Version
Status history (2 events)
  1. scan_error → available · risk low · score 0 · status scan_error -> available, risk none -> low, score none -> 0
  2. new → scan_error · risk none · score — · HTTP status client error (404 Not Found) for url (https://registry.npmjs.org/@t2000/mcp/-/mcp-4.3.0.tgz)

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
lowLarge Javascript Payloadpackage/dist/bin.js5678440 bytes0
lowLarge Javascript Payloadpackage/dist/index.js5678413 bytes0

Manifest

Package metadata

Scripts7
  • buildtsup
  • cleanrm -rf dist
  • devtsup --watch
  • linteslint src/
  • testvitest run
  • test:watchvitest
  • typechecktsc --noEmit