Skip to content

Provide option to reference a specific DejaCode dataspace in scan results #280

Description

@DennisClark

The scan process currently builds an output that contains a constructed URL to the nexB "Demo" dataspace; that works fine, and when a user clicks on that URL, the Demo version of the nexB license in the License Library is presented. However, the benefit of that is somewhat limited if the scancode user has a subscription to DejaCode, in which case it would be best if that user can tell the scanning process which dataspace to use when constructing a DejaCode license URL.

Also, even more beneficial would be the ability for the scancode user to provide an API Key to a specific dataspace, and for scancode to return the Usage Policy set for that license in the dataspace associated with the API. Doing that would provide extremely useful information directly to the scancode user, providing a logical way to sort and filter the results to find the files/packages with a license that requires Review by someone in the scancode user's organization (or requires some other action). By doing something like this, the user can focus immediately on the problem items, or at least those that require some kind of action.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions