openclaw
npm:openclaw · v2026.11.3 · sha256:dae4c4f75495 · as of 2026-11-10
- Does it take your key? no evidence
- No private-key read found in what we read of its setup and published code — the limits say how much that was.
- No evidence line on file for this question yet.
- Does your key leave? no evidence
- Not yet run — we have not run this version with planted test keys.
- No evidence line on file for this question yet.
- Can it move funds on its own? no evidence
- Unknown — we could not read what it exposes.
- No evidence line on file for this question yet.
- What changed? traced
- No change in key, host or fund behaviour since 2026.11.2.
- Our static read of the published artifact found it.
Is this your project? Respond →Dispute this reading
Hosts contacted
| Host | When | Role | Evidence |
|---|---|---|---|
| docs.openclaw.ai | code | vendor | traced |
| openclaw.ai | code | vendor | traced |
Evidence (4 lines)
- tracedT-install-script2026-11-10
package.json runs preinstall: node scripts/preinstall-package-manager-warning.mjs.
package.json
- tracedT-install-script2026-11-10
package.json runs postinstall: node scripts/postinstall-bundled-plugins.mjs.
package.json
- tracedT-hosts2026-11-10
docs.openclaw.ai appears in shipped code (vendor).
node-version.mjs
- tracedT-hosts2026-11-10
openclaw.ai appears in shipped code (vendor).
node-version.mjs
Limits
- The observed lane has not run on this version: not yet run on this version
- Traced analysis follows flows inside one module and one hop across a relative import; a longer chain is not followed.
- The observed lane has not run on this version.
- An earlier sandbox run (2026-11-09, version 2026.11.2) saw no planted key leave during install and start-up, under our test conditions — code paths that only run later, or only on a trigger, are not covered. It does not count for this version, which has not been run.
- No tool inventory was available, so fund actions were not read.
- Traced: read selectively — the tarball is 113171358 bytes, over the 15728640-byte whole-read size, so only package.json, the README and shipped JavaScript up to 2.0 MB a file were unpacked (11289 code files, 140.4 MB); not read: 3524 other files (84.8 MB), 378 type declarations (5.3 MB), 4 native binaries and WebAssembly (2.0 MB), 2 test and minified JavaScript (0.2 MB), 1 TypeScript sources (0.0 MB); 7 JavaScript files over 2.0 MB not read (29.9 MB; largest: node_modules/chrome-devtools-mcp/build/src/third_party/index.js, dist/managed-handoff-runtime.mjs, dist/package-update-activation-recovery.mjs); 11289 code files; parsed 400, entry points first.
A profile describes what we read and ran, with dates. It is not a safety rating, an audit or an endorsement, and "not found" is not "not there".
sato.custody/v1 · custody-3
Maintain this project? Respond to this reading
Loading sign-in…