c Code Health
3 open-source c repositories analyzed by activity-weighted risk — complexity × recent commit frequency. Sorted highest risk first.
redis/redis's module and networking layer carries the highest structural debt — 5 functions to address first
The riskiest function in redis/redis hasn't been touched in 51 days, but when it is next changed, whoever opens it will face a nesting depth of 13 and a long if-else chain dispatching across more than a dozen distinct server events. That structural weight is sitting silently in five critical-band functions spread across the module system, client lifecycle, cluster slot migration, and blocked-client machinery — none of them are burning right now, but all of them are overdue for refactoring before the next development push.
openssh-portable's option parsing and entry points carry the top risk
Every one of the top five riskiest functions in openssh-portable was changed within the last 30 days or sooner (4 to 30 days ago), and each carries 84 to 474 independent execution paths. I walk through where that leaves anyone shipping a change this week.
curl's test-server code carries the highest activity risk — 5 functions to address first
Five functions in curl's test infrastructure are both hard to reason about and being edited right now, and one of them, http_connect, is a 106-path tunnel handler that was changed four days ago.