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
- 3
- First published
- Mar 2026
- Publisher
- chrox
Recommended action
Review before promotingMixed signals: the package has indicators worth reading before allowing the update in automated dependency flows.
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":["@readest/[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":["@readest/[email protected]"],"fail_on":"review"}'Why flagged
What the scanner saw
Large Javascript Payload: 16107612 bytes
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 review · score 20 · status changed
Evidence
Static findings
2 static · 0 from release diff · showing high-signal first.
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| medium | Large Javascript Payload | package/bundle/main.es.js | 16107612 bytes | 10 |
| medium | Large Javascript Payload | package/dist/wasm-inline.js | 15614666 bytes | 10 |
Manifest
Package metadata
Scripts5
buildnpm run napi-build && npm run tsc-buildbundlevite buildnapi-buildsh -c 'FEATURES=browser; [ -n "$WASM_FTS" ] && FEATURES=$FEATURES,wasm-fts; napi build --features $FEATURES --profile release-official --platform --target wasm32-wasip1-threads --no-js --manifest-path ../../Cargo.toml --output-dir . && rm index.d.ts turso.wasi* wasi* browser.js'testCI=1 vitest --browser=chromium --run && CI=1 vitest --browser=firefox --runtsc-buildnpm exec tsc && cp turso.wasm32-wasi.wasm ./dist/turso.wasm32-wasi.wasm && WASM_FILE=turso.wasm32-wasi.wasm JS_FILE=./dist/wasm-inline.js node ../../scripts/inline-wasm-base64.js && node scripts/build-worker-source.mjs && npm run bundle
Dependencies2
@readest/turso-database-common0.6.0-pre.28-readest.0@readest/turso-database-wasm-common0.6.0-pre.28-readest.0