An organization restricts forking of private repositories. What risk is this policy primarily intended to reduce?
Select an answer to reveal the explanation.
Short Explanation and Infographic
Fork restrictions keep private code from sprouting copies in personal accounts outside org policy. Not an LFS speed tweak or markdown issue.
Full explanation below image
Full Explanation
Forking private organization repositories into personal user namespaces can create durable copies that leave organization IP allow lists, SSO enforcement, and security scanning coverage depending on configuration. Restricting forks keeps sensitive code within governed boundaries. The policy is unrelated to LFS performance on runners, markdown rendering, or Packages retention. Administrators should pair fork restrictions with clear contribution workflows (feature branches, inner-source internal repos) so developers still collaborate without exporting intellectual property. Periodic access reviews remain necessary for outside collaborators and transferred repositories.