StackGuardian / StackGuardian/tirith
research(interop): interoperability with external scanners
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 165
- Forks
- 42
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 11
Description
Import direction only — translating another engine's policy language wholesale is not feasible,
and competing on raw language expressiveness is a losing comparison. Realistic scope: consume
another scanner's output as a document via named multi-input, and document side-by-side
patterns. Related: #215, #161, #162.
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
No files or tests are named. Start by reviewing how named multi-input documents are handled, then read related issues #215, #161, and #162 and compare the external scanner output patterns the project wants to support. Done should mean a defined import scope and documented side-by-side interoperability patterns.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100