Skip to main content

Github–Secret scanning

One of the things you certainly want to avoid as a developer is accidently checking in secrets(passwords, api keys, ...) in your code repository. Such a credential leak can have severe consequences and is something you certainly want to avoid.

If you are using GitHub as your source repository and you have a public repository, I have some good news for you. Since December last year, Github made secret scanning available for free  for all public repositories.

It is not enabled out-of-the-box but easy to configure and get up and running for you repo. Let me show you...

Enable Secret scanning for your public Github repository.

  • Browse to your public repository in Github and click on the Security tab.

  • Click on Secret Scanning on the Security page.

  • Click on the link to the Repository settings to bring you to the correct setting on the Settings page.
  • At the bottom of the page, click on the Enable button in the Secret scanning section.

  • That’s it!

Now every time when you push a commit to this repository, Github will scan the content of those commits for secrets. If secret scanning detects a secret, GitHub generates an alert that is send to the repository administrators and organization owners..

You can also check if secrets are found in the following way:

  • Go back to the Security page and click on Secret Scanning on the left or bView Detected Secrets.

  • On the Secret Scanning page, you can see any secret that is detected.

More information: About secret scanning - GitHub Docs

Popular posts from this blog

DevToys–A swiss army knife for developers

As a developer there are a lot of small tasks you need to do as part of your coding, debugging and testing activities.  DevToys is an offline windows app that tries to help you with these tasks. Instead of using different websites you get a fully offline experience offering help for a large list of tasks. Many tools are available. Here is the current list: Converters JSON <> YAML Timestamp Number Base Cron Parser Encoders / Decoders HTML URL Base64 Text & Image GZip JWT Decoder Formatters JSON SQL XML Generators Hash (MD5, SHA1, SHA256, SHA512) UUID 1 and 4 Lorem Ipsum Checksum Text Escape / Unescape Inspector & Case Converter Regex Tester Text Comparer XML Validator Markdown Preview Graphic Color B

Help! I accidently enabled HSTS–on localhost

I ran into an issue after accidently enabling HSTS for a website on localhost. This was not an issue for the original website that was running in IIS and had a certificate configured. But when I tried to run an Angular app a little bit later on http://localhost:4200 the browser redirected me immediately to https://localhost . Whoops! That was not what I wanted in this case. To fix it, you need to go the network settings of your browser, there are available at: chrome://net-internals/#hsts edge://net-internals/#hsts brave://net-internals/#hsts Enter ‘localhost’ in the domain textbox under the Delete domain security policies section and hit Delete . That should do the trick…

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.