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
- 7
- First published
- May 2025
- Publisher
- boon4681
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
Scripts6
buildtsx ./build.tsbuild:ohmnpx ohm generateBundles --withTypes src/ohm/tab-search.ohm && tsx ./build.ohm.tsbuild:watchtsx ./build.ts --watchdevtsup ./{src,tests}/**/*.ts --watch ./{src,tests}/**/*.ts --format cjs,esm --outDir ./dev --onSuccess "node dev/tests/index.js"dev:webvite --port 5000testvitest run
Dependencies12
@codemirror/autocomplete^6.0.0@codemirror/commands^6.0.0@codemirror/language^6.0.0@codemirror/legacy-modes^6.0.0@codemirror/search^6.0.0@codemirror/state^6.0.0@codemirror/view^6.0.0@lezer/highlight^1.0.0ohm-js^17.1.0preact^10.26.6preact-custom-element^4.3.0style-mod^4.0.0