Sato Hub
Package

clawhub

npm:clawhub · v0.25.1 · sha256:0ede518fe73c · as of 2026-11-09

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?
observed
Not observed — no planted key left during install and start-up, under our test conditions — code paths that only run later, or only on a trigger, are not covered.
We ran it with planted test keys and saw it.
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?
observed
No change in key, host or fund behaviour since 0.25.0.
We ran it with planted test keys and saw it.

Is this your project? Respond →Dispute this reading

Hosts contacted

HostWhenRoleEvidence
api.github.comcoderegistrytraced
clawhub.aicodevendortraced
codeload.github.comcoderegistrytraced
docs.openclaw.aicodevendortraced
github.comcoderegistrytraced
spdx.orgcodeothertraced
registry.npmjs.orginstallregistryobserved
Evidence (7 lines)
  • observedO-hosts2026-11-09

    registry.npmjs.org was contacted during install (registry).

    sandbox:obs_3239f0f1c45dfe2a

  • tracedT-hosts2026-11-09

    api.github.com appears in shipped code (registry).

    dist/cli/commands/github.js

  • tracedT-hosts2026-11-09

    clawhub.ai appears in shipped code (vendor).

    dist/cli/registry.js

  • tracedT-hosts2026-11-09

    codeload.github.com appears in shipped code (registry).

    dist/cli/commands/skills.js

  • tracedT-hosts2026-11-09

    docs.openclaw.ai appears in shipped code (vendor).

    dist/cli/commands/packages.js

  • tracedT-hosts2026-11-09

    github.com appears in shipped code (registry).

    dist/cli/commands/github.js

  • tracedT-hosts2026-11-09

    spdx.org appears in shipped code (other).

    dist/schema/license.js

Limits

  • Traced analysis follows flows inside one module and one hop across a relative import; a longer chain is not followed.
  • Key egress not observed during install and start-up, under our test conditions — code paths that only run later, or only on a trigger, are not covered.
  • No tool inventory was available, so fund actions were not read.
  • Sandbox: DNS queries made directly by the target are not logged; hosts are recorded from proxied HTTP(S) requests and CONNECTs..
  • Sandbox: Code that ignores HTTP(S)_PROXY has no route out of the sandbox, so its attempts are not captured..

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…