Skip to content

docs: omitting SEVERITY_THRESHOLD is not report-only - #36

Open
Paramjeet-singh-neu wants to merge 1 commit into
trustabl:mainfrom
Paramjeet-singh-neu:docs/eval-report-only-recipe
Open

docs: omitting SEVERITY_THRESHOLD is not report-only#36
Paramjeet-singh-neu wants to merge 1 commit into
trustabl:mainfrom
Paramjeet-singh-neu:docs/eval-report-only-recipe

Conversation

@Paramjeet-singh-neu

Copy link
Copy Markdown

Summary

docs/EVALUATION.md told people to omit SEVERITY_THRESHOLD for a report-only trial, and that running the CodeBuild project alone "does not gate anything real".

Omit is the default (none). The wrapper still fails when the binary exits 1, which is any finding at medium or above. So omit is the default gate, not report-only. Running the project on its own still turns the build red; it just is not in a pipeline yet.

A true report-only run is the || true wrap already documented in codepipeline/README.md. Two sentences, one file. Independent of the other EVALUATION.md PRs (exit-code table, STRICT, env outputs).

Test plan

  • Skim the "Running it here" / trial paragraphs against scan/trustabl-scan.sh (NATIVE_CODE=1 still fails when SEVERITY_THRESHOLD is unset)

Made with Cursor

The evaluation guide said to omit SEVERITY_THRESHOLD for a report-only
trial, and that running the CodeBuild project alone "does not gate
anything real". Default none still fails on native medium+, so omit is
the default gate. Report-only is the || true wrap in the CodePipeline
README.

Co-authored-by: Cursor <cursoragent@cursor.com>
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.

1 participant