-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Closed
Labels
Description
When looking at the jimfs-junit-jupiter dependency graph, which uses JUnit 6.0.1, I noticed that the licenses of the JUnit modules are inconsistent:
junit-jupiter-engineandjunit-platform-testkitare reported asNOASSERTIONjunit-jupiter-paramsandjunit-platform-engineare reported asMIT AND LicenseRef-scancode-unknown-license-reference AND EPL-2.0- The remaining modules don't have a license
The situation is slightly different when looking at the junit-converters dependency graph, which uses JUnit 5.14.1.
I don't know whether it's something JUnit could solve or a bug in the GitHub dependency graph/dependency submission. Nevertheless, I wanted to raise awareness, as consuming projects might rely on the SBOM that GitHub provides.