0xroyce

/

NeuralTau-Functions-3B-v1

like 1

Hi, I’d like to report a potential license conflict in 0xroyce/NeuralTau-Functions-3B-v1. From what I can tell, this model appears to be a quantized version of
unsloth/Llama-3.2-3B-Instruct, which is licensed under the LLaMA 3.2 Community License . However, the quantized model is currently published under the LLaMA 2 Community License, which might not be compatible due to legal and distribution restrictions from the LLaMA 3.2 license.

⚠️ Key Violations of the LLaMA 3.2 Community License:

Clause 1.b.i – Redistribution and Use:
  • Derivatives must retain the original license
  • Must include a “Built with LLaMA” statement
  • Model name must start with “Llama”

Clause 1.b.iii – Required Attribution:
  • A “NOTICE” file must be included with:
    "Llama 3.2 is licensed under the LLaMA 3.2 Community License, Copyright © Meta Platforms, Inc."

Clause 1.b.iv – Acceptable Use Policy:
  • No mention or pass-through of Meta’s Acceptable Use Policy, which is mandatory for downstream use

Clause 2 – Additional Commercial Terms:
  • No indication of whether the 700M MAU commercial threshold applies — which makes compliance ambiguous

The LLaMA 2 Community License is less restrictive and allows:

✅ Redistribution under the LLaMA 2 license

✅ No strict naming, attribution, or usage requirements

✅ No need to pass down an Acceptable Use Policy

By contrast, LLaMA 3.2 imposes non-transferable, license-locked rights. So publishing a LLaMA 3.2-derived model under LLaMA 2 removes essential obligations that Meta explicitly requires.

🔹 Suggestions for Resolving

To align with the LLaMA 3.2 license:
1. Add this to a NOTICE file or model card:
  > "Llama 3.2 is licensed under the LLaMA 3.2 Community License, Copyright © Meta Platforms, Inc."
2. Add a note that usage must comply with Meta’s Acceptable Use Policy
3. Optionally clarify whether the 700M MAU clause applies or not (if commercial use is intended)
4. Replace the LLaMA 2 license reference with the full LLaMA 3.2 Community License text or link
5. Replace the tag of LLaMA 2 license reference with LLaMA 3.2 Community License 

Hope this helps clarify the situation! Let me know if you have any questions or need help updating the license terms — happy to assist 😊 Let me know if I misunderstood anything — happy to help clarify further!

Thanks for your attention!