How verdicts work

Update or Wait watches official release sources for each product — vendor RSS feeds, GitHub releases, vendor release-note pages and endoflife.date — and creates a page for every stable release.

Community reports. Every few hours we search the relevant subreddits for posts that mention each recent version. Each post is labelled problem, fine or mention by a small AI model, cross-checked with keyword rules. Visitors can also vote "updated fine" or "it broke something" once per release.

CVEs. CVE IDs named in release notes are linked directly. We also query the NIST National Vulnerability Database and link CVEs whose description says they are fixed in (or affect versions before) a specific release.

Calibration. People post when an update breaks something and rarely when it doesn't, and popular products get more posts of every kind. So we compare each release with what is typical for that product (the median number of problem reports per release), count ordinary discussion of a version as weak evidence that it's being used normally, and ask for more evidence before flagging a release that has been out for weeks.

Verdicts.

• Too early to tell under 3 days old with no clear problem signal.
• Not checked yet we haven't searched for community reports on this version yet.
• Release candidate / early access a test build that isn't on the vendor's stable channel yet. Some vendor feeds mix these in with stable releases, so we flag them (for UniFi: notes that need a UniFi OS version that isn't stable yet, or a version line Ubiquiti's stable update channel hasn't reached). They never count as a product's latest release.
• Probably fine — wait a few days under a week old with no real problem signal.
• Wait / check reports problem reports make up a noticeable share of the discussion (recent releases), or there are clearly more than usual (older releases).
• Problems reported problem reports well above what is typical for that product, and a large share of what people are saying.
• Safe to update out for a week or more, positive reports and no problem reports.
• No widespread problems out for a week or more with only a few isolated problem posts — normal background noise for widely used software.
• No problems reported out for a week or more and no problem reports found (but also few or no positive ones).

Verdicts are automated and can be wrong. A quiet release is not a guaranteed-safe release, and security updates may be worth installing promptly even when some users report issues. Always back up first.

Update or Wait is independent and not affiliated with any vendor listed.