Viral

@

viral_codes

Consider using a tool like GitGuardian or Snyk to monitor your repositories for exposed secrets and automatically flag them.

Julio Andrés Dev

@

julioandresdev

I mistakenly pushed an OpenAI API key in a commented code to github. Less than two minutes after that I received this email notifying me of the mistake. Well done Github and GitGuardian. I'm curious of what are the rules to identify a leaked api key. https://t.co/XgSkmkgWFm

San.D

@

sankaram_d

@heyOnuoha In worst case Remember GitGuardian is there for you.

Nozthun

@

nozthun

@dan_abramov @GitGuardian They saved my ass once, thanks for the spam

Jack Bridger

@

jacksbridger

Tried out @GitGuardian today & it worked really well. Wanted to convert a private repo into a public repo but was worried I left some keys in a historic commit. Anxiety gone.

Calvin Wilkinson (Kinson Digital)

@

KDCoder

So secrets/tokens make it into repos all the time and it is unfortunate. But you can make it really easy to manage and get notified of when this happens. I use GitGuardian & its fantastic. Super easy to setup!! NO excuse not to do this. https://t.co/vv2zUHPowT

San.D

@

sankaram_d

GitGuardian is the saviour for me, whenever I accidentally put private info like api keys, or other credentials, immediately receive alerts. Actually it's very cool.

Ben Gale

@

bengale

@_ediri @PulumiCorp @github Really cool that's happening out of the box. I've been really impressed with gitguardian for this sort of stuff recently, lets me know in PRs if I've messed up with credentials. Also seems to check they're actually valid credentials too which is awesome.

Kayode (📽️, 🌿)

@

zt4ff

So how can you prevent this? - make use of environment variables, for instance, .env files - Integrate code scanning tools like @GitGuardian in your workflow to detect and report secrets like API keys, passwords, etc

Alexandre Couëdelo

@

AlexCouedelo

A nice illustration of @GitGuardian on typical attack scenarios for a software supply chain https://t.co/aq2kDf6PjY

Jan Arno H. aus #Wallhausen - #ShadowBanned

@

kwikgo

#UHOH My 1997 #SMTP #Password #LEAKED Thanks for informing me, @GitGuardian @guardianfilm @guardiantech In exchange, I share this link: https://t.co/XZakKoRHts #PEACE @BBCWorld Nice work #OSS #OpenSource #QA #WebDevelopment #Monitoring #Website #CICD #Automation #Testing ☮️ https://t.co/zKyUT7CzW0

Forrest Morrison

@

4restMorrison

Note to self: If you have already committed a file to #github, just adding it to your .gitignore will not remove it from Github. You have to go on Github and delete it yourself. Thank you, @GitGuardian! You are a life saver! #webdevelopment #webdev

Graasp

@

graasp

Thank you @GitGuardian for building such a great product! It's an indispensable tool for our ecosystem of open source repositories. 🙌 https://t.co/cdr4PQ7LS2

Praveen

@

aspraveen

I made a private repo public today on #github and thanks to @GitGuardian for notifying about the google Oauth2 key leak in an old commit. 👍

Aaron Meese

@

ajmeese7

Shout-out to the amazing team at @GitGuardian for this super cool shirt, really enjoyed meeting you guys at #InfosecWorld! https://t.co/IEsoLyXM82

Kyle Mistele 🏴‍☠️🔺 // cryptokyle.eth

@

0xblacklight

If @GitGuardian isn't a part of all of your GitHub actions and CI/CD pipelines, you're not doing it right :P https://t.co/ZXNwD1PHza

Bashir Abdul 🇳🇬

@

Nerdy_Bee

I didn't know about GitGuardian until today. I got say it's very cool alerting me of an exposed secret_key in my Django app repo.

Charly@CSDev

@

CSDevAr

@GitGuardian @schmelto2 @pradumna_saraf Will do, that first impression was everlasting, great product!

Gokul

@

GokulZuzumaki

Tried out @GitGuardian and it works like a charm I intentionally made a commit while exposing my Secret API key and GitGuardian warned me about the security issues, such a handy tool!!!

Brian Bud 🇨🇦

@

brianbud_

1st day using MongoDB & when I pushed to Github, I got my email from GitGuardian for a security threat that my connectionString password was public😨. For now I figured out how to revert a pushed commit in git using "git reset Head~1" to unstage & "git push -f origin main".

jeppeReinhold 🇩🇰

@

DrReinhold

. @GitGuardian just warned me the moment I made the mistake of committing a secret API key to a GitHub repo. That was pretty cool. I've never heard of them before, I guess they just scan all public GitHub repos for mistakes..

M Shoaib | JS | Blockchain

@

shoaib_shebi40

@kunalstwt @KubeScape There is also a cool tool, gitguardian When i scanned in past, gave me this 😅 @GitGuardian https://t.co/XrEmbCmCV1

Mathias

@

matthegap

@GitGuardian Thanks for the great work. Also, the guide you are sending out is pretty good.

Mathias

@

matthegap

I pushed a repo to GitHub (for a course), and within an hour of making it public, I received an e-mail from @GitGuardian warning me about the private key in its history. Quite amazing.

Harold Oliver 🛡️

@

Colonelxy

@singhk_uttam @robin_rrtx @developer_dao . Env files are not that secure. I get notified immediately I push if there's any credentials. Gitguardian helps a lot there.

Matthias Fischer

@

mfi82

Quick shoutout to @GitGuardian and @github for their efforts to find leaked secrets in #git repos. A near miss (test credentials) in my case, but I really appreciate the feature itself! Very thoughtful to enable this for all repos by default. #infosec