Dennis Clark

perhaps one more: **sctk_version** the version of ScanCode Toolkit used to scan the package.

looks like a new license to me -- analysis in progress

@AyanSinhaMahapatra please create the following license and associated rules: key: nxlog-public-license-1.0 name: NXLOG Public License v1.0 short-name: NXLOG Public License v1.0 owner: NXLOG category: Source-available SPDX: LicenseRef-scancode-nxlog-public-license-1.0 homepage: https://nxlog.co/nxlog-public-license Notes:...

Additional ideas to improve the integration between ScanCode.io and DejaCode: - [ ] A ScanCode.io user should be able to annotate scan results and save them as ABOUT files. Cases...

almost there -- needs one more review

See this for an example of the data (note problems with vague version range): https://github.com/cloudsecurityalliance/gsd-database/commit/a03afb806f7ce38b8d4db2b8709799db26b93e78

we also do not know how the data was gathered, especially the criteria for selection.

@AyanSinhaMahapatra please create this new license and make the associated adjustments to the rules (see comments above). Note that we already have another license, punycode, from owner nicemice. key: cexcept-2008...

I think this clause makes it a Source-available license (even though 100,000 is a really high number): 5. Commercial use of the software is limited to 100.000 (one hundred thousand)...

Hi @AyanSinhaMahapatra This is basically a license detection problem, since we have this license at https://scancode-licensedb.aboutcode.org/avsystem-5-clause.html Please investigate the detection rules.