Data Integrity Risk
Detects unchecked casts, mass assignment without validation, and SQL ON CONFLICT IGNORE patterns that silently discard errors.
Why this rule exists
Silent data discard is the worst kind of bug: the system behaves correctly under tests, but production data slowly diverges from reality. By the time anyone notices, the audit trail is gone.
Code example
+ INSERT INTO orders (id, total) VALUES (@id, @total) ON CONFLICT DO NOTHING;+ INSERT INTO orders (id, total) VALUES (@id, @total)
+ ON CONFLICT (id) DO UPDATE SET total = EXCLUDED.total
+ WHERE orders.updated_at < EXCLUDED.updated_at;Configuration
Disable or adjust the severity of this rule in .gauntletci.json:
{
"rules": {
"GCI0015": { "enabled": true, "severity": "Block" }
}
}See Configuration for the full schema.
Related rules
Data and Schema Compatibility
Detects removed serialization attributes and enum member removals that may break wire formats or persisted data.
Idempotency and Retry Safety
Detects HTTP POST endpoints without idempotency keys and raw INSERT statements without upsert guards, which are unsafe under retry logic.
SQL Column Truncation Risk
Detects short nvarchar(N) or varchar(N) column definitions that may silently truncate data when real-world values exceed the column width.
Implemented in src/GauntletCI.Core/Rules/Implementations/GCI0015_*.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.