Dennis Clark

perhaps this new field belongs on the package model

better yet, let's call it license-expression-category

I think it's important to clarify that the scope of this improvement is limited to "license WITH exception" cases and not more complex license expressions that express multiple licenses connected...

This is an odd case. The text at https://chillicream.com/licensing/chillicream-license states that "This is the license we use for our proprietary software like Banana Cake Pop." but the license text itself...

@AyanSinhaMahapatra please create this new license and associated rules: key: chillicream-1.0 name: ChilliCream License 1.0 shortname: ChilliCream License 1.0 category: Copyleft Limited owner: ChilliCream spdx: LicenseRef-scancode-chillicream-1.0 homepage URL: https://chillicream.com/licensing/chillicream-license other...

Hi @swastkk we cannot play your video in the format you provided. Please feel free to submit a PR for this, and thanks in advance!

@AyanSinhaMahapatra @pombredanne we should restate the license line in question as 3. Neither the name of the copyright holder nor the names of its

Note that we already have https://scancode-licensedb.aboutcode.org/rsalv2.html Redis changed the license text on 2023-12-30 without bumping up the license version number. We just need to update the license text.

we will need to add rules for the various older versions

Two new fields, I think: **pkg_origin** list of values. The database or process that identified the package. * code-scan * purlDB match * d2d-map * dependency * about-file **is_scanned** yes/no/unknown...