Add the LICENSE file — pyproject references one that doesn't exist (inference code has no licence)

Open Beginner friendly
#24 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Quiet
Tech stack
python
Domain
documentation

Research direction

Start by reading pyproject.toml's license reference and the README licensing statement, then inspect the repository tree for existing LICENSE, COPYING, or NOTICE files. Done means the referenced license file exists and the repository's inference code licensing is stated unambiguously alongside the model-weights explanation.

Written by the indexing model from the issue text.

Description

Thanks for releasing MOSS-Audio — the work is excellent.

The model weights on Hugging Face are clearly Apache-2.0 (e.g. OpenMOSS-Team/MOSS-Audio-4B-Instruct declares license: apache-2.0). But the inference/modeling code in this repository appears to carry no licence:

  1. There's no LICENSE / COPYING / NOTICE file anywhere in the repo tree.
  2. pyproject.toml declares license = { file = "LICENSE" } — a reference to a LICENSE file that doesn't exist in the repo.
  3. The README's "Models in MOSS-Audio are licensed under the Apache License 2.0" reads as covering the weights, not unambiguously the src/ code (modeling_moss_audio.py, hf_inference.py, …).

The HF weights repos ship only configuration_*.py + processing_*.py (no modeling_*.py; config.json's auto_map has no AutoModel entry), and the documented run path is git clone … && pip install -e . && python infer.py — so running the Apache-2.0 weights requires this repository's code. Absent an explicit licence, that code defaults to "all rights reserved," which blocks self-hosting and derivative use even though the weights are openly licensed and the intent looks open.

Could you add the missing LICENSE file (presumably Apache-2.0, to match the weights and the pyproject reference)? That would make the self-host / derivative-use story unambiguous. Thanks!

Dominant language
Python
Stars
667
Forks
45
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OpenMOSS/MOSS-Audio

All issues in OpenMOSS/MOSS-Audio

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.