StackGuardian / StackGuardian/tirith
feat(cli): named multi-input — `-input plan=plan.json -input scan=scanner.json`
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 165
- Forks
- 42
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 11
Description
One document per invocation means no rule can correlate two sources — and every genuinely
interesting composition is a correlation: scanner flagged it and the plan replaces it; cost rose
and the change touches production; the plan contradicts the state. Named inputs plus a
per-evaluator document selector; with per-evaluator providers ("mixed-provider policies", above)
and eval_expression already combining evaluators, correlation comes free. Closes the intent
behind #214 (dynamic input).
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
The issue does not name files, tests, or a CLI entry point. Start by tracing how the CLI currently accepts its single document and how evaluators select inputs; define the expected behavior for named inputs, per-evaluator document selection, mixed providers, and eval_expression correlation, then add coverage showing multiple documents can be combined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100