The problem with library updates
You rename a layer. Delete an unused variant. Change a property type. Hit publish.
Then the bug reports start. Instances are broken. Developer code references point at nothing. Designs that looked fine yesterday now show detached components.
Design system changes are invisible until they break something. By then it's too late.
Know what will break before you publish
Component Guardian takes a snapshot of your component library, then compares your edits against that baseline. You see exactly what changed, how severe it is, and which components are affected.
Run it before you publish. Fix the issues that matter. Ship with confidence.
What it catches
Errors that will break existing instances
Removed components. Deleted properties. Property type changes. Removed variant options. Conflicting variants that block publishing entirely.
Warnings that may break code references
Renamed layers. Removed layers. Deleted nested instances.
Click any issue to jump straight to the affected component, even if it's on another page.
How it works
Baseline snapshots
Capture your library's current state with one click. The snapshot stores directly in your Figma file, so everyone on the team works from the same source of truth.
Scan on demand
Run a scan whenever you're ready to check your work. Toggle property and layer checking separately. Adjust scan depth for large libraries.
Export changelogs
Generate shareable reports when you need to communicate changes to your team or document what shipped.
Built for real libraries
Handles enterprise-scale component libraries through intelligent data chunking. Uses stable component keys for reliable matching that survives renames. Detects layer renames through positional heuristics instead of flagging misleading add/remove pairs.
Built with Preact. Zero external dependencies. Everything runs locally in Figma.