Security & Trust · Stellar Content Inc. (d/b/a LeanLM)
Security Overview
Encryption in Transit & at Rest
All traffic to leanlm.ai and api.leanlm.ai enforces HTTPS with TLS 1.3 and strict HSTS/CSP headers. Account billing ledgers and ephemeral CLI workspace storage are encrypted at rest with AES-256.
API Key & Installer Integrity
eco_live_... keys are stored server-side as cryptographic hashes; raw secrets are displayed once at issuance. On macOS/Linux, ecocoder login stores keys at ~/.ecocoder/key with 0600 permissions, and the CLI binary publishes its SHA-256 checksum on /quickstart.
Tenant & Workspace Isolation
Direct HTTPS requests process prompts in memory without staging repository files. When using the optional ecocoder CLI wrapper, staged source files are scoped to a per-tenant, per-session prefix purged on exit (≤24h sweep on abnormal disconnect).
SOC 2 & Compliance Status
SOC 2 Type II: Not yet certified (planned for H2 2027 following commercial GA). The public Evaluation Preview is not certified for HIPAA/BAA, PCI-DSS, or FedRAMP workloads.
Supply-Chain & Client-Side Footprint
- Zero third-party packages in the CLI: The optional
ecocoderhelper is a single inspectable Python 3 standard-library script (zeropipdependencies) that you can read in full and verify via SHA-256 before execution. - Per-process environment scoping: Running
ecocoder claudeorecocoder piscopesANTHROPIC_BASE_URL/OPENAI_BASE_URLstrictly to that child process without altering global shell profiles. - Local file-sync preview: Run
ecocoder sync-previewto inspect eligible staged files locally before connecting, or use Direct HTTPS for zero repository file staging (full data lifecycle →).
Vulnerability Reporting
If you discover a security vulnerability in leanlm.ai, api.leanlm.ai, or the ecocoder CLI, email [email protected] with reproduction steps. We acknowledge security reports within 1 business day and do not pursue legal action against good-faith researchers who avoid accessing other tenants’ data or degrading service availability.