趋势解读：Secret scanning updates – June 2026，提升开发者接入体验

Since our last pattern update , we’ve expanded secret scanning’s detection coverage with new partners, more patterns blocked by push protection by default, additional validity checks, and richer metadata for leaked secrets. Secret scanning now automatically detects the following new secret types in your repositories. This release adds two new partners (Cloudsmith and Meraki), significantly expands GitLab token coverage, and adds detectors for Elastic, Slack, Supabase, DataDog, and VolcEngine. Partner secrets are automatically reported to the secret issuer when found in public repositories through the secret scanning partnership program . User secrets generate secret scanning alerts when found in public or private repositories. The following detectors are now included in push protection by default. Repositories with secret scanning enabled, including free public repositories, will have commits containing these secrets automatically blocked. Patterns that are not yet enabled by default remain configurable in your push protection settings. These patterns now support validity checks, so alerts tell you whether a leaked credential is still active and help you prioritize remediation. These patterns now include extended metadata when detected, providing richer context about leaked secrets. Learn more about secret scanning and see the full list of supported secrets in our documentation. Let us know what you think in the community discussion .