Published on

Github automated security fixes (beta)

Last Modified on
Last modified on
Github automated security fixes (beta)
Photo by Daniel Plan on Unsplash

I thought it was so cool when I stumbled across Snyk, a tool which "enables developers to automatically find and fix open source vulnerabilities". However, given that we encounter myriad vulnerabilities we have to fix each day, the monthly free tier of this tool could potentially run out very quickly. And the next tier is horribly expensive, especially for individual developers. $599/month! Forget about it! I took my chances with the free tier.

Well, guess what? Now Github has introduced something called "Automated security fixes".

How does Github's automated security fixes (in beta) work?

First of all, public repositories receive security alerts by default. In order for private repositories to receive security alerts, the owner or admin of the repository must manually enable the dependency graph and security alerts in the repository.

The languages that the dependency graph supports are Java, JavaScript, .NET, Python, and Ruby. To learn more, please visit the Github article entitled Listing the packages that a repository depends on.

Github does state,

GitHub's security features, such as security alerts, do not claim to catch all vulnerabilities. Though we are always trying to update our vulnerability database and alert you with our most up-to-date information, we will not be able to catch everything or alert you to known vulnerabilities within a guaranteed time frame. These features are not substitutes for human review of each dependency for potential vulnerabilities or any other issues, and we recommend consulting with a security service or conducting a thorough vulnerability review when necessary.

Having yet another source to fix the vulnerabilities in your code is a good thing. The more sources you can use the better. Those of us that use Node.js and NPM (Node Package Manager) know that we also have npm audit to check and fix known vulnerabilities in our code, and Snyk has been doing this kind of thing for a while, so they are another good source to glean from. I am sure there are many other similar tools out there, but I mention these because I know about them and use them. If you know of any others and would like to share them with me, feel free to ping me on Twitter @letsbsocial1. That's letsbsocial1. And then there are always developers or services specializing in security that can conduct thorough vulnerability code reviews as well.

I will be embedding this episode of Plugging in The Holes along with a transcript in the form of a post on for your hearing and reading pleasure. I will be including the related resource links mentioned in the podcast of course. Always do. Bye for now!