aboutcode-org / aboutcode-org/scancode-toolkit

NuGet: add support for extra manifests

Open
#1,584 1 comment 0 reactions 0 assignees View on GitHub
new feature package scan package-formats
Dominant language
Python
Stars
2.6k
Forks
791
Avg merge
1d 12h
Merged PRs (30d)
5

Description

### Description
Beyond the base `.nuspec` manifest file there are several other files we should detect and report:

- `packages-config`: See https://docs.microsoft.com/en-us/nuget/reference/packages-config

This is an XML file and it mostly lists the dependencies of a project. This is a "legacy" format
It is somewhat related to the packages.lock.json too.
```xml


```

- `project.json` and `project.lock.json` See https://docs.microsoft.com/en-us/nuget/archive/project-json

This is a JSON file and mostly list dependencies though it can store some extra attributes . This is a "legacy" NuGet 3.x+ format. The lock file is also JSON.

```json
"dependencies": {
"Microsoft.NETCore": "5.0.0",
"System.Runtime.Serialization.Primitives": "4.0.10"
}
```

- `PackageReference` See https://docs.microsoft.com/en-us/nuget/consume-packages/package-references-in-project-files (therefore is XML)

It stores NuGet dependencies in the VS projects files directly under a PackageReference node.

```xml



```

Notes: Projects that use PackageReference do not use packages.config.

See also #648

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.