Provision record
GitHub · GitHub Terms of Service · View original document ↗

User-Generated Content License Grant

Medium severity Medium confidence Explicit document language Common · 263 of 352 platforms
Stay ahead of the changes
Track GitHub and get the diff the day its terms change.
Share 𝕏 Share in Share 🔒 PDF
Document Record

What it is

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

ConductAtlas Analysis

Why it matters (compliance & governance perspective)

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.

Recent Activity

This document changed recently

Medium Apr 28, 2026

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 →
Medium Apr 19, 2026

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 →

Clause Stability Stable

0
Changes
5
Months Monitored
May 12, 2026
First Seen
May 22, 2026
Last Seen
This clause type exists across 1689 other provisions on other platforms.

Change history

added Jul 11, 2026

This newly detailed provision explicitly defines the scope and conditions of the license users grant to GitHub and other users for public repositories, clarifying forking and display rights.

View full change record →

Consumer impact (what this means for users)

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.

What you can do

⚠️ These actions may provide transparency or partial mitigation but may not fully address the underlying issue. Effectiveness varies by jurisdiction and individual circumstances.
  • Export Your Data
    Navigate to GitHub Settings and review each repository's visibility setting. Change any public repositories containing sensitive or proprietary content to private to limit the scope of the content license.

How other platforms handle this

Mailchimp Medium

we may closely review accounts that offer the following services, products, or content: Online trading, day trading tips, and stock market related content

Leonardo AI Medium

Paid Subscribers can select whether Content is public or private.

Tinder Medium

If Your Content is prohibited under the laws of any jurisdiction where our Services are available, we may remove it even if it is not illegal in your location.

See all platforms with this clause type →
▸ View Original Clause Language DOCUMENT RECORD
"
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 Terms of Service

ConductAtlas Analysis

Institutional analysis (regulatory & governance intelligence)

REGULATORY LANDSCAPE: This provision engages copyright law under Title 17 of the U.S.

Insight

Unlock the full institutional analysis

Enforcement risk, jurisdiction flags, contract triggers, and due diligence action items.

Applicable agencies

  • Federal Trade Commission (ftc)
    Oversees unfair or deceptive business practices and can investigate companies that mislead consumers about data collection, sharing, or use.
    Who can file: Anyone affected by the company's practices (US or international)
    What you need: Your account details, a timeline of relevant events, and a description of the specific issue
    What to expect: Complaints inform FTC enforcement priorities and investigations but do not result in individual resolution or compensation
    File a complaint →

Applicable regulations

DSA
European Union

Provision details

Document information
Document
GitHub Terms of Service
Entity
GitHub
Document last updated
May 5, 2026
Tracking information
First tracked
May 10, 2026
Last verified
May 12, 2026
Record ID
CA-P-011572
Document ID
CA-D-00253
Evidence Provenance
Source URL
Wayback Machine
Content hash (SHA-256)
610460507af6f60333f6195921a4e0d9629d1fea528d1220cda7340159b5b46b
Analysis generated
May 10, 2026 17:12 UTC
Methodology
Evidence
✓ Snapshot stored   ✓ Hash verified
Citation Record
Entity: GitHub
Document: GitHub Terms of Service
Record ID: CA-P-011572
Captured: 2026-05-10 17:12:21 UTC
SHA-256: 610460507af6f603…
URL: https://conductatlas.com/platform/github/github-terms-of-service/provision/CA-P-011572/user-generated-content-license-grant/
Accessed: Sept. 8, 2026
Permanent archival reference. Stable identifier suitable for legal filings, compliance documentation, and research citation.
Classification
Severity
Medium
Categories

Other risks in this policy

Related Analysis

Get the research letter

Companies change their terms quietly. We read every version and catch what actually changed. One email a week on the changes that matter and what they mean.

Frequently Asked Questions

What does GitHub's User-Generated Content License Grant clause do?

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.

How does this clause affect you?

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 many platforms have this type of clause?

ConductAtlas has identified this type of provision across 263 platforms. See the full comparison.

Is ConductAtlas affiliated with GitHub?

No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by GitHub.