Forking & Cloning Policy
Binding policy governing the listing, use, modification, and monetization of forked and cloned projects on Uhpenry, including attribution, licensing compliance, and enforcement.
This Forking & Cloning Policy (“Policy”) governs the rights, restrictions, and obligations related to the listing, reuse, and monetization of forked or cloned repositories on the Uhpenry platform (“Platform”).
By listing or monetizing a project on Uhpenry, you agree to be bound by this Policy, our Terms of Service, and all applicable licenses and laws.
1. Definitions
1.1 Forking means creating a derivative repository from an existing one using GitHub's official fork functionality.
1.2 Cloning means duplicating a repository's codebase by any means, whether or not GitHub's fork mechanism is used.
1.3 Booth means a seller account or entity operating a storefront on Uhpenry.
1.4 Booth-Level Logs means internal Uhpenry tracking data regarding project origins, repository lineage, and fork/clone relationships.
Such logs are maintained for enforcement purposes and are not publicly disclosed, except where disclosure is legally required or necessary for dispute resolution.
2. Forking Rules
2.1 Forking is permitted only if the original repository is already listed on Uhpenry by its lawful owner.
2.2 A forked project may be listed only with:
-
Explicit permission from the original owner, or
-
Authorization via Uhpenry's platform-level permissions system.
2.3 Forked projects must:
-
Clearly attribute the original creator.
-
Include a modified
READMEor equivalent documentation describing its derivation.
3. Fork Monetization
3.1 Monetization of forked projects is prohibited unless:
- Substantial and original modifications have been made, including but not limited to: new features, performance improvements, or additional integrations.
- Revenue sharing is enabled and allocates:
-
30% to the original owner
-
8% to Uhpenry (or 6% for early adopters)
-
The balance to the forking developer.
3.2 Temporary Restriction:
Fork monetization is currently disabled pending implementation of Uhpenry's revenue distribution and attribution systems.
During this period, forked projects cannot be monetized or publicly listed for sale.
-
4. Cloning Rules
4.1 A cloned repository may be listed on Uhpenry only if:
-
Its license permits redistribution (e.g., MIT, Apache-2.0), and
-
Clear attribution is provided in both the project
READMEand metadata.4.2 For private or restricted repositories, verifiable written permission from the original owner is required.
4.3 The following are strictly prohibited:
-
Monetizing a clone without substantial and original contributions.
-
Cloning a project without lawful or licensed access.
-
Misrepresenting a clone as original work.
-
Using cloned repositories to bypass Uhpenry's fork detection or revenue-sharing mechanisms.
5. Enforcement & Abuse Prevention
5.1 Any user who:
- Clones or forks a project to evade detection or avoid revenue sharing, or
- Falsifies authorship, licenses, or permissions,
shall have their Uhpenry account permanently suspended.
5.2 Uhpenry may also:
- Ban the associated GitHub account or OAuth credentials from future platform use,
- Retain booth-level logs for investigation and evidence,
- Escalate to legal action in accordance with our Terms of Service.
6. Attribution & Compliance
6.1 All forked and cloned projects must:
- Include all required license files from the upstream source.
- Comply fully with original license terms, including attribution, redistribution rules, and copyright notices.
- Operate within the scope of both GitHub's and Uhpenry's policies.
7. Reporting Violations
7.1 Uhpenry monitors for policy violations using both automated systems and booth-level logs.
7.2 Users may report suspected violations through the Platform's reporting tools.
7.3 Uhpenry reserves the right to:
- Suspend, delist, or permanently ban accounts,
- Revoke monetization privileges,
- Notify GitHub and other stakeholders in cases of serious abuse.
8. GitHub Disclaimer
Uhpenry is an independent service built on GitHub's public APIs and infrastructure.
Uhpenry is not affiliated with, endorsed by, or officially connected to GitHub, Inc.
All GitHub trademarks, logos, and brand names belong to GitHub, Inc.
Any integration with GitHub is conducted in compliance with GitHub's API terms and licensing agreements.
9. Binding Effect
By listing or monetizing a forked or cloned project on Uhpenry, you acknowledge that violations of this Policy may result in immediate enforcement actions, including but not limited to account termination, removal of content, forfeiture of earnings, and legal proceedings.
Uhpenry Licensing Terms
Binding legal terms governing the licensing, sale, and distribution of projects through the Uhpenry platform, including AI-generated code disclosures and enforcement scope.
Third-Party Cookies Policy
Sets forth the terms under which third-party cookies are used on Uhpenry, including purposes, data collection, management, and compliance obligations.