SBL-CORR-2026-001: The historical input-probe disclosure overstates coverage. Unload-only transmissions were not reliably recorded. Focus and blur handlers could run, and per-field failures were not fully counted. These reports cannot establish absence of input transmission outside their retained observations.
github.com matched an interaction-monitoring signal involving a cross-site script.
SBL-CORR-2026-001: The historical input-probe disclosure overstates coverage. Unload-only transmissions were not reliably recorded. Focus and blur handlers could run, and per-field failures were not fully counted. These reports cannot establish absence of input transmission outside their retained observations.
The scan observed signals a non-expert should not have to decode from raw request tables.
The cards below translate the evidence into plain language; severity reflects fixed reference thresholds, not measured population percentiles. The request log, domain table, and methodology remain below for verification.
170 requests observed in one controlled visit.
Context
3 requests matched Brave Shields filter lists
3 requests matched the default filter lists of Brave Shields, the ad and tracker blocker built into the Brave browser, while loading normally.
Computed with Brave's own ad-block engine and default filter lists in classification mode: matched requests were not blocked by the scanner and remain in this report's observed request counts. Matching shows what Shields would target on this visit's traffic; an actual Shields visit blocks these and also prevents their follow-on requests, so this number is neither a measured block count nor the total effect.
The hand-curated service catalog separately matched 0 request rows in this visit.Show matched requests
Low signal
No change observed in the Brave-list blocking attempt
The blocking visit (the scanner configured to apply Brave's ad-block engine and default Shields filter lists (a simulation in this scanner's browser, not a live Brave-browser visit; application was not verified)) showed no change in the comparable metrics (third-party requests, third-party cookies and tracking-related service requests).
The blocking visit's engine directly blocked 3 requests; ad rotation, experiments, or caching between the two visits can offset or outweigh what blocking removed, which is how totals can hold steady or rise despite direct blocks. A single paired comparison can also reflect run-to-run variance (ad rotation, caching, experiments), so treat this as no observed difference for this pair of visits, not evidence that blocking removes nothing.
Signed per-metric differences between the two visits; nothing is summed across metrics.Show matched requests
Context
No known services matched
This scan did not match any third-party domains to the service catalog or another identity source.
No known operator or catalog entity was matched. This scan could not identify 2 of the 2 third-party hosts recorded here, so it cannot say who operates them. That is a limit of identity coverage, not evidence about the site.
The automated visit did not observe third-party cookies.
This does not prove the site never uses cookies; it means this visit did not observe third-party cookies.
6 cookies total in this report.No third-party cookies observed.
Context
Input-monitoring signal involving a script from another domain
Listener coverage that could observe typing-related input events was registered through call chains that included a script served from another registrable domain, whose operator this scan did not establish.
This is a behavioral instrumentation signal from listener registration, stack-attributed script origins, and known-vendor requests: it shows the page was instrumented to observe interaction, not that anything was transmitted. Stack attribution records the script origins present in the bounded registration call chain; a cross-site origin in that chain does not by itself establish that the cross-site script registered the listener, because first-party code can register its own listeners through a helper served from elsewhere. A different registrable domain is also not by itself a different operator: sites commonly serve their own scripts from a separate asset domain, so the card says third party only when the catalog or reviewed ownership attributes an origin to another organization. On scanners that run the active keystroke-capture probe, actual transmission is tested separately (a synthetic value is typed, never real input, and no typed values are collected); treat this card as a review prompt rather than proof.
259 interaction-listener registrations with https://*.githubassets.com/ in the registration call chain and 107 input-listener registrations with https://*.githubassets.com/ in the registration call chain
Nothing observed
No fingerprint-like API calls observed
The scan did not observe the instrumented high-entropy browser APIs.
This is an observation layer, not proof that fingerprinting is impossible.
0 API families recorded.
Raw evidence
Open the interactive evidence explorer
The findings above are built from the stored report. Load the request rows, domains, cookies, storage keys, browser signals, visit phases, charts and CSV export when you want to check them; the versioned report JSON is always available below without this interface.
This versioned report is currently retained in the public corpus. Follow the currently retained site history, repeat the same public route when it is available, or request a transparent evidence correction.
Exact build and instrument digests were not recorded by this legacy schema.
Variant visit
Started
Run quality
complete; derived from status and warnings
Scanner
playwright-chromium
Browser
151.0.7922.34
Redaction
not recorded by this schema
Provenance
Exact build and instrument digests were not recorded by this legacy schema.
Recorded provenance is self-reported measurement metadata, not a cryptographic attestation. The public versioned report JSON contains the retained public evidence; see the methodology for interpretation and retention limits.
This report covers what the scanner measures, not everything a site can do. 16 browser surfaces are not instrumented at all (Every page except the one that was scanned; Anything that only loads after scrolling or interaction; Why a request happened, as a causal chain; and 13 others), 3 capabilities are declined by policy, and 3 are outside what any single visit can see. Their absence from this report is not evidence that they did not occur. Read the published coverage boundary.
Detector accuracy is unmeasured. No calibration study currently publishes a precision or recall for the detectors on this page, so a detector match here is a recorded observation, not a calibrated classification. How detector accuracy is measured.
Approved use boundary: This report is investigative evidence that requires independent corroboration. It is not a standalone legal determination and not the sole exhibit in a legal proceeding. Recorded in this project's release manifest on .