About validity checks
You can enable validity checks for secrets identified as service provider tokens for your repository. Once enabled, GitHub will periodically check the validity of a detected credential by sending the secret directly to the provider, as part of GitHub's secret scanning partnership program. 파트너 프로그램에 대해 알아보려면 Secret scanning partner program을(를) 참조하세요.
GitHub displays the validation status of the secret in the alert view, so you can see if the secret is active, inactive, or if the validation status is unknown. You can optionally perform an "on-demand" validity check for the secret in the alert view.
You can additionally choose to enable validity checks for partner patterns. Once enabled, GitHub will periodically check the validity of a detected credential by sending the secret directly to the provider, as part of GitHub's formal secret scanning partnership program. GitHub typically makes GET requests to check the validity of the credential, picks the least intrusive endpoints, and selects endpoints that don't return any personal information.
GitHub displays the validation status of the secret in the alert view.
You can filter by validation status on the alerts page, to help you prioritize which alerts you need to take action on.
참고 항목
GitHub typically makes GET requests to check the validity of the credential, picks the least intrusive endpoints, and selects endpoints that don't return any personal information.
For more information on using validity checks, see Evaluating alerts from secret scanning.
Enabling validity checks
참고 항목
You can also use the REST API to enable validity checks for partner patterns for your repository. For more information, see 리포지토리에 대한 REST API 엔드포인트.
-
GitHub에서 리포지토리의 기본 페이지로 이동합니다.
-
리포지토리 이름 아래에서 Settings를 클릭합니다. "설정" 탭이 표시되지 않으면 드롭다운 메뉴를 선택한 다음 설정을 클릭합니다.

-
사이드바의 "Security" 섹션에서 Advanced Security 를 클릭합니다.
-
"Secret Protection"에서 "유효성 검사"의 오른쪽에 있는 사용을 클릭합니다.
-
Scroll to the bottom of the page and click Save changes.
Alternatively, organization owners and enterprise administrators can enable the feature for all repositories in the organization or enterprise. For more information on enabling at the organization-level, see 사용자 지정 보안 구성 만들기. For more information on enabling at the enterprise-level, see 엔터프라이즈를 위한 사용자 지정 보안 구성 만들기.