<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Gitleaks on AJTech</title>
    <link>https://ajtech.nl/tags/gitleaks/</link>
    <description>Recent content in Gitleaks on AJTech</description>
    <generator>Hugo -- 0.152.2</generator>
    <language>en</language>
    <copyright>Copyright © 2023–2026, Arash Jalalat; all rights reserved</copyright>
    <lastBuildDate>Sun, 18 Jun 2023 11:32:41 +0000</lastBuildDate>
    <atom:link href="https://ajtech.nl/tags/gitleaks/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How to protect and discover secrets with Gitleaks?</title>
      <link>https://ajtech.nl/blog/how-to-protect-and-discover-secrets-with-gitleaks/</link>
      <pubDate>Sun, 18 Jun 2023 11:32:41 +0000</pubDate>
      <guid>https://ajtech.nl/blog/how-to-protect-and-discover-secrets-with-gitleaks/</guid>
      <description>&lt;p&gt;Detecting and discovering secrets or (hardcoded) passwords in a code repository should be an ongoing process for everyone involved in code development. But this process should not take all the time so that we have more time to contribute to good code quality. Fortunately, nowadays there are various tools that help us to automatically check that no sensitive data is present. Secrets, such as API keys and passwords are a well-known example of this. Continue reading on how you can easily do this in your local dev environment with Gitleaks.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
