StackGuardian / StackGuardian/tirith
feat(cli): `--fail-on-severity critical|high|medium|low`
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 165
- Forks
- 42
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 11
Description
meta.severity exists and policies set it; nothing reads it. Exit 3 means "something failed" with
no way to say fail on critical, warn on medium — the difference between a gate teams adopt
gradually and one they switch off after the first noisy Friday. Add the flag, defaulting to today's
behaviour; combined with policy packs this becomes "run the CIS pack at high+".
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the CLI entry point and trace how policy results expose meta.severity and produce exit status 3. Add the --fail-on-severity threshold while preserving today’s default behavior, then verify that policy packs fail only at or above the selected severity.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 70/100