Normalize VCS URL vs. repository

aboutcode-org / scancode-toolkit

:mag: ScanCode detects licenses, copyrights, dependencies by "scanning code" ... to discover and inventory open source and third-party packages used in your code. Sponsored by NLnet project https://nlnet.nl/project/vulnerabilitydatabase, the Google Summer of Code, Azure credits, nexB and others generous sponsors!

https://github.com/aboutcode-org/scancode-toolkit/releases/

2.1k stars 544 forks source link

Normalize VCS URL vs. repository #1226

Closed pombredanne closed 5 years ago

pombredanne commented 5 years ago

Today we are getting things as they come from package manifest. It would be best to normalize this to have uniform URLs there

sschuberth commented 5 years ago

FYI, in case we want to align on how VCS URL normalization is done, this is what we do currently in ORT: https://github.com/heremaps/oss-review-toolkit/blob/ff0645eb1e8774801b6d93bf5c8a4456aacf9410/utils/src/main/kotlin/Utils.kt#L197.

pombredanne commented 5 years ago

Done. and merged.