Skip to content

Add new license llama-3-license-2024 for Meta Llama 3 - #5277

Open
MGpromax wants to merge 2 commits into
aboutcode-org:developfrom
MGpromax:add-llama-3-license-2024
Open

Add new license llama-3-license-2024 for Meta Llama 3#5277
MGpromax wants to merge 2 commits into
aboutcode-org:developfrom
MGpromax:add-llama-3-license-2024

Conversation

@MGpromax

@MGpromax MGpromax commented Aug 24, 2026

Copy link
Copy Markdown

Fixes #5269

Adds a new license llama-3-license-2024 for the Meta Llama 3 Community License Agreement (Meta Llama 3 Version Release Date: April 18, 2024), which was not yet in LicenseDB (the 3.1/3.2/3.3 agreements are separately titled and already keyed).

Choices made, following the existing llama-2-license-2023, llama-3.1-license-2024 and llama-3.2-license-2024 entries:

  • key llama-3-license-2024 by analogy with the sibling keys, as suggested in the issue
  • category: Proprietary Free, owner: Facebook, spdx_license_key: LicenseRef-scancode-llama-3-license-2024
  • the text is the agreement as published at https://github.com/meta-llama/llama3/blob/main/LICENSE (fetched from the raw URL in the issue), without the appended "Meta Llama 3 Acceptable Use Policy", consistent with the sibling entries which all end at section 7 (Governing Law and Jurisdiction)

Validation:

  • scancode-reindex-licenses runs clean
  • scanning the full upstream LICENSE file (agreement + appended AUP) now detects the agreement portion as llama-3-license-2024 with score 100 (lines 1-41). The appended AUP portion still partially matches llama-4-license-2025 (score ~66); if you want a dedicated rule or key for the Llama 3 AUP text I am happy to add it here or in a follow-up.
  • pytest tests/licensedcode/test_license_models.py passes locally

Tasks

  • Reviewed contribution guidelines
  • PR is descriptively titled 📑 and links the original issue above 🔗
  • Tests pass -- look for a green checkbox ✔️ a few minutes after opening your PR
  • Commits are in uniquely-named feature branch and has no merge conflicts 📁
  • Updated documentation pages (if applicable) -- not applicable
  • Updated CHANGELOG.rst (if applicable) -- not applicable

Add new license llama-3-license-2024 for the Meta Llama 3 Community
License Agreement (April 18, 2024 version), following the pattern of
the existing llama-2, llama-3.1, llama-3.2 and llama-3.3 license
entries. The license text is the agreement as published at
https://github.com/meta-llama/llama3/blob/main/LICENSE without the
appended Acceptable Use Policy, consistent with the sibling entries.

Reference: aboutcode-org#5269

Signed-off-by: Manoj Gowda <manojgowdabs18@gmail.com>
The CI license_validate_ignorables job caught that the declared
ignorable_urls did not match the detected ones: the Meta brand
guidelines URL keeps its trailing slash. Regenerated the ignorables
with SCANCODE_REGEN_TEST_FIXTURES=yes running
tests/licensedcode/test_detection_validate.py, which also normalized
the file ending to the canonical dump format. Both validation tests
for this license now pass locally.

Signed-off-by: Manoj Gowda <manojgowdabs18@gmail.com>
@MGpromax
MGpromax force-pushed the add-llama-3-license-2024 branch from f241efa to 4e6f075 Compare August 24, 2026 08:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

New license request: Meta Llama 3 Community License Agreement

1 participant