PkgRadar

Package evidence

[email protected]

Remote Payload: matched "cURL "

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
386
Versions published
68
First published
Feb 2026
Publisher
tildes.senna.0z

Recommended action

Review before promoting

Mixed signals: the package has indicators worth reading before allowing the update in automated dependency flows.

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"}'
Artifact bytes4,404,446
Previous version2.4.0
Published2026-05-27T21:55:19.310Z
SHA-256c9bf834313c3764713fff83b46150cf76675d3bbd1004c7b3d0d6778356ec355

Why flagged

What the scanner saw

Remote Payload: matched "cURL "

Not observed: package install, lifecycle script execution, or sandbox execution. PkgRadar only inspects on-disk artifacts.

Availability ledger

available

review
Last checked
reviewRisk
22Score
2.5.0Version
Status history (1 event)
  1. newavailable · risk review · score 22 · status changed

Evidence

Static findings

2 static · 0 from release diff · showing high-signal first.

SeverityKindPathDetailPoints
mediumRemote Payloadpackage/package.jsonmatched "cURL "12
mediumLarge Javascript Payloadpackage/dist/cli.js5593956 bytes10

Manifest

Package metadata

Scripts19
  • check-typestsc --noEmit
  • compilenpm run check-types && npm run lint && node esbuild.js
  • compile-testsnode -e "require('fs').rmSync('out/test',{recursive:true,force:true})" && tsc -p . --outDir out
  • compile:clinpm run check-types && node esbuild.js --cli
  • linteslint src
  • packagenpm run check-types && npm run lint && node esbuild.js --production
  • pretestnpm run compile-tests && npm run compile && npm run lint
  • publish:allnpm run publish:npm && npm run publish:vsce
  • publish: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_code
  • publish:vscenode -e "const p=require('./package.json');p.name='norn';require('fs').writeFileSync('package.json',JSON.stringify(p,null,2))" && npx vsce publish
  • testvscode-test
  • test:prereleasenpm test && npm run test:regression
  • test:regressionnode ./dist/cli.js ./tests/Regression/ -e prelive
  • validate:skillsnode ./scripts/validate-skills.mjs
  • vscode:prepublishnpm run package
  • watchnpm-run-all -p watch:*
  • watch-teststsc -p . -w --outDir out
  • watch:esbuildnode esbuild.js --watch
  • watch:tsctsc --noEmit --watch --project tsconfig.json
Dependencies8
  • @modelcontextprotocol/sdk^1.29.0
  • ajv^8.17.1
  • axios^1.13.2
  • chalk^5.4.1
  • mssql^12.2.0
  • norn-cli^1.10.6
  • pg^8.20.0
  • tough-cookie^6.0.0