You can now use the REST API to add collaborators to your draft security advisory.
Learn more about the repository security advisories REST API
Select a query suite when enabling code scanning with default setup at the organization level
You now have the option to select either the "Extended" or "Default" query suite when setting up code scanning with default setup for eligible repositories within your organization.
Code scanning's default query suite has been carefully designed to ensure that it looks for the security issues most relevant to developers, whilst also minimizing the occurrence of false positive results. However, if you and your developers are interested in seeing a wider range of alerts, you can enable the extended query suite. This suite includes everything from the default query suite, plus additional queries with slightly lower precision and severity.
Choose a query suite
The query suite selection can be made whenever you enable code scanning with default setup:
- When using "Enable all" on the organization settings page.
- When enabling a single or multiple repositories on the security coverage page.
- When enabling on a repository's settings page.
- When using the "Enable or disable a security feature for an organization" endpoint.
Previously, our system would automatically choose the default query suite when you enabled code scanning with default setup. Now, you can choose either the extended or default query suite.
Recommend a query suite
Additionally, you can specify either the extended or default query suite as the preferred choice for your organization. This preference determines which query suite is "recommended" when a user is enabling code scanning setup with default setup.
These improvements have shipped to GitHub.com and will be available in GitHub Enterprise Server 3.11.
Learn more about configuring default setup for code scanning and send us your feedback
Learn more about GitHub Advanced Security
GitHub secret scanning protects users by searching repositories for known types of secrets. By identifying and flagging these secrets, our scans help prevent data leaks and fraud.
We have partnered with Defined to scan for their tokens and help secure our mutual users on public repositories. Defined tokens allow users to access various administrative functions of their managed mesh networking offerings. GitHub will forward access tokens found in public repositories to Defined, which will then email the user. You can read more information about Defined's tokens here.
All users can scan for and block Defined's tokens from entering their public repositories for free with push protection. GitHub Advanced Security customers can also scan for and block Defined tokens in their private repositories.