spdx

It would be ideal to be able to identify and catalog Nix packages.

Description

A brief description of the Documentation Improvement or New Section request.

The Section "Performing Extraction" from the tutorial page "How to run a scan" mentions a Note:
"--shallow option can be used to recursively extract packages"

I think the lines in the following documentation are somehow not in correct order. Maybe chunks were added between multi line statements. Especially import_str: is broken.

https://github.com/tern-tools/tern/blob/a3e76cdb0e08d92e896822634cbcf670bdd05e30/tern/classes/image_layer.py#L18-L43

Description

The /info API returns the fossslogy version as unknown when the sever is running from docker.

![image](https://user-images.githubusercontent.com/63705023/161546

CommentStyle.MULTI_LINE is currently a three-part tuple. It should instead be a NamedTuple so that the code can access named properties instead of magical index numbers.

An authors file is needed to list and thank people who have contributed to the project.

The CLI tool should support automatic resolving and augmentation of license information, when it is missing, for components in an SBOM.

For components with an external reference to a GitHub repo it should be possible, in a lot of cases, to automatically resolve license information using the API.

This is already supported in the .NET implementation (https://github.com/CycloneDX/cyclonedx-dotn

Currently we have some parts where we fetch data from external APIs with fetch. In opossum-tool/OpossumUI#472 we started using axios (mostly because it handles error codes for you).

Known usages of fetch:

• useFetchPackageInfo

Do a search to find any other occurrences. Also look at opossum-tool/OpossumUI#472 to see how requests can be mo