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
- 5
- First published
- Dec 2021
- Publisher
- thibmeu
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":["@cloudflare/[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":["@cloudflare/[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
Scripts12
benchtsc -b bench && node ./lib/esm/bench/index.jsbuildtsc -b . tsconfig.cjs.jsoncleantsc -b --clean . test ./tsconfig.cjs.json test/tsconfig.cjs.json bench examplesexamplestsc -b examples && node ./lib/esm/examples/index.jsformatprettier './(src|test|bench|examples)/*.ts' --writelinteslint .prepacktsc -b . tsconfig.cjs.jsonpreparetsc -b . tsconfig.cjs.jsontestnpm run test:esm && npm run test:cjstest:buildtsc -b test test/tsconfig.cjs.jsontest:cjsnpm run test:build && node node_modules/.bin/jest --ci --selectProjects cjs --coverageDirectory coverage/cjstest:esmnpm run test:build && node --experimental-vm-modules node_modules/.bin/jest --ci --selectProjects esm --coverageDirectory coverage/esm
Optional dependencies2
@noble/curves1.2.0@noble/hashes1.3.2