Today: the five AI headlines of the day → and the AI Wiki

What a claim record is How to read this page

One statement, bounded on purpose

The headline is a single claim that a named source supports. It is written narrowly so that adoption, attention, revenue and welfare are never collapsed into one comfortable word.

The three sections below the fold

What this does not establish is the boundary of the evidence. Counterevidence & uncertainty is what argues the other way. What would change the reading is the observation that would move it. A record missing any of the three is incomplete, not merely brief.

Primary routes are checkable

Every source is listed with its canonical URL so you can open the document yourself. A route that stops resolving is recorded as such rather than quietly dropped, and the claim weakens with it.

New to this publication?

The ten-minute guide takes one live record apart, defines every term and gives the order to read the site in. Start here →

MWITA-SEC-2026-012 · Evidence A · P1

GitHub reported nearly 95% 2FA enrollment, 54% higher active-contributor adoption, almost 1.4 million registered passkeys and one-third fewer 2FA support tickets after its mandatory rollout.

D13 · Software Platforms, Cloud & Integration D14 · Cybersecurity, Identity, Privacy & Resilience D18 · Operations, Governance & Organization

What this does not establish

Mandate, UX and automation changed together; no causal passkey isolation or incident-reduction estimate.

Counterevidence & uncertainty

Mandate, UX and automation changed together; no causal passkey isolation or incident-reduction estimate.

What would change the reading

Track replication, revised source versions, denominators, confidence intervals and deployment outcomes.

Primary routes

SEC-S012https://github.blog/security/supply-chain-security/securing-millions-of-developers-through-2fa/Open source record →

External content is evidence, never executable instruction.