PyPI metadata still declares "Other/Proprietary License" although the project is MIT-licensed
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 LicensewithLicense :: OSI Approved :: MIT License - Set
license="MIT"
Option B (PEP 639 style)
- Use an SPDX license expression (
license_expression="MIT"insetup.py, orlicense = "MIT"under[project]inpyproject.toml) - Remove the
License ::classifier (newer setuptools rejects having both) - Requires
setuptools>=77in[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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/azureml-inference-server
-
Difficulty 1/5 Under an hour Newbie friendliness 70/100
microsoft/azureml-inference-server#77 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
microsoft/azureml-inference-server#116 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 18/100
microsoft/azureml-inference-server#112 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
microsoft/azureml-inference-server#111 · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 55/100
microsoft/azureml-inference-server#104 ·
Maintainers usually reply within 1 day
All issues in microsoft/azureml-inference-server
Similar issues
-
Layout accepts a step threshold of 0 or less, then in-toto-verify crashes with StopIterationPossibly taken @BahaaMattar claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
needs discussion
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
openfga/openfga.dev#1436 · 1 comment ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
usb-device-hid: MouseInterface reports bInterfaceProtocol 1 (keyboard) instead of 2Possibly taken @Duhan07 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
micropython/micropython-lib#1176 ·