Report a vulnerability
- Preferred: GitHub's Report a vulnerability (Security โ Advisories) โ private vulnerability reporting is enabled on the repo.
- We aim to acknowledge within a few days and to coordinate a fix and disclosure timeline with you.
Include the affected version/commit, a description, reproduction steps, and impact. Proof-of-concept code is welcome โ but never test against systems or data you don't own.
Supported versions
wyrm is pre-1.0; only the latest main is supported. Fixes land on
main and in the next tagged release.
Scope & handling notes
- Untrusted models. wyrm parses OTM documents (YAML/JSON) that may come from other repos or contributors. Parsing is memory-safe Rust with no code execution โ a malformed model should fail to parse, never escape the parser.
- Importers invoke external tools.
wyrm initshells out tohelm,kustomize/kubectl, and reads Terraform/plan sources you point it at. Those tools run their own templating โ only runwyrm initon infrastructure sources you trust, as you wouldhelm templateorterraform plan. - The GUI live-writes the file.
wyrm-guisaves every edit back to the.otm.yamlyou opened; it touches no other path and makes no network calls. - Automated hardening. Dependencies and Actions are monitored by
Renovate; every change is gated by CI (fmt, clippy
-D warnings, tests, cargo-deny, CodeQL, Trivy, MegaLinter) before merge. Our own workflows are SHA-pinned and statically analysed by zizmor.
What is not a vulnerability
- A "missing" threat finding โ the rule library is best-effort and intentionally extensible, not a guarantee of completeness. Propose a rule instead.
- Findings that require an already-compromised host or working tree.
The full policy also lives in SECURITY.md at the repo root.