Question about secrets inside git repositories and how to deal with them

This page summarizes the projects mentioned and recommended in the original post on /r/devops

Our great sponsors
  • WorkOS - The modern identity platform for B2B SaaS
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • SaaSHub - Software Alternatives and Reviews
  • sops

    Simple and flexible tool for managing secrets

  • A much, much better alternative is Mozilla SOPS. Just encrypt the YAML values but leave the keys readable (there's an option to encrypt also a whole text blob, but YAML is where it shines). Pluggable backend - you can use GPG, but also KMS or many others. Decrypt function native in Terragrunt, ArgoCD, Flux, Helm, and many others.

  • gitleaks

    Protect and discover secrets using Gitleaks 🔑

  • We use a self hosted Gitlab instance where we turned on the option to atleast detect .key files from commits. Another thing we do is we scan all our repositories using Gitleaks. It's fairly simple and works pretty well. Generates a text file report that will show you where a secret has been committed and by whom.

  • WorkOS

    The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

    WorkOS logo
NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts