On October 20, 2026, GitHub opened a public preview of a firewall that sits between Actions runners, coding agents and the npm registry, inspecting metadata requests and package downloads alike. It blocks malware at install time, where scanners show up too late: turn it on if your CI installs third-party code.
On October 16, 2026, GitHub made open source license compliance generally available: a ruleset requires compliant results before merge and blocks any pull request that adds a dependency under an unacceptable license. For enterprises that already govern their dependencies, this is the shift from after-the-fact audit to a policy enforced in CI.
On 14 October 2026, GitHub published the engineering story behind its reworked stargazers endpoint, which took 2,511 requests to rebuild react/react’s curve and was being harvested for spam. The lesson transfers to any API: a smaller response doesn’t make a cheaper query — the order of work in the database does.
On October 8, 2026, Apiiro revealed that the FakeGit campaign has re-activated 17,610 fake GitHub repositories distributing the SmartLoader loader, several hundred of them impersonating AI skills and MCP servers. Before installing a repo from GitHub, check the account owner and prefer official registries.
GitHub rolled out a fine-tuned secret-detection model that reads surrounding code to flag likely credentials, including passwords with no recognizable token format — exactly what regex-based secret scanning lets through. If you already pay for GHAS or GHSP, the switch is free and automatic; the AI push-protection and review checks will consume AI Credits you need to budget for.
GitHub announced general availability for stacked pull requests, which split a large change into small, independently reviewed pull requests that merge together at the end. If your branches keep blocking each other, GitHub’s numbers — 9% more merged code and 5% faster time-to-merge — justify adopting them now.
The GitHub Security Lab Taskflow Agent found 24 real Android vulnerabilities, from location tracking in OsmAnd to a full Wikipedia account takeover. AI can now find high-impact logic bugs, but still struggles to rank their severity.
On September 18, 2026, CrowdSec revealed that an attacker copied about 170 private GitHub repositories in May using the account of a former employee whose access had never been revoked. The initial compromise came from TanStack’s malicious npm packages, which also hit Mistral AI and OpenAI.
On August 20, 2026, GitHub’s CTO published the post-mortem for the August 17 outage: 7 hours and 47 minutes of downtime caused by an infrastructure component that failed to scale with load, as monthly commits climbed from 1.4 to 2.9 billion since April. The lesson for SRE teams fits in two words: retry budgets.
From TanStack to Trellix via GitHub Megalodon, the five biggest supply chain attacks of 2026 prove your attack surface extends to every npm install. Third-party risk management must become continuous — the annual questionnaire is dead.
On March 17, 2026, GitHub Enterprise Server 3.20 went GA with two structural security gates: releases are now immutable by default, and secret scanning gains enterprise-wide governance controls. Against a backdrop of escalating supply chain attacks, this release turns the forge into a fortress.
