Logic is going to get messy fast, rules engine?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.2k
- Forks
- 229
- PR merge metrics
- No merged PRs in 30d
Description
I've been thinking about this and relates to a few issues I've added recently.
I think the logic is going to get messy as we add more Threats, Mitigations, and add logic to alter severity while applying mitigations.
Does it make sense to continue creating a tightly coupled rules engine here vs using something existing?
Idk what exists for Python. For Java I've worked with Drools that would be perfect for this. So much so I had the fleeting thought to port this to Java to use it.
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 reviewing the existing threat, mitigation, and severity logic referenced in the issue, along with the related issues. Survey Python rules-engine options and compare them with continuing the current tightly coupled approach. Done means a concrete recommendation and agreed scope are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- security
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100