Source code
Releases
Stability
No feature-flag on risky path
Part of the Production readiness check · fix arrives as a guide
What it is
A significant or risky code path ships without a flag that can turn it off independently of a deploy.
Why it matters
When it misbehaves in production your only remedy is a rollback, which reverts everything else in that release too. Under incident pressure that is slower and riskier than flipping one switch.
How to fix it
Put risky paths behind a flag that can be changed at runtime, default it off, and roll out gradually. Remove the flag once the path has been stable for a while so the codebase does not accumulate them.
Run them all on your app
Connect your repo and your live services with read-only scopes. The first scan is free, and nothing changes without your approval.