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
- 10
- First published
- Mar 2026
- Publisher
- alex_sova
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
Scripts7
preparegit config core.hooksPath .git-hooks || echo 'Not in a git repo'pubnpm run sync-version && npm run types && npm test && npm publishsync-versionnode -e "const v=JSON.parse(require('fs').readFileSync('package.json','utf8')).version; require('fs').writeFileSync('lib/version.js', \"export const VERSION = '\" + v + \"';\\n\\nexport default VERSION;\\n\")"testnode --test tests/*.test.js && npx playwright testtest:e2enpx playwright testtest:unitnode --test tests/*.test.jstypestsc -p types/hook.json
Dependencies4
@symbiotejs/symbiote^3.5.8hls.js^1.5.18leaflet^2.0.0-alpha.1three^0.171.0