When you post content to a public GitHub repository, you give GitHub and other users a license to view, display, fork, and reproduce that content through the GitHub platform.
This analysis describes what GitHub's agreement states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability and practical outcomes may vary by jurisdiction, enforcement context, and individual circumstances. Read our methodology
The provision authorizes GitHub to display and reproduce your public repository content and grants other users a license to fork and view it, which is central to how GitHub's collaborative platform functions but also means public content can be used by others within the service.
Interpretive note: The exact scope of the sublicense granted to other users and whether it survives content deletion is not fully specified in the available document text.
GitHub's updated Terms of Service now include an explicit section governing AI features, including Copilot. The new section establishes specific contractual terms for how user data may be collected, used, and retained for developing and improving AI and machine learning models, and identifies what controls are available to users. The practical effect is that AI-related data practices are now consolidated under dedicated contractual language rather than dispersed across general service terms.
View change record →GitHub's Terms of Service update on April 19, 2026 involved substantial revisions across 54 sentences, with 40 sentences removed and 4 added. The extent of change suggests modifications to core service provisions; however, without access to the specific language that was modified, removed, or added, the precise operational implications for users cannot be determined. Users should review the updated Terms directly to understand how the changes affect their usage rights, account obligations, or dispute resolution procedures.
View change record →Content posted to public repositories is licensed to GitHub and to all other GitHub users for display, forking, and reproduction on the platform. Developers hosting proprietary or sensitive code should ensure repositories are set to private to limit the scope of this license.
How other platforms handle this
By submitting, sharing, or otherwise making User-Generated Content available through any of the Licensed Products, including by submitting User-Generated Content using UEFN, you grant Epic a royalty-free, perpetual, irrevocable, non-exclusive, sublicensable, worldwide license to use, reproduce, modi...
As a Subscriber you may submit or transmit (collectively, "post") Content on or through Steam, including but not limited to, written works, images, photos, messages, comments, game data, gameplay recordings, and profile data ('User Generated Content' or 'UGC'). By posting any UGC on Steam, you expre...
"Content" means anything you or your Customers create or make available through the Service in connection with your Account, including your intellectual property (e.g. trademarks, trade names, service marks, and copyrighted works); the products or services you offer (e.g., courses, coaching, members...
Monitoring
GitHub has changed this document before.
Receive same-day alerts, structured change summaries, and monitoring for up to 25 platforms.
"By setting your pages and repositories to be viewed publicly, you agree to allow others to view and fork your repositories within the GitHub Service. By setting your repositories to be viewed publicly, you agree to allow GitHub to display your User Content in ways to enable users to view, fork, and download your repositories. If you set your pages and repositories to be viewed publicly, you grant each User of GitHub a nonexclusive, worldwide license to use, display, and perform your Content through the GitHub Service and to reproduce your Content solely on GitHub as permitted through GitHub's functionality. You may grant further rights if you adopt a license.— Excerpt from GitHub's GitHub Terms of Service
REGULATORY LANDSCAPE: This provision engages copyright law under Title 17 of the U.S. Code and, for EU users, the EU Copyright Directive. The license grant's scope, including sublicensing rights to other users, may require evaluation under GDPR where content includes personal data of third parties. The FTC Act is relevant if the license scope is not clearly disclosed to users at the point of content submission. GOVERNANCE EXPOSURE: Medium. The license is limited to the GitHub Service and does not assert rights for GitHub to commercialize user content outside the platform. However, the sublicensing right to other users and the reproduction right create operational exposure for developers who inadvertently publish proprietary code to public repositories. The provision does not specify a termination mechanism for the license once content is deleted, which may require further evaluation. JURISDICTION FLAGS: EU/EEA users should consider whether public repository content includes personal data subject to GDPR, as the license grant would facilitate broad distribution of that data within the service. California residents retain CCPA rights over personal information but this provision addresses content copyright rather than personal data directly. CONTRACT AND VENDOR IMPLICATIONS: Enterprise procurement teams should assess whether employee use of GitHub could result in proprietary code being committed to public repositories under this license. Internal GitHub usage policies and repository visibility governance are relevant vendor assessment items. The provision does not assert an indemnification shift but the license grant could affect intellectual property ownership claims in vendor contracts. COMPLIANCE CONSIDERATIONS: Organizations should implement internal controls requiring code review before repository visibility is set to public. Legal teams should confirm that any open-source license adopted for public repositories is consistent with the organization's IP policies. Data mapping reviews should assess whether public repositories contain personal data triggering GDPR or CCPA obligations.
Full compliance analysis
Regulatory citations, enforcement risk, and due diligence action items.
Free: track 1 platform + weekly digest. Monitor: 25 platforms + same-day alerts. No credit card required.
Buried in Robinhood's customer agreement is broad authority to close your positions, suspend your account, and force arbitration. Here is what it actually says.
Stripe's terms authorize fund reserves, payout withholding, and account termination. Here is what the agreement states and what business owners should review.
Compliance Governance Intelligence
Need to monitor specific governance provisions?
Compliance includes provision-level monitoring, governance timelines, regulatory mapping, and audit-ready analysis.
Built from archived source documents, structured governance mappings, and historical version tracking.
The provision authorizes GitHub to display and reproduce your public repository content and grants other users a license to fork and view it, which is central to how GitHub's collaborative platform functions but also means public content can be used by others within the service.
Content posted to public repositories is licensed to GitHub and to all other GitHub users for display, forking, and reproduction on the platform. Developers hosting proprietary or sensitive code should ensure repositories are set to private to limit the scope of this license.
ConductAtlas has identified this type of provision across 5 platforms. See the full comparison.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by GitHub.