l3montree-dev / l3montree-dev/devguard
Add License Risk exclusion on org level
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 161
- Forks
- 43
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 37
Description
Is your feature request related to a problem? Please describe.
Having internal dependencies, e.g. pkg:maven/de.myorg/shared-lib.jar which has no license / proprietary license creates hundreds of License Risks in the whole organization.
Describe the solution you'd like
Make it possible to define org or group-wide exclusion of license risk's without forcing me to click hundreds of times for every artifact and every version in every group.
Possible pattern, e.g.:
pkg:maven/de.myorg.*
Contributor guide
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.
Research direction
No files, tests, or entry points are named. Start by tracing how license risks and artifact-level exclusions are stored and applied, then determine how organization- or group-wide patterns should be represented and inherited. Done means a pattern such as pkg:maven/de.myorg.* excludes matching risks across the requested scope without per-artifact actions, with coverage for matching and non-matching dependencies.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend-api-design, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100