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
- 164
- Versions published
- 23
- First published
- Apr 2026
- Publisher
- todmy
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":["[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"}'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
Scripts8
benchnode dist/bin/valis-bench.jsbuildtsccorpus:fetch:longmemevalnode --experimental-strip-types scripts/fetch-longmemeval.tsdevtsc --watchlinttsc --noEmitprepublishOnlypnpm run build && pnpm run testtestvitest runtest:watchvitest
Dependencies14
@inquirer/input^4.2.4@inquirer/password^4.0.21@inquirer/select^4.4.2@modelcontextprotocol/sdk^1.12.1@qdrant/js-client-rest^1.13.0@secretlint/core^11.7.1@secretlint/secretlint-rule-preset-recommend^11.7.1@supabase/supabase-js^2.49.4chokidar^4.0.3commander^13.1.0pg^8.20.0picocolors^1.1.1yaml^2.6.0zod^3.24.4