tomtan/EverOS
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
306dcfe167d512c03369c93c66e804f101a63943
EverOS/SECURITY.md
Elliot Chen 518b8eca85 chore: initialize EverOS 1.0.0 
md-first memory extraction framework for AI agents.

Markdown is the single source of truth; SQLite holds state and LanceDB
provides the rebuildable vector + BM25 + scalar index. The codebase follows
a single-direction DDD layering (entrypoints -> service -> memory -> infra,
with component / core / config cross-cutting) enforced by import-linter.

Engineering surface:
- Coding conventions in .claude/rules/ (path-scoped) and workflows in
  .claude/skills/ (/commit, /new-branch, /pr).
- GitHub Actions CI runs make lint + test + integration; pre-commit mirrors
  the gates locally (ruff, hygiene hooks, gitlint commit-msg).
- Commit messages follow Conventional Commits, enforced by gitlint.
- make lint also enforces datetime two-zone discipline and OpenAPI drift.
2026-06-06 07:33:17 +08:00

1.8 KiB
Raw Blame History

Security Policy

Supported Versions

EverOS is in active alpha development. Security fixes are applied to the latest release line only.

Version Supported
0.1.x ✅
< 0.1 ❌

Reporting a Vulnerability

Please do not report security vulnerabilities through public GitHub issues, discussions, or pull requests.

Instead, email evermind@shanda.com with:

  • A description of the vulnerability and its potential impact
  • Steps to reproduce, or a proof-of-concept
  • The affected version / commit
  • Any suggested mitigation, if you have one

We will acknowledge your report within 5 business days, keep you informed of progress, and aim to ship a fix or mitigation before any public disclosure. Reporters are credited in the release notes unless you prefer to remain anonymous.

Scope & Threat Model

EverOS runs as a local-first service for single users or small teams (Markdown + SQLite + LanceDB on the local filesystem). Please keep the following in mind:

  • Exposing the HTTP API (everos server) to an untrusted network is outside the supported threat model — it assumes a trusted local caller. The server binds to 127.0.0.1 by default (env EVEROS_API__HOST) so a fresh install is loopback-only. Only set the bind to 0.0.0.0 (or any routable interface) after you have placed your own gateway / auth layer in front; everos server start will log a warning when you bind to 0.0.0.0.
  • Secrets (LLM / embedding API keys) live in your local .env; protect that file as you would any credential. EverOS never transmits them anywhere except the providers you configure.
  • Memory content is stored as plaintext .md files; apply OS-level file permissions or disk encryption if your data is sensitive.