PkgRadar

Package evidence

@skhatri/[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.

Versions published
10Established · −30% score
First published
Aug 2025
Publisher
skhatri

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":["@skhatri/[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":["@skhatri/[email protected]"],"fail_on":"review"}'
Publisherskhatri
Artifact bytes17,814
Previous version0.9.0
Published2026-06-01T13:04:35.806Z
SHA-256e81e4b4a57a1205a530ec2c100ad119eb2c61175d9f5f57a643725b03997a17f

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
0.9.3Version
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

Scripts16
  • buildtsc
  • cleanrm -rf dist
  • devtsc && node dist/index.js
  • dev:httptsc && node dist/index.js --http --port 3001
  • dev:stdiotsc && node dist/index.js --stdio
  • link:localnpm run build && npm link
  • publishnpm publish
  • setup:cursornpm run build && npm link && echo 'Ready for Cursor! Use maven-mcp command.'
  • startnode dist/index.js
  • start:httpnode dist/index.js --http --port 3001
  • start:stdionode dist/index.js --stdio
  • testjest
  • test:cijest --coverage --ci --watchAll=false
  • test:coveragejest --coverage
  • test:servernpm run build && node dist/index.js --stdio
  • test:watchjest --watch
Dependencies4
  • @modelcontextprotocol/sdk^0.5.0
  • eventsource^4.0.0
  • node-fetch^3.3.2
  • undici^6.0.0