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
- 6
- First published
- Jun 2026
- Publisher
- zzj-new
Recommended action
Looks clean — keep monitoringNo high-signal indicators in the stored static report. PkgRadar will re-check on the next ingest pass.
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":["@szc-ft/[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":["@szc-ft/[email protected]"],"fail_on":"review"}'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
Status history (1 event)
- new → available · risk low · score 0 · status changed
Evidence
Static findings
No findings stored for this release.
Manifest
Package metadata
Scripts14
buildtsc && node scripts/copy-assets.js && chmod +x dist/mcp-stdio.jsprepublishOnlynpm run buildreleaserelease-itrelease:dryrelease-it --dry-runrelease:majorrelease-it majorrelease:minorrelease-it minorrelease:patchrelease-it patchrestartbash scripts/restart.shstartts-node src/server.tsstart:mcpts-node src/mcp-stdio.tstestjesttest:coveragejest --coveragetest:unitjest test/sketchConfigAnalyzer.test.ts test/tools.test.tstest:watchjest --watch
Dependencies5
@types/multer^2.0.0body-parser^1.19.0express^4.17.1extract-zip^2.0.1multer^2.0.2