bazelbuild / bazelbuild/rules_license

Populate third party license meta data

Open
#110 2 comments 0 reactions 0 assignees View on GitHub
enhancement P3
Dominant language
Starlark
Stars
85
Forks
37
PR merge metrics
No merged PRs in 30d

Description

Is it possible to extend the aspect such that third party license information would be automatically populated?

For example [`pip_parse`](https://github.com/bazelbuild/rules_python#using-a-workspace-file-1) should expose the Python license meta information ([`setup.py license=`](https://packaging.python.org/en/latest/guides/distributing-packages-using-setuptools/#license), [`pyproject.toml license=](https://python-poetry.org/docs/pyproject/#license), [`License ::` classifier](https://pypi.org/classifiers/)).

Contributor guide

Open the contributing guide

Research direction

Start by tracing how pip_parse exposes package metadata, then compare the license sources named in setup.py, pyproject.toml, and the PyPI License classifier. Define how the aspect should expose that information and how completion would be verified across these metadata formats.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
build-system
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.