External Service Safety
Detects unsafe HTTP client usage and external service call patterns that lack timeout, cancellation, or retry configuration.
Why this rule exists
Default HttpClient timeouts are 100 seconds. A single slow downstream service can drain your entire thread pool and take the whole app offline before any health check fires.
Code example
+ var http = new HttpClient();
+ var resp = await http.GetAsync(url);+ var resp = await _httpClientFactory.CreateClient("orders")
+ .GetAsync(url, ct); // factory configures timeout, retry, circuit breakerConfiguration
Disable or adjust the severity of this rule in .gauntletci.json:
{
"rules": {
"GCI0039": { "enabled": true, "severity": "Block" }
}
}See Configuration for the full schema.
Related rules
Resource Lifecycle
Detects disposable resources allocated without a using statement or try/finally disposal, leading to connection and handle leaks.
Concurrency and State Risk
Detects async void methods, blocking async calls (.Result, .Wait()), static mutable state, and patterns that introduce deadlock risk.
Idempotency and Retry Safety
Detects HTTP POST endpoints without idempotency keys and raw INSERT statements without upsert guards, which are unsafe under retry logic.
Implemented in src/GauntletCI.Core/Rules/Implementations/GCI0039_*.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.