Skip to content

ClearlyDefined not using LicenseRef-scancode-chillicream-1.0 #4085

@ariel11

Description

@ariel11

Instead of using the correct LicenseRef-scancode-chillicream-1.0, ClearlyDefined is putting:

  • "Elastic-2.0 AND LicenseRef-scancode-unknown-license-reference," or
  • "Elastic-2.0 AND NOASSERTION."

Unfortunately, these are both wrong. This is not the Elastic-2.0 license, as a key license limitation is missing. The LICENSE file is a match for LicenseRef-scancode-chillicream-1.0.

image

I submitted a curation for v20.0.2, though had to first curate "OTHER" and then edit the yaml file, as the UI was not allowing me to curate a LicenseRef - clearlydefined/curated-data#29191. Will curation support for LicenseRefs be added?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions