# Enabling extended metadata checks for your repository
Learn how to enable extended metadata checks for detected secrets so alerts detected by secret scanning include additional information that help you assess and remediate leaks faster.
> \[!NOTE] Extended metadata checks for tokens is in public preview and subject to change.
This article shows how you can enable extended metadata checks for individual repositories through repository settings. Alternatively, you can enable them at scale using **security configurations** at the organization or enterprise level. See [Creating a custom security configuration](/en/code-security/how-tos/secure-at-scale/configure-organization-security/establish-complete-coverage/create-custom-configuration) or [Creating a custom security configuration for your enterprise](/en/code-security/how-tos/secure-at-scale/configure-enterprise-security/establish-complete-coverage/create-custom-configuration).
## Prerequisites
Before enabling metadata checks, you need to ensure that validity checks are enabled for the repository. See [Enabling validity checks for your repository](/en/code-security/how-tos/secure-your-secrets/customize-leak-detection/enable-validity-checks#enabling-validity-checks).
## Enabling extended metadata checks
1. On GitHub, navigate to the main page of the repository.
2. Under your repository name, click ** Settings**. If you cannot see the "Settings" tab, select the **** dropdown menu, then click **Settings**.
3. In the "Security and quality" section of the sidebar, click ** Advanced Security**.
4. Under "Secret Protection" and "Validity checks", to the right of "Extended metadata", click **Enable**.
## Further reading
* [Manage secret scanning alerts](/en/code-security/how-tos/manage-security-alerts/manage-secret-scanning-alerts)