Data and AI releases

78 this month · 172 companies

Security risk assessments include repository protection status

UpdateNot yet verified

The GitHub code security risk assessment and secret risk assessment now show whether findings are in protected or unprotected repositories, helping you identify where to extend your security coverage. Organization admins and security managers can start an assessment by going to Assessments under their organization’s Security tab.

SecurityObservability

Read on github.blog

Also shipped Nov 2, 2026GitHub in November 2026 →

More from GitHub Advanced SecurityEvery GitHub Advanced Security release →

Public monitoring now available with data residency

Public monitoring for secret scanning is now in public preview for GitHub Enterprise Cloud with data residency. It attributes exposed credentials to enterprises using verified domain matching while keeping data within the designated geography.

Preview
Source ↗

Updates to GitHub secret scanning

This update covers improvements and bug fixes for GitHub secret scanning. Update to audit log events On November 12, 2026 , the business field in affected secret_scanning_alert.* and secret_scanning_push_protection.bypass audit log events will change from the enterprise display name to the enterprise slug .

Preview
Source ↗

Dependabot alerts REST API now includes dependency versions

You can now get the version of a vulnerable dependency directly from Dependabot alert responses in the REST API. Each alert’s dependency object includes a new version_requirement field with the version or version constraint that Dependabot last recorded for the alert.

Update
Source ↗

GitHub package firewall in public preview

An increasing number of malware attacks exploit systems at package installation time, harvesting credentials on CI/CD hosts or developer workstations without even running the package’s code. To stem this tide of attacks, GitHub is introducing a new package firewall capability.

Preview
Source ↗

CodeQL changes for macOS 27, Xcode 27, and Swift 6.4

Starting with macOS 27 and Xcode 27, Apple no longer includes Intel (x86_64) code in some of the system binaries and libraries that CodeQL relies on to trace builds. As a result, CodeQL can’t support traced scans on these versions or analyze Swift 6.4.

Update
Source ↗