PkgRadar

Package evidence

[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
16
First published
Feb 2026
Publisher
jim380

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":["[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"}'
Publisherjim380
Artifact bytes209,895
Previous version0.2.1
Published2026-04-06T01:30:10.656Z
SHA-2561612bd7000863f0eb75397d23ecb49553312ef1ef34561bb772533231de3ea60

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.2.2Version
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

Scripts5
  • buildtsc
  • build:allnpm --prefix clinkx-workflows run build && npm run build
  • prepublishOnlynpm --prefix clinkx-workflows run build && npm run build && node -e "const root=require('./package.json').dependencies;const sub=require('./clinkx-workflows/package.json').dependencies;const missing=Object.keys(sub).filter(d=>!root[d]);if(missing.length){console.error('Missing from root deps:',missing);process.exit(1);}"
  • startnode dist/index.js
  • testvitest run
Dependencies5
  • @modelcontextprotocol/sdk^1.27.1
  • pino^9.6.0
  • yaml^2.7.0
  • zod^3.24.0
  • zod-to-json-schema^3.24.0