Package evidence
@cmdoss/[email protected]
Install-time lifecycle script: postinstall="npm rebuild hnswlib-node || echo hnswlib-node rebuild skipped - using WASM fallback"
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
- 18
- Versions published
- 7
- First published
- Dec 2025
- Publisher
- aaronphancommandoss
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":["@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
Install-time lifecycle script: postinstall="npm rebuild hnswlib-node || echo hnswlib-node rebuild skipped - using WASM fallback"
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 5 · status changed
Evidence
Static findings
1 static · 0 from release diff · showing high-signal first.
No high-signal findings — see all findings below.
Show all 1 findings (low-signal and informational)
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| low | Install-time lifecycle script | package.json | postinstall="npm rebuild hnswlib-node || echo hnswlib-node rebuild skipped - using WASM fallback" | 5 |
Manifest
Package metadata
Scripts24
buildnpm run build:ts && node scripts/fix-esm-imports.cjsbuild:browsernpx esbuild src/index.ts --bundle --format=esm --outfile=dist-browser/pdw-sdk.browser.js --platform=browser --external:@mysten/sui --external:@mysten/sui/* --external:@mysten/walrus --external:@mysten/walrus-wasm --external:fs --external:path --external:fs/promises --external:crypto --sourcemap --target=es2022build:fullnpm run codegen && npm run build:ts &&build:tstsccodegensui-ts-codegen generate && node scripts/fix-codegen-paths.cjscodegen:summariescd ../../smart-contract && sui move summary --skip-fetch-latest-git-depsdevtsc --watchlinteslint src --ext .ts,.tsxlint:fixeslint src --ext .ts,.tsx --fixpostinstallnpm rebuild hnswlib-node || echo hnswlib-node rebuild skipped - using WASM fallbackprepareecho 'Skipping build during install'prepublishOnlynpm run buildserve:testnode test/e2e/serve-test.mjssetup:testnetnpx tsx scripts/setup-testnet.tstestjesttest:deploynpm run build && npm run test:sealtest:e2enpx playwright testtest:e2e:uinpx playwright test --uitest:embedding-hookstsx test/hooks/test-embedding-hooks-live.tstest:sealjest --testPathPattern=seal-deployment --verbosetest:seal:watchjest --testPathPattern=seal-deployment --watch --verbosetest:watchjest --watchverify:deploymentnode scripts/verify-deployment.jsverify:quicknpx jest test/simple-config.test.ts && npm run verify:deployment
Dependencies20
@ai-sdk/google^2.0.46@ai-sdk/openai^2.0.86@ai-sdk/provider^2.0.0@google/genai^1.20.0@langchain/core^0.3.0@langchain/google-genai^0.1.12@mysten/bcs^1.9.2@mysten/codegen^0.5.0@mysten/seal^0.9.4@mysten/slush-wallet^0.2.1@mysten/sui>=1.44.0@mysten/utils^0.2.0@mysten/walrus^0.8.3@noble/hashes^2.0.1@openrouter/sdk^0.3.7ai^5.0.113eventemitter3^5.0.1hnswlib-wasm^0.8.2sha3^2.1.4zod^4.2.1
Optional dependencies1
hnswlib-node^3.0.0