Will It Vibe?getStaticProps without a revalidate strategy
Part of Architecture & Best Practices, which counts for 15% of the overall score. When this check fires it deducts 4 points from that category, once per scan, no matter how many places it turns up.
What it detects
A page uses getStaticProps but never sets revalidate, so it is built once and the content is frozen until the next full deploy. Heuristic: fully static content is a legitimate choice, so this is a nudge to confirm the page is meant to never update.
Why it matters
A page that uses getStaticProps without a revalidate value is generated once at build time and then never changes until the next full deploy. If the underlying data updates (prices, listings, content), users keep seeing stale pages. This is a heuristic: genuinely static content is a valid reason to omit revalidate, so treat it as a prompt to confirm intent.
How to fix it
If the page shows data that can change, add a revalidate value (in seconds) to the getStaticProps return so Next.js regenerates the page in the background on a schedule (Incremental Static Regeneration). Pick an interval that matches how fresh the data needs to be. Leave it off only for content that truly never updates between deploys.
The paid report includes a ready-to-paste prompt for your AI coding agent for every check it finds, pointed at the exact findings from your scan. See pricing
Does your repo trip this check?
Paste a GitHub URL or drop a project folder. Scans run in your browser and take seconds.
Scan your repo