Detect targeting rules whose valueOverride equals the flag's defaultValue — a silent no-op that sends the same value to 100% of users. Surfaced in the dashboard banner, the CLI, and Flagify AI.
A targeting rule with rolloutPercentage=50 and valueOverride=true only splits users between true and true if the flag’s defaultValue is also true — users outside the rollout fall through to defaultValue, so 100% of users receive the same value the rule would serve. The rule is a silent no-op.
This release detects that configuration automatically across every project.
Dashboard — Flag Health banner
The Overview page now surfaces rule_value_matches_default warnings alongside the existing env_mismatch critical checks. Each warning shows the affected flag, the environment, and a one-line fix hint.
CLI — flagify flags health
A new subcommand scans the current project and prints every issue detected server-side.
flagify flags health --project <project-id>
JSON output (for CI gating) includes the fix field with a remediation suggestion. Exit code is always 0 — use jq -e 'length == 0' to fail builds when issues appear.
Flagify AI
The in-app assistant gained a get_flag_health tool, so asking “which flags have issues?” now reads the real health endpoint instead of guessing from the flag list.
Docs
- Targeting — Pitfall:
defaultValuecollides with your rollout value explains the semantics and the fix. - CLI reference —
flagify flags healthshows sample output and CI integration.
Packages affected
flagifyhq/api— newrule_value_matches_defaultissue type on/v1/projects/{pid}/overview/health@flagify/cli— v1.5.0, addsflagify flags health- Dashboard + Website — Flag Health banner extended, CLI docs updated