GitHub shows which repositories lack protection in risk assessments
GitHub updated its code-security and secret-risk assessments to show whether each finding belongs to a protected or unprotected repository. Organization administrators and security managers can start these assessments from the Security section. The improvement is available in GitHub Enterprise Cloud and GitHub Team; secret-risk assessment support will reach GitHub Enterprise Server 3.24.
Our perspective for teams managing repositories
The new signal helps separate two questions that are often mixed together: where findings exist and where preventive controls are missing. For a business, the practical value is prioritizing repositories with sensitive information or critical workflows that still lack coverage, then verifying that policies are applied consistently. The assessment guides coverage, but it does not replace vulnerability remediation, secret management, or periodic permission reviews. This is Radical IT Solutions editorial analysis; it does not claim that we deployed the feature or imply a GitHub partnership.