Data and AI releases

548 this month · 176 companies

Track organization code quality trends

Generally availableVerified

The organization-level Code Quality dashboard now includes a Trends tab that shows how code quality has changed across your repositories over time. Instead of a point-in-time snapshot, you can see whether open findings are trending up or down and which repositories are driving the change.

PricingBIObservabilityDeveloper tools

Read on github.blog

Also shipped Aug 19, 2026GitHub in August 2026 →

Data movement policies (General availability)

With this release, data movement policies are now generally available for Enterprise Edition (or higher). Data movement policies are part of Snowflake’s data exfiltration protection controls. These SQL-style conditional policies can help you limit, alert on, or block data movement operations based on specific movement types.

GA
Source ↗

Organization Features in Organization Command Center (Preview)

Organization Features is now in preview in Organization Command Center. From the organization account, a user with the GLOBALORGADMIN role can open Organization Hub » Command center , then the Organization Features tile, to see which organization-level capabilities are enabled. In preview, the main control is premium views for cross-account telemetry.

Preview
Source ↗

Organization Command Center 3rd party access configuration (Preview)

3rd party access configuration is now in preview in Organization Command Center. From the organization account, a user with the GLOBALORGADMIN role can open Organization Hub » Command center , then the 3rd party access configuration tile, to classify member accounts as internal or external, set the default tenant type for new accounts, and maintain allowed...

Preview
Source ↗

More from GitHub Advanced SecurityEvery GitHub Advanced Security release →

Track GitHub Code Quality enablement changes in the audit log

GitHub Code Quality now writes an audit log event whenever someone enables, disables, or changes its settings on a repository. Three new events give you that history: repo.code_quality_enabled records when someone turns on Code Quality for a repository. repo.code_quality_disabled records when someone turns it off.

Update
Source ↗

Credential revocation and deauthorization by token type

Building on our self-service credential revocation experiences for incident response, you can now take token-type and user-specific actions to deauthorize and revoke user credentials during a security incident. This gives you finer-grained control when responding to a compromise.

Update
Source ↗

Block users directly from security advisories

You can now block a user directly from a security advisory page in public repositories owned by either an organization or a personal account. This brings the streamlined moderation experience available for issues and pull requests to security advisories.

Update
Source ↗

License data quality improvements

GitHub now uses package registries like npmjs.org and PyPI to determine license information for software components in the dependency graph. This improves the accuracy and completeness of the licenses shown in dependency insights, software bills of materials (SBOMs), the open source license compliance feature in GitHub Advanced Security, and the dependency...

Update
Source ↗

Secret scanning coverage updates

This release expands secret scanning’s coverage with more secrets blocked by push protection, one new secret scanning partner, and richer metadata on alerts. Secret scanning partnership program Lovable Labs is now a GitHub secret scanning partner. Secret scanning now automatically detects the following new secret type in your repositories.

Update
Source ↗

Multiple trusted publishing configurations for npm

We’re continuing to make trusted publishing smoother for npm publishers, guided by maintainers feedback. Three updates to npm publishing are now generally available: Multiple trusted publishing configurations per package Staged packages can only be approved after malware scanning is complete Maintainers can see their staged history in the package versions...

GA
Source ↗

Customize code scanning default setup at scale

You can now apply your own configuration file to code scanning default setup, using the new github-codeql-config-file repository property. This gives you control over how CodeQL scans your code for security vulnerabilities, whether that’s on one repository or across your whole organization.

Update
Source ↗