apache / apache/polaris

Detect license and notice issues in GitHub CI

Open
#4,186 4 comments 0 reactions 0 assignees View on GitHub
enhancement stale
Dominant language
Java
Stars
2.1k
Forks
522
Avg merge
1d 22h
Merged PRs (30d)
137

Description

### Is your feature request related to a problem? Please describe.

License and notice issues in bundled artifacts can slip through until late review, risking incorrect LICENSE or NOTICE files in releases.

### Describe the solution you'd like

Add a GitHub CI check to validate license and notice files for built artifacts.

The check should fail when:
- required files(e.g., License, notice) are missing
- bundle license or notice content is incorrect or outdated
- dependencies are missing or stale in the bundle files

### Describe alternatives you've considered

_No response_

### Additional context

_No response_

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the repository's GitHub CI workflows and the process that produces built artifacts, then identify where LICENSE, NOTICE, and dependency bundle files are assembled. Define checks for missing, incorrect, outdated, or stale contents, and add CI coverage for each failure case. Done means the workflow reliably rejects invalid bundles and passes for valid artifacts.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions
Domain
build-system, ci-cd
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.