-
any updates needed?
review for improvements on easier reading/understandability
-
Currently node-licked license issuing actively exploits `User's favorite expression`.
It is presisted as a String emf-property, without a format demands. The property's editor also does not restri…
-
To support #90, we should add the https://github.com/nexB/license-expression library to DeltaCode and update our algorithm to use this library.
-
LicenseFinder should be able to parse and validate [SPDX License Expressions](https://github.com/spdx/spdx-spec/blob/development/v2.3.1/chapters/SPDX-license-expressions.md), as they get more commonly…
-
**What happened**:
Sometimes syft can encounter a dpkg license where the regular expression used to match on contents cannot correctly identify the license.
In the following example we should find…
-
Hi, We have 4 dependency packages being upgraded which are using extensive Dual licensing. I have recently updated my config file to accommodate the flagged license identifiers as well. Still we are g…
-
If a package is released under the terms of two licenses the manual says
> Multiple licenses should be separated by commas, Example: `GPL-3.0-or-later, custom:Hugware`.
However, this does not ma…
-
Spun out from today's legal meeting, I think we should add ~~`UNLICENSED`~~ `NONE` to license expressions, because external tools like [npm's `package.json`][1] are currently defining `UNLICENSED` as …
wking updated
5 months ago
-
Like #49, but for `NOASSERTION` instead of `NONE`. The semantics would [be][1]:
> NOASSERTION means:
> (i) the SPDX License Expression author has attempted to but cannot reach a reasonable object…
wking updated
5 months ago
-
I am updating purldb to use the latest version of scancode-toolkit. In purldb, we create package objects using the Package class from packagedcode (https://github.com/nexB/purldb/blob/7bed64d12fa124bf…