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
- 1
- First published
- Jan 2026
- Publisher
- margo_cmdoss
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":["@cmdoss/[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":["@cmdoss/[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:bundleesbuild src/index.ts --bundle --format=esm --outfile=dist/bundle.js --external:chromebuild:testnpm run build && npm run build:bundle && cp dist/bundle.js test-extension/bundle.jsbuild:watchtsc --watchcleanrimraf distdevtsc --watchlinteslint src --ext .tslint:fixeslint src --ext .ts --fixprepublishOnlynpm run clean && npm run buildtestecho "Tests not implemented yet" && exit 0
Dependencies5
@mysten/bcs^1.8.0@mysten/sui^1.38.0@mysten/suins^0.7.34@mysten/walrus^0.6.0buffer^6.0.3