PyPI metadata still declares "Other/Proprietary License" although the project is MIT-licensed

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

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
76/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
python
Domain
build-system

Research direction

Inspect the packaging configuration that defines the package license and classifiers; the issue does not name its file, so locate the metadata settings first. Compare them with the MIT license and choose one of the suggested packaging options. Build the wheel and check its METADATA for an MIT license expression or the OSI Approved MIT classifier, with no proprietary license classifier.

Written by the indexing model from the issue text.

Description

Summary

The repository is licensed under MIT (see LICENSE), but the package metadata published to PyPI still classifies azureml-inference-server-http as proprietary.

On the PyPI page for 1.6.1, the License section shows:

Other/Proprietary License (https://opensource.org/license/MIT)

and the classifiers include:

License :: Other/Proprietary License

Background

The 1.6.0 changelog notes "Corrected the package license URL to point to the MIT license", so the license URL was updated. However, the License :: Other/Proprietary License classifier appears to be left over from before the project was open-sourced (earlier releases pointed to https://aka.ms/azureml-sdk-license). PyPI displays the classifier name with the license field in parentheses, which produces the contradictory "Other/Proprietary License (.../MIT)" label.

Impact

Software composition analysis tools (e.g. Sonatype, and others that read PyPI metadata or wheel METADATA) report this package as having a proprietary license. In organizations with license policies, this blocks or flags the package and requires manual waivers, even though the code is MIT-licensed.

Suggested fix

Either of the following in the packaging configuration:

Option A (minimal change)

  • Replace the classifier License :: Other/Proprietary License with License :: OSI Approved :: MIT License
  • Set license="MIT"

Option B (PEP 639 style)

  • Use an SPDX license expression (license_expression="MIT" in setup.py, or license = "MIT" under [project] in pyproject.toml)
  • Remove the License :: classifier (newer setuptools rejects having both)
  • Requires setuptools>=77 in [build-system] requires

After the change, the built wheel's METADATA should contain Classifier: License :: OSI Approved :: MIT License (Option A) or License-Expression: MIT (Option B).

Dominant language
Python
Stars
28
Forks
10
Avg merge
7h 58m
Merged PRs (30d)
10

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 microsoft/azureml-inference-server

All issues in microsoft/azureml-inference-server

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.