Qubes code audit

I’d like a community driven program where the QubesOS team selects a QubesOS repository/component of their choosing, and for that week or month that repository/component is highlighted on the forum/website/Github/etc for a community audit. A thread can be made to discuss any findings of concern, clarifications on what code is doing for the less savvy, better ways of doing things, code cleanup, etc.

This way we can get a focused look on each area of concern instead of multiple eyes all over the place. We would essentially be doing a group audit, component by component over time.

10 Likes