An enterprise policy prevents members from changing repository visibility. What risk does this primarily reduce?
Select an answer to reveal the explanation.
Short Explanation and Infographic
The classic oops: someone flips a private repo to public and secrets or IP hit the open internet. Enterprise/org policies that lock visibility changes stop that class of accidents. It is not about SSH cloning or rewriting author fields.
Full explanation below image
Full Explanation
The correct answer is reducing accidental public exposure of private repositories. Visibility change restrictions keep private/internal code from becoming public without authorized owners, which is a common source of intellectual-property and secret leaks. Option B is unrelated to visibility policy. Option C is unrelated to authorship metadata. Option D is unrelated to Actions artifact retention. Combine with secret scanning, push protection, and external collaborator controls for layered data-leak prevention across the enterprise.