<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
  <title>appsec.fyi — gitleaks</title>
  <link>https://appsec.fyi/tools.html#gitleaks</link>
  <description>Curated gitleaks resources from appsec.fyi</description>
  <language>en-us</language>
  <atom:link href="https://appsec.fyi/feeds/tool/gitleaks.xml" rel="self" type="application/rss+xml"/>
  <lastBuildDate>Sun, 07 Jun 2026 04:05:35 +0000</lastBuildDate>
  <managingEditor>carl@chs.us (Carl Sampson)</managingEditor>
  <item>
    <title>GitHub Secret Scanning 2026: New Patterns, Push Protection</title>
    <link>https://www.buildmvpfast.com/blog/github-secret-scanning-pattern-updates-devops-2026</link>
    <guid isPermaLink="true">https://www.buildmvpfast.com/blog/github-secret-scanning-pattern-updates-devops-2026</guid>
    <description>Library for GitHub Secret Protection offers enhanced detection of leaked secrets with 28 new patterns across 15 providers, expanded push protection for 39 token types, and AI-powered generic password detection via Copilot. Available to GitHub Team plan customers at $19 per month per active committer, it includes validity checks and improved API visibility. This solution aims to prevent credential-related breaches, which cost an average of $4.88 million, by blocking pushes of sensitive information like Supabase service keys and Vercel API tokens before they reach repositories.</description>
    <category domain="tool">gitleaks</category>
    <category domain="difficulty">beginner</category>
    <pubDate>Wed, 22 Apr 2026 12:52:56 +0000</pubDate>
  </item>
  <item>
    <title>Pre-Commit Hooks for Secret Detection: Setup in 10 Minutes</title>
    <link>https://rafter.so/blog/secrets/pre-commit-hooks-secret-detection</link>
    <guid isPermaLink="true">https://rafter.so/blog/secrets/pre-commit-hooks-secret-detection</guid>
    <description>Library for implementing pre-commit hooks to prevent secrets from entering Git history. It details the setup process for tools like gitleaks, detect-secrets, and TruffleHog, offering solutions for immediate detection and blocking of credential leaks. The library emphasizes catching secrets at the cheapest point in the lifecycle, preventing the need for costly history rewrites and incident response by integrating these tools seamlessly into the Git commit workflow.</description>
    <category domain="tool">gitleaks</category>
    <category domain="difficulty">intermediate</category>
    <pubDate>Sun, 19 Apr 2026 02:37:09 +0000</pubDate>
  </item>
  <item>
    <title>Understanding Your Organization&#x27;s Exposure to Secret Leaks — GitHub</title>
    <link>https://resources.github.com/enterprise/understanding-secret-leak-exposure/</link>
    <guid isPermaLink="true">https://resources.github.com/enterprise/understanding-secret-leak-exposure/</guid>
    <description>Library for assessing an organization&#x27;s exposure to secret leaks, highlighting that over 39 million secrets were detected on GitHub in 2024 alone. This resource details how secrets like API keys and passwords are leaked through repository commits or misconfigurations, referencing the $4.88 million average cost of credential compromise breaches and the 2022 LastPass breach. It provides methods for quantifying risk, including inventory audits and benchmarking against OWASP ASVS and NIST guidelines, and mentions GitHub&#x27;s secret risk assessment tool for enterprise customers.</description>
    <category domain="tool">gitleaks</category>
    <category domain="difficulty">beginner</category>
    <pubDate>Sun, 19 Apr 2026 02:22:23 +0000</pubDate>
  </item>
  <item>
    <title>Exposed Developer Secrets Surge: AI Drives 34% Increase in 2025</title>
    <link>https://securityledger.com/2026/03/exposed-developer-secrets-surge-ai-drives-34-increase-in-2025/</link>
    <guid isPermaLink="true">https://securityledger.com/2026/03/exposed-developer-secrets-surge-ai-drives-34-increase-in-2025/</guid>
    <description>Report detailing a 34% surge in exposed developer secrets during 2025, fueled by AI-assisted coding and expanded use of tools like Claude Code. GitGuardian&#x27;s analysis highlights significant increases in leaked AI service credentials, including DeepSeek API keys, and identifies internal repositories as a six-fold greater risk. The report also notes that 28% of exposures occur outside code in platforms like Slack and Jira, with 64% of discovered secrets remaining unrevoked.</description>
    <category domain="tool">gitleaks</category>
    <category domain="difficulty">news</category>
    <pubDate>Sun, 19 Apr 2026 02:22:23 +0000</pubDate>
  </item>
  <item>
    <title>GitHub Found 39M Secret Leaks in 2024 — The GitHub Blog</title>
    <link>https://github.blog/security/application-security/next-evolution-github-advanced-security/</link>
    <guid isPermaLink="true">https://github.blog/security/application-security/next-evolution-github-advanced-security/</guid>
    <description>Library for GitHub Advanced Security, featuring Secret Protection and Code Security, addresses the pervasive issue of exposed secrets, which led to 39 million leaks on GitHub in 2024. It emphasizes built-in push protection for public repositories and introduces affordable standalone products and a free point-in-time scan for organizations to identify and manage secret exposures effectively, partnering with vendors like AWS and Google Cloud Platform to enhance detection accuracy.</description>
    <category domain="tool">gitleaks</category>
    <category domain="difficulty">news</category>
    <pubDate>Sun, 19 Apr 2026 02:22:22 +0000</pubDate>
  </item>
  <item>
    <title>Secret Scanning in CI Pipelines using Gitleaks</title>
    <link>https://dev.to/sirlawdin/secret-scanning-in-ci-pipelines-using-gitleaks-and-pre-commit-hook-1e3f</link>
    <guid isPermaLink="true">https://dev.to/sirlawdin/secret-scanning-in-ci-pipelines-using-gitleaks-and-pre-commit-hook-1e3f</guid>
    <description>Tool for integrating Gitleaks into GitLab CI pipelines for secret scanning. It details setting up a CI job to run Gitleaks against the OWASP Juice Shop application, demonstrating how to detect and prevent secret leaks like API keys, usernames, and secret keys from being committed. The entry also mentions the use of Git hooks as a pre-commit security measure.</description>
    <category domain="tool">gitleaks</category>
    <category domain="difficulty">intermediate</category>
    <pubDate>Sat, 11 Apr 2026 16:48:23 +0000</pubDate>
  </item>
  <item>
    <title>Add a Local Gitleaks Pre-Commit Hook</title>
    <link>https://www.d4b.dev/blog/2026-02-01-gitleaks-pre-commit-hook/</link>
    <guid isPermaLink="true">https://www.d4b.dev/blog/2026-02-01-gitleaks-pre-commit-hook/</guid>
    <description>Library for a local Gitleaks pre-commit hook that prevents accidental secrets from entering Git history. It utilizes files within `.git/` for a fast, easily removable safety net, supporting custom configurations via `.gitleaks.toml` and optional team-wide enforcement with Lefthook or GitHub Actions.</description>
    <category domain="tool">gitleaks</category>
    <category domain="difficulty">intermediate</category>
    <pubDate>Sat, 11 Apr 2026 16:48:22 +0000</pubDate>
  </item>
  <item>
    <title>Top 8 Git Secrets Scanners in 2026</title>
    <link>https://www.jit.io/resources/appsec-tools/git-secrets-scanners-key-features-and-top-tools-</link>
    <guid isPermaLink="true">https://www.jit.io/resources/appsec-tools/git-secrets-scanners-key-features-and-top-tools-</guid>
    <description>Library of eight Git secrets scanners, including Jit, Gitleaks, GitGuardian, HawkScan, AWS Git Secrets Scanner, Spectral, Trufflehog, and GitHub Secret Scanning, designed to detect and neutralize exposed sensitive data like API keys and credentials within code repositories. These tools employ pattern-based and ML detection, custom rules, historical and pre-commit scanning, CI/CD integration, and remediation guidance to prevent data breaches and unauthorized access by shifting security left in the development lifecycle.</description>
    <category domain="tool">gitleaks</category>
    <category domain="difficulty">beginner</category>
    <pubDate>Fri, 10 Apr 2026 01:52:08 +0000</pubDate>
  </item>
  <item>
    <title>TruffleHog vs. Gitleaks: A Detailed Comparison</title>
    <link>https://www.jit.io/resources/appsec-tools/trufflehog-vs-gitleaks-a-detailed-comparison-of-secret-scanning-tools</link>
    <guid isPermaLink="true">https://www.jit.io/resources/appsec-tools/trufflehog-vs-gitleaks-a-detailed-comparison-of-secret-scanning-tools</guid>
    <description>Library comparing TruffleHog and Gitleaks, popular secret scanning tools that identify hardcoded secrets like API keys and tokens within codebases and other environments. TruffleHog offers extensive scanning across S3 buckets and Docker images with advanced verification, while Gitleaks provides a lightweight, fast, and user-friendly experience focused on code repositories, excelling in CI environments. Both integrate into the SDLC to proactively detect and rectify leaked credentials, preventing unauthorized access and security breaches.</description>
    <category domain="tool">gitleaks</category>
    <category domain="difficulty">intermediate</category>
    <pubDate>Fri, 03 Apr 2026 15:50:55 +0000</pubDate>
  </item>
  <item>
    <title>Gitleaks - Find Secrets with Gitleaks</title>
    <link>https://github.com/gitleaks/gitleaks</link>
    <guid isPermaLink="true">https://github.com/gitleaks/gitleaks</guid>
    <description>Tool for detecting secrets like passwords, API keys, and tokens in git repos, files, and via stdin. Gitleaks supports scanning via `git`, `dir`, and `stdin` commands, and can be integrated as a pre-commit hook or GitHub action. It allows for baseline scanning to ignore old findings and custom rule configuration.</description>
    <category domain="tool">gitleaks</category>
    <category domain="difficulty">beginner</category>
    <pubDate>Fri, 03 Apr 2026 15:50:51 +0000</pubDate>
  </item>
</channel>
</rss>