LineageGuard compares two schemas, classifies breaking versus additive changes, then follows column mappings through downstream datasets. The goal is to review blast radius before a producer change reaches a mart, export, or dashboard.
The lineage graph uses explicit column mappings. Removed columns, type changes, and nullable→required changes are treated as breaking; a nullable/defaulted added column is additive. This is not a warehouse catalog or automatic SQL parser. Source and tests ↗