On Thu, 05 Nov 2026, Xuneng Zhou <[email protected]> wrote: > I am wondering whether it's helpful to build a > temporary site or use existing tools to track those bugs after > filtering, auditing and grouping them.
That's the direction we are going with hackorum.dev. It already makes reading/searching/using the lists much easier, and we are working on many features that will move it even more towards a proper bug tracker / review tool based on the mailing list. You can also suggest ideas or PRs :) (we are already working on LLM-assisted automatic grouping, for example, soon available) > Another complementary tool that > seems helpful is something like the sashiko review system from the > linux community Thanks, that's a useful link I didn't know about. I already built something similar during the year (for now privately) for reviewing patches, which is based on the claude/codex CLI, so it works with subscriptions instead of API based billing. The long term goal with that is also to automatically run it for every patch submission (and commits, as sometimes there are changes between the last patch and the committed code), and to make it public, but I want to make it really good before I publish it. > That said, not sure about the degree of > that demand since there's a likely ceiling to the current growth of > bug reports I would be still more worried about the part that without a human actually looking at it, we are just risking disclosing/finding security issues more easier. I know LLMs are already capable of finding many, but we shouldn't make it even more easier by just dumping lots of unreviewed bugreports on the internet.
