StackGuardian / StackGuardian/tirith
feat(terraform_plan): `module_address` filtering on every operation
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 165
- Forks
- 42
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 11
Description
module_address sits on every resource_changes entry and no operation exposes it. Add it as a
filter ("module_address": "module.approved/*"): nothing outside approved modules, no change
touching two teams' modules at once, per-module ceilings — combined with action-filtered count,
blast radius per owner, which is what approval routing needs.
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 by locating where resource_changes entries are filtered for operations and how action-filtered count is handled. Done means module_address filtering applies to every operation, excludes non-approved modules and cross-team changes, and enforces per-module ceilings alongside action-filtered count.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100