Determine license expression for ruby-advisory-db

[sbs2001]

Please check https://github.com/rubysec/ruby-advisory-db/blob/master/LICENSE.txt .

Determine and enable the detection of correct license expression for the above LICENSE.

[pombredanne]

Thanks! I reckon that would be something you want to use for VulnerableCode, correct?

[sbs2001]

@pombredanne yes

[pombredanne]

@DennisClark what would be your take there?

[pombredanne]

This is for aboutcode-org/vulnerablecode#63

[DennisClark]

The correct expression to derive from the text at https://github.com/rubysec/ruby-advisory-db/blob/master/LICENSE.txt should be:
LicenseRef-scancode-generic-cla AND LicenseRef-scancode-public-domain AND LicenseRef-scancode-osvdb AND LicenseRef-scancode-warranty-disclaimer

but scancode-toolkit-v32.3.3 reports
LicenseRef-scancode-generic-cla AND LicenseRef-scancode-public-domain AND LicenseRef-scancode-proprietary-license AND LicenseRef-scancode-warranty-disclaimer

all of which are available at https://scancode-licensedb.aboutcode.org/

Note that the LICENSE.txt in question points to a bad URL which gets stuck in my browser. The date of the LICENSE.txt in question is June 21, 2021.

Also note the following Reference Notes from DejaCode regarding LicenseRef-scancode-osvdb :

There is lingering old data in the Rubysec advisory database that still uses this license. The name of the license is misleading, because it is not an open source license. See license text for the various restrictions.

@AyanSinhaMahapatra please create a detection rule for the text at https://github.com/rubysec/ruby-advisory-db/blob/master/LICENSE.txt to point to the license expression described above.

Given the obsolescence of this license notice, it is NOT a high priority.

[DennisClark]

LICENSE.txt
LICENSE.txt-results.json