@selfxyz/enterprise-sdk
npm:@selfxyz/enterprise-sdk · v0.4.1 · sha256:4a6bf7208d97 · as of 2026-11-02
- 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? no evidence
- First profile of this subject — nothing to compare yet.
- No evidence line on file for this question yet.
Is this your project? Respond →Dispute this reading
Hosts contacted
| Host | When | Role | Evidence |
|---|---|---|---|
| edge.dashboard.self.xyz | code | vendor | traced |
| verifier.self.xyz | code | vendor | traced |
| verifier.staging.self.xyz | code | vendor | traced |
| registry.npmjs.org | install | registry | observed |
| codeload.github.com | install | registry | observed |
Evidence (5 lines)
- observedO-hosts2026-11-02
registry.npmjs.org was contacted during install (registry).
sandbox:obs_fc3af7373860409a
- observedO-hosts2026-11-02
codeload.github.com was contacted during install (registry).
sandbox:obs_fc3af7373860409a
- tracedT-hosts2026-11-02
edge.dashboard.self.xyz appears in shipped code (vendor).
dist/index.js
- tracedT-hosts2026-11-02
verifier.self.xyz appears in shipped code (vendor).
dist/index.js
- tracedT-hosts2026-11-02
verifier.staging.self.xyz appears in shipped code (vendor).
dist/index.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
Recorded on Solana ↗ · reading of 2026-09-26 · same build as the one read above. It records what was read on that date; it is not a verdict.
Maintain this project? Respond to this reading
Loading sign-in…