riseproject-dev / riseproject-dev/python-wheels

Investigate adding a license checker for built wheels

Open
#167 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement infrastructure
Dominant language
Python
Stars
0
Forks
0
Avg merge
16h 14m
Merged PRs (30d)
952

Description

Right now, part of the wheel build review process has always involved downloading a built wheel, unpacking it, and inspecting it for:

  1. The project's LICENSE files and related data
  2. The presence of linked libraries included in the wheels as part of the final build process
  3. Any license compliance steps which needed to be taken based on the libraries found in step 2 (if any)

It would be very helpful to have this check automated along with everything else we've got running for every PR. However, while checking for the correct license according to the target project may be simple, having the workflow/script confirm that we aren't missing any supplemental licensing (or, possibly, that the wheels are actually failing to meet licensing requirements) is going to be more complicated.

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.

Research direction

Start by reviewing the existing workflow or script that builds wheels for every pull request, then inspect the built wheels for LICENSE files and bundled libraries. Define how supplemental licensing and compliance findings should be reported; the work is done when the automated check reliably identifies these cases during pull request builds.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
build-system, ci-cd
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.