The Problem: We all use feature flags, but they accumulate forever. Knight Capital lost $460M in 45 minutes due to a reused stale flag. Every team I've worked with spends 3-5 hours/week per developer managing technical debt, or worse, leaves them to accumulate. The industry does 20 trillion flag evaluations daily, yet most flags are never cleaned up.
How it works: - Monitors your repos for feature flags using AST parsing - Tracks flag lifecycle across pull requests - When flags go stale, automatically creates PRs to remove them - You review and merge - or ignore if the flag is still needed
The magic: You keep shipping features while FlagShark handles the cleanup. No more quarterly "flag cleanup sprints" or tech debt accumulation.
Currently supports Go, TypeScript/JavaScript, and Python. Detects LaunchDarkly, Unleash, Split.io, Flipt, and custom implementations.
Looking for beta testers! Free access for early users who can provide feedback:
- How stale should a flag be before suggesting removal? - Should it create one PR per flag or batch them? - What safety checks would make you confident auto-merging? - Which feature flag libraries does your team use?
If you're interested, comment here or sign up on the site. Let's eliminate flag debt together.