elizaos
npm:elizaos · v2.0.3-beta.7 · sha256:33d4f791ae37 · 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 beta.
- Our static read of the published artifact found it.
Is this your project? Respond →Dispute this reading
Hosts contacted
| Host | When | Role | Evidence |
|---|---|---|---|
| api.elizacloud.ai | code | other | traced |
| app.example.vercel.app | code | other | traced |
| capability.example.test | code | other | traced |
| cloud-capability.example.test | code | other | traced |
| cloud.example.test | code | other | traced |
| eliza.so | code | other | traced |
| github.com | code | registry | traced |
| registry.npmjs.org | code | registry | traced |
Evidence (8 lines)
- tracedT-hosts2026-11-10
api.elizacloud.ai appears in shipped code (other).
dist/commands/deploy.js
- tracedT-hosts2026-11-10
app.example.vercel.app appears in shipped code (other).
dist/commands/deploy.test.js
- tracedT-hosts2026-11-10
capability.example.test appears in shipped code (other).
dist/commands/capability-router.test.js
- tracedT-hosts2026-11-10
cloud-capability.example.test appears in shipped code (other).
dist/commands/capability-router.test.js
- tracedT-hosts2026-11-10
cloud.example.test appears in shipped code (other).
dist/commands/capability-router.test.js
- tracedT-hosts2026-11-10
eliza.so appears in shipped code (other).
templates/project/scripts/ensure-elizaos-optional-app-stubs.mjs
- tracedT-hosts2026-11-10
github.com appears in shipped code (registry).
dist/scaffold.js
- tracedT-hosts2026-11-10
registry.npmjs.org appears in shipped code (registry).
dist/commands/plugins.js
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.
- No tool inventory was available, so fund actions were not read.
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…