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
- 14
- First published
- Apr 2026
- Publisher
- ryanjansen
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
Obfuscation Density: high encoded/escaped-token density
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
1 static · 0 from release diff · showing high-signal first.
No high-signal findings — see all findings below.
Show all 1 findings (low-signal and informational)
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| low | Obfuscation Density | package/dist/mcp-package/index.mjs | high encoded/escaped-token density | 0 |
Manifest
Package metadata
Scripts27
buildnpm run build:server && npm run build:schemas && npm run build:module && npm run build:mcp-packagebuild:mcp-packagenode scripts/build-mcp-package.mjsbuild:modulenode scripts/build-module.mjsbuild:npmnpm run build:mcp-packagebuild:schemastsx scripts/generate-tool-schemas.tsbuild:servertsc -p tsconfig.server.jsoncss-guardnode scripts/file-size-guard.mjs cssdeploynpm run build && node scripts/deploy.jsdevtsx watch src/server/index.tsformatprettier --write .format:checkprettier --check .inspectnpx @modelcontextprotocol/inspector tsx src/server/index.tsknipknip --include nsExports,nsTypes --treat-config-hints-as-errorslicense-checknode scripts/license-check.jslinteslint . && stylelint "src/**/*.css"lint:cssstylelint "src/**/*.css"lint:css:fixstylelint "src/**/*.css" --fixlint:fixeslint . --fix && stylelint "src/**/*.css" --fixlockfile-lintlockfile-lint --path package-lock.json --type npm --allowed-hosts npm --validate-https --validate-package-names --validate-integrity --empty-hostname falseprebuildnode -e "require('fs').rmSync('dist',{recursive:true,force:true})"preparehuskyprepublishOnlynpm run typecheck && npm run lockfile-lint && npm run license-check && npm run build:schemas && npm run build:mcp-packagescansemgrep scan --config .semgrep.yml --config p/owasp-top-ten --config p/nodejs src/ts-guardnode scripts/file-size-guard.mjs tstypechecktsc --noEmit -p tsconfig.server.json && tsc --noEmit -p tsconfig.module.jsonupdate:tool-snapshottsx scripts/generate-tool-schemas.ts --update-snapshotverify:schemasnpm run build:schemas && git diff --exit-code -- src/module/ai/tools/generated/ scripts/tool-order.snapshot.json