All Drift Types
Comprehensive drift detection for modern frontend codebases
Hardcoded Values
Find colors, spacing, and fonts that bypass your design tokens.
Duplicate Components
Detect similar components that should be consolidated.
Naming Drift
Catch inconsistent naming conventions across your codebase.
Prop Mismatches
Find when the same prop has different types across components.
Deprecated Patterns
Track components marked as deprecated still in use.
Accessibility Issues
Find missing ARIA labels, focus traps, and contrast issues.
Orphaned Components
Components in code but missing from Figma or Storybook.
Unused Tokens
Design tokens defined but never referenced in code.
How Drift Detection Works
Scan
Buoy parses your codebase to build a map of all components, props, and style values.
Analyze
Compares against your design system config to identify patterns that don't match.
Report
Outputs drift signals with severity, location, and suggested fixes.
Step 1: Find Drift
Every issue includes the exact file, line, and what to change.
Step 2: Catch at the PR
Add Buoy to CI. Design drift never reaches main.
Missing aria-label Critical → Add aria-label={buttonText}
Hardcoded color #ffffff → Use var(--color-bg)
Deprecated component NavHeader → Use Navigation
What You Get
Clarity, not just data. Every scan ends with concrete next steps.
PR Checks
Catch drift at the PR. Every issue shows the exact token to use instead.
buoy drift check --ci Clear Explanations
Every issue includes the file, line, and exactly what needs to change.
buoy drift check --format detailed Coverage Score
Track design system adoption over time. Show leadership real numbers.
buoy show health Visible Outcomes
👩💻 For Developers
- ✓ No guessing — exact file, line, and fix
- ✓ CI catches issues before they merge
- ✓ PR checks catch issues before review
- ✓ Less time debating, more time building
📊 For Leaders
- ✓ Real adoption numbers, not estimates
- ✓ Track improvement week over week
- ✓ Prove design system ROI with data
- ✓ Identify which teams need help
Not ready to install? Start with a manual audit.
20 warning signs to look for in your next code review. Spot drift before it spreads.
No spam. Unsubscribe anytime.
Why Design Drift Matters
Without Drift Detection
- ✗ Inconsistent UI across the app
- ✗ Design system becomes optional
- ✗ Harder to maintain and update
- ✗ No way to measure adoption
With Buoy
- ✓ Consistent, cohesive UI
- ✓ Design system enforcement
- ✓ Easy global updates via tokens
- ✓ Real adoption metrics