Skip to content

docs: add generation-time vs scan-after-write comparison (#42) - #45

Open
mafujahmedridoy22-commits wants to merge 1 commit into
ehtishammubarik:masterfrom
mafujahmedridoy22-commits:docs/comparison-section
Open

mafujahmedridoy22-commits wants to merge 1 commit into
ehtishammubarik:masterfrom
mafujahmedridoy22-commits:docs/comparison-section

Conversation

@mafujahmedridoy22-commits

Copy link
Copy Markdown

Fixes #42

Adds a README section that states, factually and without a takedown, that
stackmason is a different category of tool: it prevents insecure HCL from
existing at generation time, while Checkov/tfsec/OPA scan what is already
written. Includes the tool table (when it runs / what it needs installed /
what it does on a finding) and states the honest limits in the same section
(AWS-only, 3 of 9 stacks ready).

State the category difference plainly and factually: stackmason prevents
insecure HCL from existing, while Checkov/tfsec/OPA scan what is already
written. Table covers when each runs, what it needs installed, and what it
does on a finding, including the honest limits (AWS-only, 3/9 stacks).

Closes ehtishammubarik#42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add a "generation-time vs scan-after-write" comparison section (stackmason vs Checkov/tfsec/OPA)

1 participant