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
- 50
- Versions published
- 20Established · −30% score
- First published
- Sep 2025
- Publisher
- kyr0
Effective trust discount applied: −30% (max across signals — discounts don’t stack). New install-lifecycle deltas vs the previous release would clear the discount.
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
Scripts17
benchnpx autocannon -p 32 -w 8 -c 200 -d 20 -m POST -H "content-type: application/json" -b '{"hello":"world"}' http://127.0.0.1:3000/bodybench:rpcnpx autocannon -p 256 -w 8 -c 1024 -d 30 -m POST -H 'content-type: application/json' -b '{"className":"mathApi","methodName":"add","args":[1,2]}' http://127.0.0.1:3000/rpcbuildpkgroll && node ./scripts/append-virtual-config-types.mjscleanrm -rf ./dist && rm -rf ./node_modules/.bun && rm -rf ./.container-runtimecli-buildnode ./dist/cli.mjs build ../../example-ssg/cli-devnode ./dist/cli.mjs dev ../../example-ssg/cli-dev:threenode ./dist/cli.mjs dev ../../examples/with-three.js/cli-servenode ./dist/cli.mjs serve ../../example-ssg/cli-serve:mcnode ./dist/cli.mjs serve ../../example-ssg/ --multicoreprebuildbun run cleanprepare:containernode ./scripts/prepare-container-runtime.mjsprepublishOnlybun run testpretestbun run buildstartnode ./dist/cli.mjs dev ../../example-ssg/testbun run test:cli-dev:threetest:browservitest run --config vitest.browser.config.ts --passWithNoTeststest:cli-dev:threebun run build && vitest run scripts/cli-dev-three.spec.ts
Dependencies19
@mdx-js/rollup^3.1.0defuss^3.4.6defuss-express^0.3.2defuss-vite^1.2.0esbuild^0.27.3fast-glob^3.3.3rehype-katex^7.0.1rehype-stringify^10.0.1remark-frontmatter^5.0.0remark-gfm^4.0.1remark-math^6.0.0remark-mdx-frontmatter^5.2.0remark-parse^11.0.0remark-rehype^11.1.2rolldown^1.0.0-rc.18toml^3.0.0vite^8.0.0ws^8.20.0yaml^2.8.2