Resource Lifecycle
Detects disposable resources allocated without a using statement or try/finally disposal, leading to connection and handle leaks.
Why this rule exists
An undisposed SqlConnection or FileStream eventually exhausts the pool or the OS handle table. The symptom is a slow degradation that production alerting will only catch after customer impact.
Code example
+ var conn = new SqlConnection(cs);
+ conn.Open();
+ var cmd = conn.CreateCommand();+ using var conn = new SqlConnection(cs);
+ await conn.OpenAsync();
+ using var cmd = conn.CreateCommand();Configuration
Disable or adjust the severity of this rule in .gauntletci.json:
{
"rules": {
"GCI0024": { "enabled": true, "severity": "Warn" }
}
}See Configuration for the full schema.
Related rules
Concurrency and State Risk
Detects async void methods, blocking async calls (.Result, .Wait()), static mutable state, and patterns that introduce deadlock risk.
External Service Safety
Detects unsafe HTTP client usage and external service call patterns that lack timeout, cancellation, or retry configuration.
Implemented in src/GauntletCI.Core/Rules/Implementations/GCI0024_*.cs.
Eric Cogen -- Founder, GauntletCI
Twenty years in .NET production. Most of those years, the bugs that hurt me were not the ones tests caught. They were the assumptions I did not know I was making: a removed guard clause, a renamed method that still did the old thing, a catch {} that turned a page into a silent dashboard lie. GauntletCI is the checklist I wish I had run before every commit. It runs the rules I learned the hard way, so you do not have to.