if you've ever shipped an SDK update and then, three weeks later, a GitHub issue lands saying "the README example doesn't work," you'll recognize this problem.
The code changed. The docs didn't. Users hit broken snippets. You only find out from the angry messages.
I built DriftGuard because I kept seeing this in Web3 SDKs - contracts get upgraded, the TypeScript SDK evolves, but the docs and example apps lag behind. By the time someone reports it, a dozen users have already been confused.
What it is
DriftGuard is a CLI + GitHub Action that detects "drift" - when changes in one layer of your project break another layer. It runs in CI on every pull request and posts inline annotations at the exact line that broke.
