@openai/codex
npm:@openai/codex · v0.167.1 · sha256:a5b60ca409e0 · as of 2026-11-11
- 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? no evidence
- No change in key, host or fund behaviour since 0.167.0.
- No evidence line on file for this question yet.
Is this your project? Respond →Dispute this reading
Evidence (0 lines)
- No evidence lines on file.
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 0.167.0) 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.
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…