Improvement

June 17, 20263 Minute Read

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.

Detectors added

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.

ProviderSecret type
Cloudsmithcloudsmith_api_key
Datadogdatadog_pat
Datadogdatadog_sat
Elasticelastic_stack_api_key
GitLabgitlab_ci_build_token
GitLabgitlab_deploy_token
GitLabgitlab_feature_flag_client_token
GitLabgitlab_feed_token_v2
GitLabgitlab_incoming_email_token
GitLabgitlab_kubernetes_agent_token
GitLabgitlab_oauth_app_secret
GitLabgitlab_pipeline_trigger_token
GitLabgitlab_runner_auth_token
GitLabgitlab_runner_registration_token
GitLabgitlab_scim_oauth_token
Merakimeraki_api_key
Slackslack_workflow_trigger_url
Supabasesupabase_oauth_access_token
Supabasesupabase_scoped_personal_access_token
VolcEnginevolcengine_ark_api_key

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.

Push protection defaults expanded

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.

ProviderSecret type
Cloudflarecloudflare_account_api_token
Cloudflarecloudflare_global_user_api_key
Cloudflarecloudflare_user_api_token
Cockroach Labsccdb_api_key
Flutterwaveflutterwave_test_api_secret_key
Hack Clubhackclub_ai_api_key
OpenRouteropenrouter_api_key
PostHogposthog_oauth_refresh_token
Supabasesupabase_personal_access_token

Patterns that are not yet enabled by default remain configurable in your push protection settings.

Validity checks added

These patterns now support validity checks, so alerts tell you whether a leaked credential is still active and help you prioritize remediation.

ProviderSecret type
Alibabaalibaba_cloud_access_key_id
Alibabaalibaba_cloud_access_key_secret
Azureazure_ai_services_key
Azureazure_anomaly_detector_ee_key
Azureazure_anomaly_detector_key
Azureazure_cognitive_services_key
Azureazure_content_moderator_key
Azureazure_cosmosdb_key_identifiable
Azureazure_custom_vision_prediction_key
Azureazure_custom_vision_training_key
Azureazure_event_hub_key_identifiable
Azureazure_function_key
Azureazure_relay_key_identifiable
Azureazure_service_bus_identifiable
Azureazure_storage_account_key
Azureazure_text_translation_key
Coveocoveo_access_token
Coveocoveo_api_key
Databricksdatabricks_access_token
Salesforcesalesforce_access_token
Shopifyshopify_access_token
Shopifyshopify_custom_app_access_token
Shopifyshopify_merchant_token
Shopifyshopify_private_app_password

Extended metadata support

These patterns now include extended metadata when detected, providing richer context about leaked secrets.

ProviderSecret type
Airtableairtable_api_key
Airtableairtable_personal_access_token
Grafanagrafana_cloud_api_token
npmnpm_access_token
xAIxai_api_key

Learn more

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.

Subscribe to our developer newsletter

Discover tips, technical guides, and best practices in our biweekly newsletter just for devs.

By submitting, I agree to let GitHub and its affiliates use my information for personalized communications, targeted advertising, and campaign effectiveness. See the GitHub Privacy Statement for more details.

Secret scanning updates – June 2026 - GitHub Changelog