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.
Why this rule exists
varchar(50) for an email is fine until the first user with a long address. Silent truncation produces data corruption that is impossible to recover after the fact.
Code example
+ Email nvarchar(50) NOT NULL,+ Email nvarchar(320) NOT NULL, -- RFC 5321 maxConfiguration
Disable or adjust the severity of this rule in .gauntletci.json:
{
"rules": {
"GCI0050": { "enabled": true, "severity": "Info" }
}
}See Configuration for the full schema.
Related rules
Data Integrity Risk
Detects unchecked casts, mass assignment without validation, and SQL ON CONFLICT IGNORE patterns that silently discard errors.
Data and Schema Compatibility
Detects removed serialization attributes and enum member removals that may break wire formats or persisted data.
Implemented in src/GauntletCI.Core/Rules/Implementations/GCI0050_*.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.