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
- 384
- Versions published
- 69
- First published
- Feb 2026
- Publisher
- tildes.senna.0z
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
Large Javascript Payload: 5597919 bytes
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 | Large Javascript Payload | package/dist/cli.js | 5597919 bytes | 0 |
Manifest
Package metadata
Scripts19
check-typestsc --noEmitcompilenpm run check-types && npm run lint && node esbuild.jscompile-testsnode -e "require('fs').rmSync('out/test',{recursive:true,force:true})" && tsc -p . --outDir outcompile:clinpm run check-types && node esbuild.js --clilinteslint srcpackagenpm run check-types && npm run lint && node esbuild.js --productionpretestnpm run compile-tests && npm run compile && npm run lintpublish:allnpm run publish:npm && npm run publish:vscepublish:npmnode -e "const fs=require('fs');const p=require('./package.json');p.name='norn-cli';fs.writeFileSync('package.json',JSON.stringify(p,null,2)+'\n')" && npm publish; exit_code=$?; node -e "const fs=require('fs');const p=require('./package.json');p.name='norn';fs.writeFileSync('package.json',JSON.stringify(p,null,2)+'\n')"; exit $exit_codepublish:vscenode -e "const p=require('./package.json');p.name='norn';require('fs').writeFileSync('package.json',JSON.stringify(p,null,2))" && npx vsce publishtestvscode-testtest:prereleasenpm test && npm run test:regressiontest:regressionnode ./dist/cli.js ./tests/Regression/ -e prelivevalidate:skillsnode ./scripts/validate-skills.mjsvscode:prepublishnpm run packagewatchnpm-run-all -p watch:*watch-teststsc -p . -w --outDir outwatch:esbuildnode esbuild.js --watchwatch:tsctsc --noEmit --watch --project tsconfig.json
Dependencies8
@modelcontextprotocol/sdk^1.29.0ajv^8.17.1axios^1.13.2chalk^5.4.1mssql^12.2.0norn-cli^1.10.6pg^8.20.0tough-cookie^6.0.0