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
- Feb 2026
- Publisher
- subash.77
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":["@tetherto/[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":["@tetherto/[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
Scripts10
buildtscbuild:stricttsclinteslint . --ext .ts,.tsx,.js,.jsx --max-warnings 0lint:fixeslint . --ext .ts,.tsx,.js,.jsx --fix --max-warnings 0prepacknpm run buildpreparenpm run buildtestjesttest:coveragejest --coveragetest:watchjest --watchtypechecktsc --noEmit
Dependencies9
@tanstack/react-query^5.0.0@tetherto/pear-wrk-wdk1.0.0-beta.8@tetherto/wdk-react-native-secure-storage1.0.0-beta.2expo-crypto^15.0.8immer^11.1.3react-native-bare-kit^0.12.3react-native-mmkv^4.1.0zod^3.22.0zustand^5.0.9