You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Drop the versionless License :: classifier now that license is a valid SPDX expression #434
This issue is part of a larger batch of similar-scoped issues we distribute in the context of our internal vulnerability and dependency tracking activities. The batch covers multiple projects, this is only one of them. The goal is to rise awareness and trigger/initiate the change towards clean project metadata in projects we depend on.
Summary
This project already declares a valid SPDX license id/expression in its packaging metadata (License: MPL-2.0 in the built METADATA), but the deprecated classifier License :: OSI Approved :: Mozilla Public License 2.0 (MPL 2.0) is still present. PEP 639-aware SBOM tooling like cyclonedx-bom can't map it to an SPDX id, so it falls back to emitting the raw classifier text as a free-text license name. This free-text field is just noise and causes downstream tooling to flag this project as non-SPDX-compliant.
Suggested fix
Remove the redundant License :: OSI Approved :: from classifiers in the packaging config. No change to the license field is needed.
It's a bit early to drop the prior best practice for one only standardized relatively recently in the grand arc of packaging just because some tool doesn't do the right thing by preferring the more accurate value if it is present.
Activity
sigmavirus24 commentedon Aug 26, 2026
Personally I wouldn't do this yet given how widely certifi is used.
See also psf/requests#7610 for discussion of why requests isn't pursuing a fix
alex commentedon Aug 28, 2026
I'm pretty apathetic, but would merge a PR removing the classifier in favor of hte proper license metadata.
sigmavirus24 commentedon Aug 28, 2026
It's a bit early to drop the prior best practice for one only standardized relatively recently in the grand arc of packaging just because some tool doesn't do the right thing by preferring the more accurate value if it is present.