Add licence string normalization logic
Open
enhancement
needs-discussion
- Dominant language
- Go
- Stars
- 183
- Forks
- 18
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 7
Description
**What would you like to be added**:
Eg my image has jars or packages which have licences like
**Why is this needed**:
Can we normalize these to known supported licences
eg **The Apache Software License, Version 2.0** is same as **Apache-2.0**
**Additional context**:
Contributor guide
Research direction
The issue does not name files, tests, or an entry point. Start by locating where grant parses and compares license names, then review how supported licenses are represented; done means equivalent names such as “The Apache Software License, Version 2.0” resolve to the canonical Apache-2.0 identifier and the behavior is covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100