Skip to content

Security: Ambientware-labs/ambient-runtime

Security

docs/SECURITY.md

Security

Ambient Runtime v0.1 is a static, client-side app with a small, honest threat surface.

Data handling

  • Everything stays in the browser. The Free Engine runs locally. No task sends input anywhere.
  • Saved runs are stored in localStorage (per-origin, per-browser). They are never uploaded.
  • Exports (JSON / Markdown) are generated in the browser and downloaded locally.
  • Every result reports leftBrowser — in v0.1 this is always false.

No secrets, no keys

  • The app requires no API keys and reads no environment secrets.
  • Do not commit .env files or credentials. .gitignore excludes .env* and *.local.
  • Do not add hosted AI model dependencies or ask users for keys (see AGENTS.md).

Network

  • No backend, no auth, no analytics, no third-party calls in v0.1.
  • The model slot performs a read-only existence check for a native browser AI surface; it never calls it and makes no network request.

When future engines leave the browser

Pro and Bring engines are placeholders today. When implemented, anything that transmits data must:

  • set leftBrowser: true and surface it visibly in the UI,
  • be strictly opt-in,
  • keep user-provided keys in client-controlled storage / env, never committed.

Reporting

This repo is private during v0.1. If you find a security issue, contact the maintainer directly rather than opening a public issue.

Dependencies

Runtime deps are limited to React. Build deps are Vite + TypeScript + the React plugin. No AI SDKs. Keep the dependency surface small and audited.

There aren't any published security advisories