solana-agent-kit
npm:solana-agent-kit · v2.0.10 · sha256:113858513146 · as of 2026-11-02
- Does it take your key? declared
- It asks for a private key or seed phrase in its setup.
- The project says so — README, config, env list or tool description.
- 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 |
|---|---|---|---|
| mainnet.helius-rpc.com | code | rpc | traced |
| registry.npmjs.org | install | registry | observed |
| nodejs.org | install | other | observed |
Evidence (5 lines)
- observedO-hosts2026-11-02
registry.npmjs.org was contacted during install (registry).
sandbox:obs_ad9bf0c0774ca605
- observedO-hosts2026-11-02
nodejs.org was contacted during install (other).
sandbox:obs_ad9bf0c0774ca605
- tracedT-hosts2026-11-02
mainnet.helius-rpc.com appears in shipped code (rpc).
dist/index.cjs
- declaredD-env-key2026-11-02
Setup names a Solana wallet adapter (e.g. KeypairWallet from a Keypair) as something to provide.
deploy_spec.requires
- declaredD-env-key2026-11-02
Setup names SOLANA_PRIVATE_KEY as something to provide.
solana-agent-kit@2.0.10/README.md
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…