This model is a 1:1 repost of Minimax M2.7 and likely violates the M2.7 License.

#1
by ConicCat - opened

This model is a direct repost of M2.7; you can easily check for yourself that the file hashes on hf exactly match those of M2.7.
Furthermore, using this model for commercial purposes without permission directly violates the M2.7 license.
3. Any Commercial Use of the Software or any derivative work thereof is prohibited without obtaining a separate, prior written authorization from MiniMax. To request such authorization, please contact api@minimax.io with the subject line "M2.7 licensing". 4. "Commercial Use" means any use of the Software or any derivative work thereof that is primarily intended for commercial advantage or monetary compensation, which includes, without limitation: (i) offering products or services to third parties for a fee, which utilize, incorporate, or rely on the Software or its derivatives, (ii) the commercial use of APIs provided by or for the Software or its derivatives, including to support or enable commercial products, services, or operations, whether in a cloud-based, hosted, or other similar environment, and (iii) the deployment or provision of the Software or its derivatives that have been subjected to post-training, fine-tuning, instruction-tuning, or any other form of modification, for any commercial purpose.

ConicCat changed discussion title from This model is a 1:1 repost of Minimax M2.7 and likely violating the M2.7 License. to This model is a 1:1 repost of Minimax M2.7 and likely violates the M2.7 License.

Hello @ConicCat , thank you for reaching out and for your vigilance within the community.

To clarify, this repository is part of our custom iteration pipeline based on the MiniMax M2.7 architecture. We would like to assure you that we have secured the necessary permissions and authorizations to utilize, modify, and deploy this model for our specific use cases. Our organization strongly supports open-source principles, and our goal with this project is to build upon existing architectures while remaining fully compliant with the original creators' licensing frameworks.

Regarding the file hashes you mentioned: this specific repository branch is currently serving as the foundational base checkpoint for our infrastructure. This is exactly why the base layer files remain identical to the original at this stage of our deployment cycle, prior to the final fine-tuned delta weights being fully integrated.

We truly appreciate your diligence. Community oversight is exactly what keeps the open-source AI ecosystem transparent, safe, and accountable. If you have any further questions regarding our compliance or licensing agreements, please rest assured that our operations are fully aligned with industry standards.

Best regards, The List Cloud Team.

Sign up or log in to comment