Security
The threat model, what never leaves your machine, and an honest statement about reporting a vulnerability.
Written and covered by tests — not yet observed in a live run
#The threat model
Finexia runs on your machine and drives command-line tools you already trust with your subscription. The interesting risks are therefore not about a remote service holding your data — it does not — but about what an agent can reach once it is running.
| Concern | Position |
|---|---|
| A vendor key leaking | Keys live in the macOS keychain. No code path writes one to a file, a database, an environment file or a log. |
| An agent reaching data it should not | A role declares its capabilities; the local tool server serves only what those cover. No role holds both your data and arbitrary web access. |
| Retrieved content steering the agent | Anything fetched from outside is data, never instruction. |
| A secret hidden in a source URL | The provenance writer redacts before writing to the journal. |
| A file written somewhere unexpected | A tool call cannot choose a path. The core composes it, because it owns the data room. |
| An order reaching a broker | There is no write path. The feed trait exposes no write method — verifiable by compilation. |
| The remote server seeing your work | It is a control plane: account, licence, updates. Cut it off and the application still works. |
| Processes outliving the session | The quit path stops every process the application started. A signal from outside bypasses it, by definition. |
#Reporting a vulnerability
Still missingThere is no published security contact yet. Rather than print an address that nobody monitors, this page states plainly that the channel still has to be defined. Until it is, a finding should go through whichever private channel you already have with the project.
#What is not proven
- The sub-agent boundary is written and tested, and nothing calls it. Inheritance of reach and budget is untested in a real delegation.
- The application is signed ad hoc and is not notarised.
- No third party has reviewed any of this.
#Sources
- Finexia OS — handover report 0.0.22FinexiaInternal document, not published
Read next
More in Resources