GitHub Security Advisories, which launched in beta earlier this year, are now generally available. And we’ve made some exciting changes based on feedback from maintainers. First, we’ve added the ability to automatically request a CVE identifier for any Security Advisory. We’ve also refined the process of creating and publishing a Security Advisory, so that it’s clearer when the advisory will become public and easier to provide the information needed to power automatic dependency updates via the GitHub Advisory Database.
See what launched at GitHub Universe
Missed the main event? Learn more about everything that launched at GitHub Universe, from GitHub for mobile and a redesigned notifications experience to the GitHub Archive Program.Read the day one keynote recap
Secure the world's code, together
On day two of GitHub Universe, we announced GitHub Security Lab, bringing together security researchers, maintainers, and companies across the industry to secure open source.Read the day two keynote recap