
Today’s most common security vulnerabilities explained
We're taking a look at some of the most common security vulnerabilities and detailing how developers can best protect themselves.
GitHub Blog Search
We're taking a look at some of the most common security vulnerabilities and detailing how developers can best protect themselves.
GitHub will require all users who contribute code on GitHub.com to enable one or more forms of two-factor authentication (2FA) by the end of 2023.
Introducing CodeQL packs to help you codify and share your knowledge of vulnerabilities.
On April 12, GitHub Security began an investigation that uncovered evidence that an attacker abused stolen OAuth user tokens issued to two third-party OAuth integrators, Heroku and Travis-CI, to download data from dozens of organizations, including npm. Read on to learn more about the impact to GitHub, npm, and our users.
Upgrade your local installation of Git, especially if you are using Git for Windows, or you use Git on a multi-user machine.
Security Overview for organizations is generally available
Organizations with GitHub Advanced Security can now proactively protect against secret leaks with secret scanning’s new push protection feature.
If there's one habit that can make software more secure, it's probably input validation. Here's how to apply OWASP Proactive Control C5 (Validate All Inputs) to your code.
Secret scanning Advanced Security customers can now view alerts on their public repositories
Code scanning detects more security issues, supports new language versions
GitHub Actions workflows in the Security category will now appear among the workflow recommendations based on a repository's content.
A behind-the-scenes peek into the machine learning framework powering new code scanning security alerts.
Starting today, we are rolling out mandatory 2FA to all maintainers of top-100 npm packages by dependents.
We’re excited to announce the V4 release of the OpenSSF’s Scorecard project in partnership with Google.
My colleague Stormy Peters and I are proud to represent GitHub at the White House’s Open Source Software Security Summit.
The GitHub Security Lab’s CodeQL bounty program fuels GitHub Advanced Security with queries written by the open source community.
In this post, I’ll discuss how to apply OWASP Proactive Control C2: Leverage security frameworks and libraries.
Use GitHub’s security features to assess Apache Log4j exposure and, where possible, mitigate this vulnerability within your GitHub repositories.
Defining your security requirements is the most important proactive control you can implement for your project. Here's how.