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
- 222
- Versions published
- 27
- First published
- May 2026
- Publisher
- thotischner
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":["@thotischner/[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":["@thotischner/[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
Scripts3
buildtsc && rm -rf dist/ui && cp -r src/ui dist/uidevtsx watch src/index.tsstartnode dist/index.js
Dependencies15
@kubernetes/client-node^1.4.0@modelcontextprotocol/sdk^1.12.0@opentelemetry/api^1.9.0@opentelemetry/auto-instrumentations-node^0.76.0@opentelemetry/exporter-trace-otlp-http^0.218.0@opentelemetry/resources^2.2.0@opentelemetry/sdk-node^0.218.0@opentelemetry/semantic-conventions^1.40.0express^5.2.1express-rate-limit^8.5.2js-yaml^4.1.0prom-client^15.1.0redis^4.7.0ws^8.18.0zod^4.4.3