AtomGit App Marketplace Publisher Agreement
Current Version: 1.0
Effective Date: November 03, 2026
Thank you for using the AtomGit (hereinafter referred to as the “Platform”) App Marketplace services.
The Platform’s App Marketplace (hereinafter referred to as the “Marketplace”) provides developers with plugin display, search, and distribution services. Through the Marketplace’s Actions module, you may publish and list automated plugins developed within your public repositories (hereinafter referred to as “Plugins”) for other users to reference, install, and run within their own projects.
Important Notice:
We specifically remind you that before utilizing the Marketplace publishing capability, please read the "AtomGit App Marketplace Publisher Agreement" (hereinafter referred to as this “Agreement”) completely and carefully. By thoroughly understanding all terms herein, particularly those limiting or exempting liability, publishing requirements and delisting mechanisms, and the Platform’s right of disposition, please note that clauses limiting or exempting liability may be presented in bold or other conspicuous formats to draw your attention. By checking the agreement box in the publishing wizard and clicking Submit, you are deemed to voluntarily commit to being bound by the terms of this Agreement, which shall become effective at that moment. If you do not accept the contents of this Agreement, please refrain from checking the box, and you may stop using the Marketplace publishing service by choosing not to submit, revoking published entries, or deactivating your account.
For the purposes of service feature development and in compliance with applicable laws and regulations, we may amend this Agreement from time to time. Upon any amendment, we will notify you via pop-ups, announcements, or other means. If you disagree with the amended contents, please immediately cease using the Marketplace publishing service. Your continued use of the Marketplace publishing service or retention of listed Marketplace entries shall be deemed as your acceptance of the amended Agreement.
You represent and warrant that upon using this Platform, you possess the civil capacity compatible with your actions as prescribed by the laws of the People's Republic of China. If you are a person with limited or no civil capacity, please review this Agreement and decide whether to accept its terms under the guidance of your statutory guardian. If you are accepting this Agreement on behalf of an entity rather than yourself, you shall be deemed to have obtained proper authorization to agree to this Agreement on behalf of that entity.
We specifically draw your attention to the following: The Marketplace’s plugin review consists solely of automated formal checks executed by the system according to established rules, without any manual substantive review. A plugin “passing the check” or being “published/listed” merely indicates that its formal requirements were met at the point of inspection; it does not constitute our approval, certification, recommendation, endorsement, guarantee, or warranty regarding the plugin. Where we grant certifications, badges, or other identifiers to specific plugins based on separately published rules, the application conditions, review standards, validity periods, re-review procedures, and revocation matters for such certifications and identifiers shall be governed by those respective rules.
This Agreement is a special stipulation supplementing the “AtomGit Service Terms.” In the event of any inconsistency between this Agreement and the “AtomGit Service Terms” regarding the publishing, display, distribution, delisting, or disposition of Marketplace listings, this Agreement shall prevail. Matters not covered herein shall be governed by the “AtomGit Service Terms” and other publicly posted behavioral norms and policies of this Platform.
I. Relevant Definitions
- App Marketplace: Refers to the functional module within this Platform used for publicly displaying, searching, and distributing applications and plugins, including its web interfaces, APIs, and配套distribution mechanisms.
- Plugin: Refers to a reusable automation unit stored in a code repository that can be referenced and invoked by others in their workflows, encompassing various forms such as script-based, containerized, and composite plugins.
- AI-based Plugin: Refers to a plugin that invokes, integrates, or otherwise utilizes generative artificial intelligence technology (including large model APIs, intelligent coding assistant extensions, etc.).
- Marketplace Entry: Refers to the display and distribution unit representing a specific plugin within the Marketplace, possessing an independent status.
- Publisher and You: Refers to the Platform user who initiates the publishing action and holds management permissions over Marketplace entries.
- User: Refers to a Platform user who references, installs, and runs a plugin within their own project or workflow.
- EULA: Refers to the End-User License Agreement you provide to Users for a plugin, including any open-source license or other equivalent licensing terms adopted by the plugin.
- Version Tags and Release Versions: Refers to version anchoring points. Version tags may be moved, deleted, or repointed to other commits, whereas specific commit records remain immutable.
- Runner: Refers to the computational environment where plugin code is actually executed, including official runners provided and managed by us, as well as self-hosted runners deployed and managed independently by Users.
- Scoped Token: Refers to a temporary credential issued by this Platform for executing plugins, with its scope strictly limited to the authorizations granted at issuance.
II. Publisher Information
- You shall ensure that all information filled in when registering with this Platform and publishing plugins is true, accurate, complete, and promptly updated.
- You shall bear responsibility for all publishing, modification, and revocation actions occurring under your account, including operations performed by your employees, agents, or personnel authorized by you.
III. Publishing Requirements, Checks, and Distribution Updates
1. Form Requirements for Publishing
Your submitted Marketplace entry must satisfy all of the following formal requirements. Failure to meet any single requirement will result in immediate rejection by the system, which will specify the missing items. You may resubmit after rectification:
(1) The plugin is stored in a public code repository;
(2) A repository contains only one plugin, without unrelated supplementary content;
(3) The plugin configuration specification file is located in the repository root directory and conforms to naming conventions;
(4) The plugin name is globally unique within the Marketplace and does not duplicate previously used names;
(5) Icons, descriptions, and usage documentation are provided as required;
(6) The usage documentation truthfully discloses the plugin’s purpose, required and optional parameters, necessary account secrets, execution entry points, runtime environments, and the scope of permissions and data access the plugin will obtain;
(7) A valid EULA accessible to Users has been provided;
(8) Other formal requirements periodically published by us.
The aforementioned requirements are continuous conditions, not one-time review items. During the lifespan of a Marketplace entry, if any requirement ceases to be satisfied, we reserve the right to halt distribution per Article IV and Article XII of this Agreement.
2. Nature of Checks
(1) The checks we perform on Marketplace entries are automated formal validations executed by the system according to established rules, aimed solely at verifying whether the objective requirements listed above are met;
(2) We do not conduct any manual reading, testing, evaluation, or substantive review regarding the logic, quality, functionality, performance, security, presence of vulnerabilities or malicious behavior, third-party right infringement, or compliance with any industry standards or regulatory requirements of the plugin code;
(3) Statements such as “Passed Check,” “Listed,” or “Status Normal” for a Marketplace entry merely indicate that its formal requirements were met at the point of inspection; they do not constitute our approval, certification, recommendation, endorsement, guarantee, or warranty, nor do they imply our endorsement of the plugin’s suitability for any specific purpose;
(4) You shall not mislead Users in any context (including but not limited to plugin documentation, Marketplace pages, external publicity, or commercial contracts) by claiming the plugin was “reviewed and approved by this Platform,” “platform-certified,” “officially recommended,” or similar. Violations thereof entitle us to immediately intercept and handle the entry per Article XII;
(5) Where we grant certifications, badges, or other identifiers to specific plugins based on separately published rules, the application conditions, review standards, validity periods, re-review procedures, and revocation matters for such certifications and identifiers shall be governed by those respective rules.
3. Classification of Failed Checks
A failed check signifies a failure in the formal validation of submitted information. This classification differs from an administrative “rejection.” You shall not claim that we have made any negative assessment or demand explanations for the reason.
4. Updates and Automatic Distribution
We may periodically inspect available updates for your Marketplace entries (including but not limited to bug fixes and feature enhancements). Upon your release of update versions to the Marketplace, these updates may be automatically requested, downloaded, and distributed to Users without further notice to you or the Users; we make no guarantees regarding the timing, coverage of updates, or actual acquisition status by Users. All update versions are subject to this Agreement and the EULA you publish for the plugin.
5. Formation and Record of the Agreement
This Agreement becomes effective at the moment you check the agreement box in the publishing wizard and click Submit. At that moment, we will record and retain the agreement version number, checkbox timestamp, your account identifier, operating IP address, and corresponding Marketplace entry ID as evidence of formation and content fixation. This Agreement is concluded in electronic text form; your expression of intent via checkbox click holds equal legal效力 to a written signature.
IV. Repository Public Visibility, Withdrawal, and Delisting
1. Continuous Public Obligation
You acknowledge and agree that the prerequisite and foundation for a plugin to be distributed via the Marketplace is that its host repository remains publicly visible. You commit to: during the existence of the Marketplace entry, continuously maintain the repository’s public visibility, refrain from converting it to private, refrain from deleting the repository, refrain from deleting or moving version tags of released versions, and refrain from restricting access to publicly available versions.
2. Irrevocable License for Published Versions
Regarding each specific version you have successfully published, the licenses to reproduce, cache, and distribute granted to us (detailed in Article IX) are irrevocable within the scope of that version. Subsequent conversion of the repository to private, revocation of publishing, or deletion of tags shall not affect our distribution licenses for cached snapshots of published versions per Article IX. We may continue distributing to previously referencing Users and reserve the right to cease distribution at any time.
3. Automatic Delisting upon Condition Failure
Upon your violation of Paragraph 1 of this Article, our system will automatically render the Marketplace entry undiscoverable and ineligible for distribution (“Delisted”). This disposition is executed by the system according to rules, requiring no additional decision from us, and we have no obligation to separately notify Users. If you restore the repository to public visibility, proceed per Paragraph 4 of this Article.
4. Restoration to Listing
After a Marketplace entry is delisted, restoring the repository to public visibility does not guarantee automatic re-listing. Typically, you must republish a version and pass all checks under Article III Paragraph 1 to regain discoverability.
5. Advance Notice and Continuing Obligations for Voluntary Withdrawal
(1) Should you intend to actively revoke publishing, cease maintenance, or convert the repository to private to withdraw the plugin from the Marketplace, you must announce this prominently on the Marketplace entry page and usage documentation thirty (30) days in advance;
(2) Your withdrawal from the Marketplace shall not affect the existing rights Users who have already installed, referenced, or acquired the plugin obtained under their EULA, nor shall it exempt you from delivery, support, and bug-fix obligations to such Users. You shall continue to fulfill them per their EULA and agreements with Users;
(3) If you withdraw without fulfilling the advance notice obligation, causing losses to Users, you shall bear full responsibility;
(4) We have no external disclosure obligation regarding the specific reasons for your withdrawal, except where laws, regulations, regulatory requirements, or judicial authorities mandate disclosure.
6. Allocation of Liability to Third Parties
(1) You shall provide maintainer contact information and alternative/migration instructions in your usage documentation or Marketplace page to guide Users upon your withdrawal;
(2) Any losses suffered by Users due to your violation of Paragraph 1 or exercise of disposal rights over your repository—including availability damage, business interruption, or replacement development costs—shall be borne solely by you, independent of us. Should Users assert claims against us, you shall fully indemnify us for related expenses incurred;
V. Version Management, Support, and Security Maintenance
1. Version Anchors
You shall release versions using version tags and release versions. You understand that version tags may be moved, deleted, or repointed to other commits; only specific commit records are immutable. Users referencing only major or minor version numbers will automatically fetch the code currently pointed to by that tag upon their next execution. We recommend Users lock to specific commit hashes, but this recommendation does not constitute our mandatory obligation or warranty.
2. Prohibition of Content Drift
You shall not replace the actual content of a published version within the same version number (including but not limited to patch versions) by moving tags, overwriting release artifacts, modifying build scripts, or altering dependencies. Nor shall you introduce breaking changes in patch versions. Where breaking changes are genuinely necessary, you must bump the major version number and prominently announce them on the Marketplace page and usage documentation, detailing the changes, impact scope, and migration paths.
3. Artifact and Source Code Consistency
You guarantee that the runtime entry and build configurations declared in the configuration specification match the source code committed to the repository; executable artifacts included in release versions are generated from that source code via the publicly documented build process in the repository. You shall not cause the actually executed logic to exceed the scope disclosed in the specification and usage documentation through any means, including build scripts, dependency injection, remote loading, environment variable hijacking, conditional triggers, etc.
4. Support and Maintenance Obligations
You shall provide technical support and maintenance for the plugin commensurate with its User base, and continuously display valid support contact channels (email, ticketing entry, or other reachable channels) on the Marketplace entry page for Users to seek support, file complaints, and assert rights. If you fail to respond to User support requests within a reasonable timeframe, provide significantly inadequate support quality, or provide false/outdated contact information, we reserve the right to reduce the search weight and exposure of the Marketplace entry, annotate risk warnings on the page, restrict new version publishing, or deliste/remove the entry in severe cases or after repeated User complaints without improvement.
5. Security Maintenance Obligations
(1) Upon discovering or becoming aware of security vulnerabilities, embedded malicious code, or credential leak risks in the plugin, you must release a patched version or publish a risk warning on the Marketplace page within twenty-four (24) hours;
(2) Where User credentials may be compromised, you must immediately take止损 measures;
(3) For widely adopted versions, you should make reasonable efforts to provide a transition period or指明 alternative solutions before ceasing maintenance.
6. Suspension Right for User Violations
If a User employs your plugin in violation of this Agreement, related Platform rules, or your EULA, we have the right to suspend or terminate that User’s access to and usage of the plugin. We shall bear no liability to you for exercising this right.
VI. End-User License Agreement (EULA)
1. Provision of EULA
You must provide a separate EULA or other equivalent licensing terms (including any adopted open-source license) for each plugin, and provide an access path prominently on the Marketplace entry page or usage documentation. Absent an EULA, you are deemed to adopt the open-source license contained in the plugin’s repository as the EULA. If the repository also lacks such declaration, we may require you to supplement it and refuse publishing applications until supplemented.
2. Non-Party Status to EULA
You acknowledge and agree: The EULA is formed solely between you and Users. We are not a party to the EULA, bear no responsibility for rights or obligations thereunder, and do not participate in disputes arising from the EULA between you and Users. Complaints, claims, or administrative penalties caused by your EULA shall be handled by you with consequent liabilities borne by you.
3. Us as Third-Party Beneficiaries
You shall explicitly state in your EULA that this Platform is a third-party beneficiary, entitled to directly request Users to fulfill obligations related to Platform interests. Absent such statement, we may require you to assert rights against Users violating the EULA to our detriment, in your name; you must promptly assert such rights upon receiving our notice and inform us of the outcome. Failure to do so without justified reasons entitles us to dispose of the matter per Article XII. You hereby authorize us to issue notices, negotiate, and assert rights against violating Users in your name.
4. Disclosure and Revocation of Permission Scope
Where a plugin requires User authorization (including but not limited to tokens, repository read/write permissions, data access scopes), you must itemize each requested permission and its purpose in the documentation, applying in accordance with the principle of minimum necessity. Upon User revocation of authorization, you must delete obtained User data within the公示 period and confirm with us.
VII. Special Requirements for AI-based Plugins
1. Scope of Application
Where your plugin invokes, integrates, or otherwise utilizes generative AI technology, in addition to complying with other provisions herein, you must comply with this Article.
2. Your Specific Obligations
(1) Pre-release Testing: Test the plugin across diverse input scenarios to ensure outputs within foreseeable ranges do not violate this Agreement, related Platform rules, or laws;
(2) Prominent Disclosure and Content Labeling: Inform Users prominently in the interface or output that they are interacting with generative AI, and fulfill content labeling obligations according to law (including explicit labeling and metadata labeling, subject to our published technical specifications);
(3) Feedback and Reporting Mechanisms: Provide channels for Users to report errors, defects, inappropriate outputs, or unexpected results, and grant us reception permissions or establish regular synchronization mechanisms for these channels. Upon receiving reports against the plugin, you must respond promptly;
(4) Applicable Scenarios and Limitations: Describe applicable scenarios, best practices, and known limitations in documentation. Do not imply outputs constitute professional advice, are fully trustworthy, or can replace human review;
(5) Lawful Data Sources: Guarantee lawful training data sources, avoiding infringement of others’ intellectual property, trade secrets, personal information rights, and other legitimate rights. Where personal information processing occurs, secure the legality basis required by laws.
3. Prohibitions
You shall not use AI-based plugins to generate or disseminate content violating laws/regulations or Article XI of this Agreement. You shall not bypass model safety alignment via prompt injection or other methods. You shall not use plugins to bulk-generate spam, misinformation, or conduct automated attacks.
4. Cooperation with Compliance Obligations
You shall independently fulfill obligations as a generative AI service provider (where applicable), including security assessments, algorithm registration, content labeling, and illegal content handling. Providing a distribution channel does not make us liable for these obligations. Upon compliance verification, content labeling checks, or disposal measures by us pursuant to laws, you shall cooperate and provide required materials. Failure to cooperate or rectify per published obligations entitles us to dispose per Article XII, including suspending the plugin’s model invocation capabilities.
VIII. Representations and Warranties
You make the following continuing representations and warranties regarding each Marketplace entry, every version, and accompanying documentation, which remain true, accurate, and complete throughout the entry’s lifespan:
-
Rights Ownership: You are the copyright owner of the plugin code, documentation, icons, identifiers, and other accompanying content, or have obtained sufficient valid authorizations to perform this Agreement, including copyrights, patents, trade secrets, and trademark rights.
-
Non-Infringement: The plugin and its distribution/execution do not infringe, misappropriate, or violate any third party’s copyrights, patents, trademarks, trade secrets, portrait rights, reputation rights, data rights, or other legitimate rights, nor constitute unfair competition.
-
Open-Source License Compliance: Third-party code, components, and dependencies included in or relied upon by the plugin comply with their respective open-source licenses or equivalent terms (including attribution, license copies, source availability, and copyleft fulfillment); your distribution in the Marketplace does not violate the plugin’s adopted open-source license or any third-party terms; where open-source, you guarantee the license permits us to copy, display, and distribute per this Agreement.
-
No Malicious Features: The plugin does not contain, hide, or load/execute during runtime any: viruses, trojans, worms, backdoors, ransomware; undisclosed cryptocurrency mining; undisclosed outbound network connections, data回传, or telemetry; reading, retaining, or transmitting User credentials, tokens, or environment variables; privilege escalation, sandbox escape, host environment persistence; use as command-and-control infrastructure or vulnerability delivery channels; or other acts exceeding disclosed scope.
-
Legality: The plugin and its content comply with mandatory provisions of current PRC laws, administrative regulations, departmental rules, and national standards, do not contain legally prohibited information, do not endanger cybersecurity, and do not interfere with normal Platform/User usage.
-
Content Truthfulness: Filled plugin names, descriptions, categories, icons, screenshots, examples, release notes, compatibility statements, and other display information are true and accurate, free of fictitious, exaggerated, or misleading statements, do not constitute false or misleading commercial promotion, and do not intend to mislead or confuse Users. You shall not artificially inflate rankings or ratings via fake volume, fake reviews, or fraudulent transactions.
-
No Unsolicited Commercial Messages: The plugin’s design purpose and practical application shall not include sending unsolicited commercial electronic messages to Platform Users, end-users, or other third parties.
-
Data and Personal Information Compliance: Where the plugin accesses/processes data during execution, you guarantee:
① Data access is strictly limited to what is necessary for the plugin’s declared functions, adhering to the minimum necessity principle;
② No reading, retaining, or third-party transmission of data undisclosed in specifications/documentation, especially prohibiting backtransmission of scoped tokens, environment variables, source code, build artifacts, or sensitive log information to your or third-party servers;
③ Where personal information processing occurs, you have the legality basis required by the PRC Personal Information Protection Law, and have fulfilled notification, separate consent, de-identification, and cross-border transfer obligations per agreements with Users or statutory requirements;
④ Without prior User consent or statutory mandate, you shall not alter personal information affecting integrity, disclose it to third parties, or use it for purposes beyond plugin functionality provision;
⑤ You shall not leverage plugin execution to build separate data sets, training datasets, or user profiles for yourself or third parties; nor use personal information for advertising or third-party sales;
⑥ You shall provide a legally compliant privacy policy clarifying your identity as a processor, processing purposes, storage location, sharing recipients, and User rights exercise methods. You shall not collect personal information in the Platform’s name or purporting to represent the Platform.
-
Third-Party Terms Compliance: Where the plugin invokes third-party services, APIs, or platforms, you have complied with their terms and call limits (including explicit rate limits) and sufficiently disclosed relevant calls to Users.
-
Export Control and Sanctions Compliance: Neither you nor the plugin’s distribution/use violates export control, technology import/export, economic sanctions, or anti-money laundering regulations of the PRC and applicable jurisdictions. You are not on any sanctions list, and you shall not supply the plugin to restricted entities or for restricted purposes. Violation of any warranty herein constitutes a material breach. We reserve the right to dispose per Article XII and demand compensation per Article XV.
IX. Grant of Licenses
1. License Grant to Us and Partners
We require lawful rights to serve you and your plugins, such as display, distribution, and execution. You grant us, or authorize us to delegate to our affiliates or partners, worldwide, free-of-charge, non-exclusive, sublicensable, and transferable rights to store, archive, parse, reproduce, publish, display, share, and disseminate your Marketplace content (including plugin code, configuration specifications, usage documentation, icons, descriptions, screenshots, metadata, and version snapshots), including the right to make derivative copies, strictly for Marketplace service provision, including but not limited to: copying content to our/partners’ databases and creating backups; displaying to you and Users; parsing into search indexes or analyzing on our servers; executing plugin code on Runners per explicit User instructions; and reasonably excerpting, compiling, formatting, translating, and redisplaying for Marketplace operation, ecosystem promotion, security monitoring, and compliance review.
To the extent necessary for distribution, availability, and security, we may generate and retain version snapshots, caches, and other copies of your plugins. For each successfully published specific version, the foregoing license is irrevocable; however, we retain the right to cease distribution at any time.
2. Use of Brand Identifiers in Promotion
You grant us a license to use your brand identifiers in any materials promoting the Marketplace. Upon ceasing distribution of a plugin via the Marketplace, we will cease using that product’s identifiers in promotional materials, except where necessary to explain historical Marketplace content, fulfill disclosure obligations, or comply with laws/regulations.
3. License Grant by You to Other Users
You must explicitly grant Users the right to download, install, and run the plugin via the EULA (including its adopted open-source license). You commit that licenses granted to Users under the Marketplace distribution scenario cannot be unilaterally withdrawn; after plugin usage, you shall not assert rights or fees beyond the declared scope.