The Unreasonable Effectiveness of VEX in NixOS
NixOS configuration can make vulnerability triage reproducible: encode the conditions that make a CVE unreachable, then generate a VEX statement that disappears if those conditions stop holding.
The example starts with a scanner flagging OpenSSH for a 2007 username-enumeration flaw. The author checks the actual conditions—OPIE support, PAM configuration, and keyboard-interactive authentication—and shows how NixOS’s declarative configuration makes those assumptions machine-checkable. The accompanying nixos-vex project turns that into a build artifact that can be passed to Grype, reducing the reported count by one without hiding unrelated findings.
This is an early project and the author explicitly says not to treat it as a high-trust data source yet. The useful idea is the auditable workflow: document why a finding does not apply and automatically revisit that claim whenever configuration changes. The Hacker News discussion had no comments when checked.