Two kinds of evidence
A patch page can carry two different things, and they are never merged into one number:
- Vendor release information — what the publisher says changed. This is the factual baseline for what an update contains. It does not establish that the update is safe to install.
- User-reported experiences — individual public reports that name the exact release. Every counted report is linked, so you can read the original and judge it yourself.
A page that carries vendor information and no user reports is labelled as such. That combination is not a safety finding.
What a patch page shows
- The exact release identity, including the build where a product ships several builds under one version.
- Links to the vendor source and to every counted report.
- How many confirmed patch-specific reports were counted, including when that number is zero.
- The evidence state, the date the vendor source was last checked, and the date the newest accepted user report was captured.
- Whether coverage for that exact release is limited, incomplete or out of date.
How official sources are labelled
Official vendor pages are not all the same kind of document, and they are not recorded as though they were. Release notes, a fixed-issue list, a security advisory and a changelog are release documentation. A feature summary, a “what’s new” article, a download page, a release-status page and an official announcement are still official, but they are a different kind of document.
Each official citation on a patch page carries the kind of document it is, next to the link. That label, not the section heading, is what tells you what the source actually is: the Official Patch Notes heading is shown for any captured official body text, so a page whose official source is a download page or a release-status page still appears under that heading. Read the citation label.
An official source can also be linked with a missing-detail note. That means the page was reached but its body text could not be captured, and it is recorded rather than hidden.
What counts as a confirmed report
- The report or comment names the exact patch, version or update.
- Or the parent thread or page title names the exact patch, version or update.
- Where the parent thread is specific to one release, replies inside that thread count, unless a reply clearly moves to another version or an unrelated issue.
Every confirmed report carries equal weight. Where a report was published does not multiply it and does not discount it.
What does not count
- General complaints about the software.
- Posts that only say “after the update” with no release-specific parent thread.
- Mentions that cannot be tied to the exact version on the page.
- Reports that clearly refer to a different version, a driver, an operating-system update or an unrelated add-on.
Reports with too little context are excluded completely. They are not counted at reduced weight and they are not used as a weak signal.
Evidence states
- Official source only
- A vendor source has been captured. No confirmed patch-specific user reports are counted for this release. This is the most common state on the site, and it is not a safety finding.
- Verified reports
- The page carries confirmed patch-specific reports that were captured earlier. Check when the newest accepted report was captured before treating them as current.
- Live consensus
- The release’s confirmed patch-specific user reports have reached the High evidence-strength level, and the community collection for that exact release is running and healthy. It is withdrawn automatically when that collection stops, fails, or has not run for 14 days. That is a test of the collection, not of the reports: the date the newest accepted report was captured is a separate fact, and a live release can show an older date there while collection keeps running and finds nothing new to accept. A vendor’s own release notes never count toward it.
- Insufficient data
- There is not enough vendor or user evidence to support anything beyond a placeholder state.
No state means an update is safe. “Official source only” and “Insufficient data” both mean the user-report picture for that release is empty or thin, not that it is clear.
When coverage is limited or outdated
Report collection is not exhaustive and it is not continuous. For any given release it may be incomplete, out of date, or not running at all. Each patch page states the collection position for that exact release. Where there is collection history for that exact release, the page also names each source family it checked and the result of each check; where there is none, the page is labelled Official source only and names no sources.
A check can complete, complete and find nothing, complete only partly, return a low-confidence result, be refused by the source, fail with an error, be out of date, need manual review, or not be running at all. Some sources are no longer called: where a source refused request after request over a sustained period, AUXSAYS stopped calling it rather than spending every cycle timing out against it, and the patch page says so for that source. Those sources are kept and can be restored if the source starts answering again.
None of those outcomes is evidence about the update itself. A refused, stopped or failed check means AUXSAYS does not know. It does not mean users reported problems, and it does not mean they reported none.
Each page also states how many of its sources returned a usable, recent result, and says when that number is below the minimum AUXSAYS treats as adequate coverage. Where coverage for a release is thin or stale, the page says so rather than presenting the result as settled.
Dates mean different things
A patch page can carry several dates: when the vendor source was last checked, when vendor detail was last captured, when the record itself last changed, and when the newest accepted user report was captured. They move independently. A recent collection check does not mean a new report was accepted, and an old capture date does not mean collection has stopped: the monitoring status states that separately. One recent date is not proof that the others are recent, and a vendor check moving does not mean the recommendation, the report count or the evidence state changed.
Limits of these notes
These notes describe what AUXSAYS counts and what it shows. They are not a claim that every public report has been found, that a listed release has been tested, or that a recommendation will hold. Recommendations are based on the available information and may change as new reports emerge.
Where the evidence for a release is absent, limited or stale, prefer the page’s own stated caveats over the recommendation on its own.