Source code
Code quality
Releases
Missing / stale .env.example
Part of the Production readiness check · fix arrives as a pull request
What it is
There is no .env.example, or it has drifted from the variables the code actually reads.
Why it matters
Setting up the project becomes a guessing game of running it, reading the crash, adding a variable, repeating. Missing variables also tend to surface as confusing runtime behaviour rather than a clear startup failure.
How to fix it
Keep .env.example listing every variable with a placeholder value and a comment on what it is for, and validate the environment at startup against a schema so a missing one fails immediately with a useful message.
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.