This document explains how the AutoFigure-Edit name, logo, and related branding may be used.
It is intended to be practical and lightweight. It does not change the open-source software license.
These guidelines apply to:
- the
AutoFigure-Editname - the AutoFigure-Edit logo and visual brand assets
- official project, product, and service names used by ResearAI for AutoFigure-Edit
The source code remains licensed under the repository's software license. Trademark rights are separate from copyright and software license rights.
You may generally do the following without asking for separate permission:
- use the name
AutoFigure-Editto factually refer to this project - say that your work is based on, compatible with, or built with AutoFigure-Edit
- link to the official repository, paper, website, and documentation
- discuss, review, compare, benchmark, or cite AutoFigure-Edit in papers, blog posts, talks, and tutorials
- fork the code and state that your fork originated from AutoFigure-Edit
Examples of generally acceptable use:
Built with AutoFigure-EditThis project is a fork of AutoFigure-EditCompatible with AutoFigure-Edit SVG workflow
Please do not use the AutoFigure-Edit name, logo, or branding in ways that are likely to confuse users about source, sponsorship, certification, or official status.
Without prior written permission, please do not:
- present your fork, hosted service, plugin, benchmark, or derivative product as the official AutoFigure-Edit project
- use the AutoFigure-Edit logo as the primary brand for a modified or third-party product
- name a modified distribution in a way that strongly suggests it is the official release
- register or use domain names, package names, app listings, or social-media handles that are likely to confuse users into thinking your project is the official AutoFigure-Edit offering
- imply endorsement, certification, partnership, or approval by ResearAI when that is not true
- use phrases such as
official,certified,by ResearAI, or similar claims in a misleading way
Examples of problematic use:
Official AutoFigure-Edit CloudAutoFigure-Edit Studiofor an unrelated third-party hosted product- using
autofigure-editas the primary package or service name for a modified public distribution without clearly identifying it as unofficial - shipping a modified fork under the unchanged AutoFigure-Edit product name in a way that hides that it is a fork
You may fork, modify, and redistribute the code under the repository's software license.
If you distribute a modified version as a separate product or service, please make the modified status clear.
Good patterns include:
ProjectName, based on AutoFigure-EditAutoFigure-Edit fork by <your org>Modified AutoFigure-Edit build for internal use
If your fork is becoming a distinct public-facing product, we strongly prefer that you adopt your own primary product name and branding.
We do not object to reasonable nominative or descriptive use of the AutoFigure-Edit name when you are accurately referring to the project.
That includes:
- documentation
- comparative evaluations
- academic citations
- compatibility notes
- tutorials
- screenshots of the unmodified product
These trademark guidelines do not change:
- the repository software license
- your rights to use, study, modify, or redistribute the code under that license
They only address branding, naming, and source-identification issues.
If AutoFigure-Edit materially helps a paper, report, or public figure artifact, we strongly encourage citation of the AutoFigure-Edit paper and clear disclosure of meaningful AI assistance.
See:
If you want to:
- use the AutoFigure-Edit logo in a commercial context
- use the AutoFigure-Edit name for a public hosted service
- request explicit permission for co-branding or partnership-style usage
please contact:
resear.ai@gmail.com
These guidelines are intended to stay lightweight and practical.