SECURITY / VERIFY THE BOUNDARY

Small enough
to inspect.

Memoree keeps its trusted core local and deliberately narrow. The public source, locked dependency graph, protocol schema, release checksums, and build provenance let you verify those boundaries instead of taking them on faith.

No hidden network path

The Memoree crate has no HTTP client. Normal daemon, storage, recall, search, context, checkpoint, verification, and backup operations do not contact this website or an update service. The binary never checks for updates automatically.

Explicit model boundary

memoree remember is a caller-side convenience that shells out to the locally installed, already authenticated Codex CLI for one tool-free, schema-constrained compilation. Preview is the default. The daemon never invokes a model, reads a provider credential, or executes model output.

Local transport

The default Unix socket lives in an owner-only runtime directory and is mode 0600. Loopback TCP is host-local but not user-private, and non-loopback TCP requires an intentionally alarming opt-in flag. Authorization is outside the local personal v0.1 scope.

Release integrity

The installer uses versioned memoree.dev URLs, backed by public GitHub Releases, and rejects an archive that does not match its published SHA-256 checksum. Release builds use a locked dependency graph and publish GitHub build provenance. The installer never uses sudo or starts the daemon.

Report a vulnerability