From 6efc3b3c1d6c39cd99e2cc2d43f511649a7f9c82 Mon Sep 17 00:00:00 2001 From: mafujahmedridoy22-commits Date: Sat, 7 Nov 2026 08:29:18 +0600 Subject: [PATCH 1/2] docs(readme): open with the validate-vs-apply gap Lead with the pain point that makes the tool worth searching for, instead of the tagline. Grounds the misconfiguration claim in cited sources rather than an unattributed statistic. Uses the existing tagline unchanged. Closes #41 --- README.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/README.md b/README.md index 9e531d2..5297fd8 100644 --- a/README.md +++ b/README.md @@ -1,5 +1,21 @@ # stackmason +**`terraform validate` passes. `apply` still fails.** + +Validate checks that your HCL is well-formed and type-correct. It does not check +that it means anything — an empty list and a null argument both pass. Cloud +misconfiguration is repeatedly cited as a leading cause of cloud security +incidents (IEEE [1](https://ieeexplore.ieee.org/abstract/document/11647997), +Verizon DBIR 2026), and most of it ships through a pipeline where every check +was green. + +stackmason is a **generation-time guardrail**: it refuses to write the insecure +default in the first place, instead of flagging it after the fact like a +scan-after-write linter. The result is a repository that is **secure by +default** — zero dependencies, no runtime tool needed — so "terraform validate +passes apply fails" stops being the failure mode you discover on your first real +plan. + **Answer some questions. Get a Terraform repository that is secure by default.** ![Python](https://img.shields.io/badge/python-3.10%20%7C%203.11%20%7C%203.12-3776AB?logo=python&logoColor=white) From bbe78e518bfc82c7b9f0cfbb6a630c2f515d8109 Mon Sep 17 00:00:00 2001 From: mafujahmedridoy22-commits Date: Sat, 7 Nov 2026 08:30:23 +0600 Subject: [PATCH 2/2] docs(readme): cite verified DBIR 2026 figure for misconfiguration claim Replace the unverifiable IEEE abstract link with the concrete, attributed figure from Verizon's 2026 Data Breach Investigations Report (cloud misconfiguration caused 14% of all global breaches in Q1 2026, up from 9% in 2024). The claim now cites only what the source actually reports. --- README.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 5297fd8..e15402c 100644 --- a/README.md +++ b/README.md @@ -3,11 +3,11 @@ **`terraform validate` passes. `apply` still fails.** Validate checks that your HCL is well-formed and type-correct. It does not check -that it means anything — an empty list and a null argument both pass. Cloud -misconfiguration is repeatedly cited as a leading cause of cloud security -incidents (IEEE [1](https://ieeexplore.ieee.org/abstract/document/11647997), -Verizon DBIR 2026), and most of it ships through a pipeline where every check -was green. +that it means anything — an empty list and a null argument both pass. +Misconfiguration is now the single largest technical breach vector: Verizon's +2026 Data Breach Investigations Report attributes 14% of all global breaches in +Q1 2026 to cloud misconfiguration, up from 9% in 2024 — and most of it ships +through a pipeline where every check was green. stackmason is a **generation-time guardrail**: it refuses to write the insecure default in the first place, instead of flagging it after the fact like a