Extra "unknown" reported for some packages
Summary
For certain packages an "unknown" license is added even if all of a package's license have been correctly identified. So far only observed for maven
packages.
Example: `com.github.jsqlparser/jsqlparser`
{"name":"com.github.jsqlparser/jsqlparser","lowest_version":"0.9.4","highest_version":"4.8.0","default_licenses":["unknown","Apache-2.0","LGPL-2.1","LGPL-2.1+","LGPL-2.1-only","LGPL-2.1-or-later"],"other_licenses":[{"licenses":["unknown","LGPL-2.1","LGPL-2.1+","LGPL-2.1-only","LGPL-2.1-or-later"],"versions":["0.8.5","0.8.6","0.8.8","0.8.9","0.9","0.9.1","0.9.2","0.9.3"]}]}
Steps to reproduce
tbd
Example Project
tbd
What is the current bug behavior?
An unknown
license is shown for packages even though all licenses are correctly identified.
What is the expected correct behavior?
An unknown
license should not appear.
Relevant logs and/or screenshots
tbd
Possible fixes
This seems to be caused by the interfacer
sending out the identifier for the license plus its full name. Some of these full names are incorrectly mis-classified in the processor
and set as unknown
.
Implementation Plan
-
Add alias in the interfacer so that license strings match known licenses. -
Release on dev and prod -
Re-run respective feeder withSKIP_CURSOR
Edited by Nick Ilieskou