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
- 21
- Versions published
- 17
- First published
- Apr 2026
- Publisher
- fetsorn
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":["@fetsorn/[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":["@fetsorn/[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
buildvite builddevvitelinteslint ./src/previewvite previewtauritauritestvitest --run --browser.headless --coveragewdio-browserwdio run ./wdio.browser.conf.js
Dependencies18
@solid-primitives/resize-observer^2.1.5@solidjs/meta^0.29.4buffer^6.0.3file-saver^2.0.5history^5.3.0i18next25.8.18i18next-browser-languagedetector8.2.1i18next-http-backend3.0.2microdiff^1.5.0mime^4.1.0path-browserify^1.0.1process^0.11.10search-query-parser^1.6.0sha.js^2.4.12solid-js^1.9.11tempy^3.2.0uuid^13.0.0web-streams-polyfill^4.2.0