Proof
gstack’s daily /cso report stops listing security findings it can’t prove
gstack's daily /cso security report now leaves out any finding it cannot prove. If the damage needs code outside the snapshot, or a future change, or exposes nothing sensitive, it is logged as coverage instead.
False alarms
Five of six false alarms gone, every planted bug still caught
That cuts false alarms. Before, about one daily finding in nine was wrong, mostly this kind. In a twelve-cell pilot, five of six false alarms disappeared, and every planted bug was still caught.
Trade-off
Daily reports also drop low and informational issues
/cso/cso --comprehensiveThe cost: daily reports also drop real issues rated low or informational. The pilot lost four of its thirteen control cases this way. Comprehensive mode still reports them, and keeps unproven candidates as labeled hypotheses.
Your setup
Shorter daily reports, fewer false alarms
CHANGELOG.mdgstack 1.91.141.0 release notesIf you run /cso every day, expect shorter reports with fewer false alarms. Which do you run on your own repo: the daily /cso, or comprehensive mode?















