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
- 13
- First published
- May 2026
- Publisher
- moe.osaze
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":["@workscribe/[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":["@workscribe/[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
Scripts11
buildtsupdevtsx src/index.tspostbuildchmod +x dist/index.js && node -e "const fs=require('fs'),p='dist/index.js';fs.writeFileSync(p,fs.readFileSync(p,'utf8').replace('require(\"sqlite\")', 'require(\"node:sqlite\")'))"prepacknpm run buildreleaserelease-itrelease:dryrelease-it --dry-runsync-docsnode scripts/sync-docs.js ../workscribe-landing-page user-docstestvitest runtest:watchvitesttypechecktsc --noEmitwatchtsup --watch
Dependencies3
chalk^4.1.2commander^12.1.0prompts^2.4.2