Status & transparency

What is current, stale, or unknown

This page reads public deployment receipts, scanner health, and versioned repository artifacts. Missing, malformed, future-dated, or unreachable evidence is shown as unknown, not silently treated as healthy.

← Back to Site Behavior Lab

Live deployment

Public site and scanner

Checking

Checking the public deployment and scanner health endpoints…

Site revision
Unknown
Scanner revision
Unknown
Health observed
Unknown

Site receiptScanner health JSON

Publication freshness

Evidence and measurement inputs

Latest eligible corpus evidence

Unknown

Aug 11, 2026, 4:24 AM UTC

93 distinct sites currently make up the corpus sample a report page compares a scan against; 99 sites have at least one successful load.

This date and this site count both describe the one measurement cohort behind that comparison, and each percentile card names its own denominator. Category medians are published one cohort per category and span 3 cohorts in total, so no single cohort backs every published aggregate. Current means no more than eight days old. It does not mean every site was refreshed in that window. A site that loaded but whose evidence was cut short, by a request cap or a censored family, is counted as covered and never as measured, so the two numbers differ by more than failed loads. Nearly all committed corpus reports are frozen schema v1 from the disclosed fallback collection lane; the methodology states what v1 evidence can and cannot support.

Brave default-list snapshot

Unknown

Aug 11, 2026, 6:35 PM UTC

31 source files · manifest c16dadd4e996

Current means no more than eight days old. A failed refresh never replaces the last validated snapshot.

Recorded toolchain

Versions that shape the measurement

Playwright
1.62.1
Ad-block engine
adblock-rust-0.13.2
Service catalog
hand-curated-2026.08
Catalog entries
146

Exact browser versions and per-report toolchain identities remain attached to each report. See the methodology for what these inputs can and cannot establish.

Monitoring evidence

Checks and incident visibility

GitHub Actions runs the production posture monitor and records delivered successes and failures. GitHub scheduling is best-effort, so an absent run is not proof of uptime. The browser check above verifies only the public endpoints it can reach now.

  • Production health history
  • Featured-corpus refresh history
  • Measurement-input refresh history
  • Open project issues and managed incidents
AboutGlossaryStatusCatalogMethodologyPrivacySecurityCorrectionsSource