# GitHub Tames Secret Scans with LLMs
_GitHub is using LLMs to slash false positives in secret scanning, boosting alert accuracy and developer efficiency by over 75%._
**Published:** 2026-06-11
**Source:** https://www.startuphub.ai/ai-news/technology/2026/github-tames-secret-scans-with-llms
---
GitHub is leveraging Large Language Models (LLMs) to make its [secret scanning](/ai-news/insights/2026/ai-security-tools-vibe-coded-apps-2026) more trustworthy. The move aims to cut down on the 'noise' of false positives that plague automated security tools, allowing developers to focus on genuine threats.

Secret Scanning NoiseDriver

too many alerts that look like secrets but aren'tFrom the article 3 mentionsGitHub is leveraging Large Language Models (LLMs) to make its secret scanning more trustworthy.GitHub Secret ScanningContextexisting pipeline combining pattern and AI detectionFrom the article 3 mentionsThis enhancement builds upon GitHub's existing secret scanning pipeline, which combines pattern-based and AI-based detection.Microsoft Security & AICoreFrom the article 4 mentionsTo combat this, GitHub partnered with Microsoft Security & AI to integrate more contextual reasoning into the verification process.leads toDeveloper FrictionDriverwasting time triaging false positive security alertsFrom the article 4 mentionsThis friction erodes confidence in automated security systems.solved byLLM Contextual AnalysisCoreexamining how detected values are used within the codeFrom the articleThe new approach focuses on the verification step, adding LLM-based contextual analysis.enablesBoosted Alert AccuracyEffectslashing false positives in secret scanningresults inDeveloper EfficiencyOutcomeover 75% improvement in focusing on genuine threatsFrom the article 4 mentionsThis focused context, rather than more raw code, is crucial for accuracy and efficiency.
The core issue: too many alerts that look like secrets but aren't, forcing developers to waste time triaging. This friction erodes confidence in automated security systems. To combat this, GitHub partnered with Microsoft Security & AI to integrate more contextual reasoning into the verification process.

## Context is Key

This enhancement builds upon GitHub's existing secret scanning pipeline, which combines pattern-based and AI-based detection. The new approach focuses on the verification step, adding LLM-based contextual analysis. Instead of just matching patterns, the system now examines how a detected value is used within the code.

The goal is to make alerts more actionable. By understanding the usage context, for instance, if a value is assigned to a variable and then passed into an API request or SDK call, the LLM can better determine if it's a real secret or just a placeholder, test data, or an opaque string. This focused context, rather than more raw code, is crucial for accuracy and efficiency.

This strategy yielded impressive results. In evaluations against hundreds of customer-confirmed false positives, the new method achieved a 75.76% reduction, surpassing their 65% target. This translates directly to fewer irrelevant alerts and faster remediation of actual security incidents, a significant win for developer productivity.

The work continues, with GitHub exploring larger datasets and refining context extraction. The ultimate aim is clearer signals, fewer distractions, and quicker action on genuine risks, making [GitHub's free code scan](/ai-news/technology/2026/github-s-free-code-scan) and other offerings more effective. This advancement is part of a broader trend in [improving GitHub secret scanning](/ai-news/cybersecurity/2026/github-fake-stars-reputation-as-a-service) with AI, echoing efforts like [Uber's AI data guards](/ai-news/tech/2026/uber-s-ai-guards-data-at-scale) in their pursuit of reducing false positives at scale.
---
Original analysis from [startuphub.ai](https://www.startuphub.ai), the #1 AI startup directory.