Contributor IP and Submission Rules

Version: 2026-03-23

This page supplements the Legal Notice, the repository license, and the contribution process. It states baseline provenance expectations for code, documentation, assets, and release inputs submitted to AniBridge.

1. Core Representation

By submitting a contribution, the contributor represents that, to the best of their knowledge and authority, they are entitled to submit the material under the repository's licensing and contribution rules.

2. Material That Must Not Be Submitted

Do not submit:

• proprietary or confidential code that you are not authorized to contribute;
• copied documentation, images, branding, or other assets without permission or a clear license basis;
• secrets, API keys, cookies, session tokens, personal credentials, or private datasets;
• decryption keys, credential packs, or other materials primarily intended to bypass access controls;
• content that falsely suggests third-party sponsorship, endorsement, or affiliation.

3. Provenance Expectations

Contributors should be prepared to identify the origin of non-trivial submitted material, especially where it includes imported assets, vendored code, or text adapted from another source.

If a contribution depends on third-party material, the contributor should make the applicable license or permission status clear in the pull request or commit context.

4. Maintainer Response

Maintainers may request clarification, reject a contribution, remove submitted material, or ask for remedial changes where provenance, entitlement, or legal status is unclear.

Acceptance of a pull request does not waive the project's ability to revisit or remove material later if a legitimate rights or compliance issue is identified.