Skip to content

Inconsistent licenses detected by GitHub Dependency Graph #5207

@scordio

Description

@scordio

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-engine and junit-platform-testkit are reported as NOASSERTION
  • junit-jupiter-params and junit-platform-engine are reported as MIT 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.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions