How does TripoSG's MIT declaration sit alongside the Tencent agreements and the BRIA licence that its own files and NOTICE point to, and where do the texts conflict?
At commit fc5c40990181e2a756c4e0b1c2f4d6b5202faf8c TripoSG declares MIT at the root while one file states that its use is subject to the Tencent Hunyuan Community License Agreement (with the agreement text embedded), a second licence file in triposg/ is the FlashVDM agreement, and NOTICE adds BRIA and Tencent code. The Tencent template lets modifiers add other licence terms 'except' where its sections 3 and 5 apply, and both agreements restrict territory and other-model improvement; whether and how those survive in an MIT-labelled release is not stated by any of the texts. Separately, FlashVDM's own source files name a Non-Commercial agreement while its LICENSE and NOTICE name the Community agreement, and RMBG-1.4's licence URL is dead. No conclusion on legal effect is drawn.
Structured fields
{
"citations": [
{
"url": "https://github.com/VAST-AI-Research/TripoSG/tree/fc5c40990181e2a756c4e0b1c2f4d6b5202faf8c",
"note": "FlashVDM d16f5b99 attention_processors.py L1, L13 (producer work copy); FlashVDM d16f5b99 volume_decoders.py L1, L13 (curator raw GET, byte-identical to work copy); FlashVDM NOTICE L7, L9; FlashVDM LICENSE; TripoSG triposg/LICENSE (curator raw GET)"
},
{
"url": "https://github.com/Tencent/FlashVDM/tree/d16f5b99b5185170e4cf14d5568f2264ba5894d0",
"note": "FlashVDM d16f5b99 attention_processors.py L1, L13 (producer work copy); FlashVDM d16f5b99 volume_decoders.py L1, L13 (curator raw GET, byte-identical to work copy); FlashVDM NOTICE L7, L9; FlashVDM LICENSE; TripoSG triposg/LICENSE (curator raw GET)"
},
{
"url": "https://github.com/Tencent/HunyuanDiT/tree/bf37693476a86e281006173ddd364debbb3c3624",
"note": "FlashVDM d16f5b99 attention_processors.py L1, L13 (producer work copy); FlashVDM d16f5b99 volume_decoders.py L1, L13 (curator raw GET, byte-identical to work copy); FlashVDM NOTICE L7, L9; FlashVDM LICENSE; TripoSG triposg/LICENSE (curator raw GET)"
}
]
}Evidence claims
- [sourced_fact] At commit fc5c40990181e2a756c4e0b1c2f4d6b5202faf8c TripoSG declares MIT at the root while one file states that its use is subject to the Tencent Hunyuan Community License Agreement (with the agreement text embedded), a second licence file in triposg/ is the FlashVDM agreement, and NOTICE adds BRIA and Tencent code. The Tencent template lets modifiers add other licence terms 'except' where its sections 3 and 5 apply, and both agreements restrict territory and other-model improvement; whether and how those survive in an MIT-labelled release is not stated by any of the texts. Separately, FlashVDM's own source files name a Non-Commercial agreement while its LICENSE and NOTICE name the Community agreement, and RMBG-1.4's licence URL is dead. No conclusion on legal effect is drawn. · locator: FlashVDM d16f5b99 attention_processors.py L1, L13 (producer work copy); FlashVDM d16f5b99 volume_decoders.py L1, L13 (curator raw GET, byte-identical to work copy); FlashVDM NOTICE L7, L9; FlashVDM LICENSE; TripoSG triposg/LICENSE (curator raw GET) source
Rights
| component | license | hosting | redistribution | modification | training | Evidence and notes |
|---|---|---|---|---|---|---|
| documentation | unknown | permitted | permitted | unknown | unknown | Applies to this original summary only, not to the cited sources. |