Helix StudioGenome IDE
← Docs
Helix CLI docs
Browse Helix CLI docs

Security Policy

We treat determinism and provenance as security features. Please report vulnerabilities privately and avoid filing public GitHub issues for exploitable findings.

Reporting a vulnerability

  • Preferred: GitHub Security Advisory (private report) on this repository.
  • Email: security@omniscoder.com (PGP optional; include a repro bundle or minimal payload when possible).
  • Response targets: acknowledge within 2 business days; triage and plan within 5; fixes land in the next weekly patch train (or faster for critical bugs).
  • Embargo: coordinated disclosure by default; we can issue CVEs when applicable.
  • Safe harbor: good-faith research that respects user data and avoids active exploitation is welcome; we will not pursue or assist legal action for such reports.

Scope

In scope: Helix CLI, Helix Studio, deterministic runtimes/backends, plugin host and registry handling, bundle/build artifacts we ship, and published schemas/specs. Out of scope: forks or unsigned third-party builds, EOL releases (>2 supported minors old), denial-of-service without safety impact, issues requiring prior root/VM escape, and hardware/driver flaws outside our control.

Assets and threat framing

See docs/threat_model.md for the detailed model. Critical assets are: artifact and bundle integrity, deterministic execution guarantees, policy/profile enforcement, trust store keys, plugin registry contents, and confidentiality of user inputs/projects.

Supply-chain posture

  • Pinned dependencies with checksums; release SBOMs attached to tags.
  • Deterministic plugin packages (.helixplugin) with HASHES + optional Ed25519 signatures; trust-store enforcement is documented in docs/policies/plugin_governance.md.
  • Build provenance and attestations tracked per docs/policies/release_provenance.md (hashes, signatures, SBOMs, and planned SLSA-style attestations).
  • Reproducibility bundles and verifier keep runtime outputs auditable against manifests.

Patch cadence

  • Regular: weekly patch train for security/stability fixes.
  • Critical: out-of-band releases within 72 hours of confirmation.
  • Backports: supported for the two most recent minor versions; older versions receive only documentation mitigations.

Contact for abuse or policy violations

Email security@omniscoder.com with subject [Helix Abuse] for suspected policy/profile bypass, compromised plugin registry entries, or distribution of malicious .helixplugin packages.