You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Aliases are certainly not the most common method of referencing packages, but since all transitive dependencies must be specified in the vuln-reach config, it seems like it is enough if one dependency in a project is specified via an alias to make vuln-reach not applicable.
When running vuln-reach-cli with this config, it fails
$ vuln-reach-cli ./vuln-reach-config.toml
Downloading @vue/test-utils-vue3-2.2.0 to ./tarballs/@vue/test-utils-vue3-2.2.0.tgz...
Downloading vue-loader-vue3-17.0.1 to ./tarballs/vue-loader-vue3-17.0.1.tgz...
Error: error decoding response body: missing field `versions` at line 1 column 21
Caused by:
missing field `versions` at line 1 column 21
Expected Behavior
vuln-reach can download packages that have been specified via an alias
Actual Behavior
vuln-reach fails to download packages referenced by an alias
The text was updated successfully, but these errors were encountered:
Description
Yarn and npm support specifying packages via aliases, see https://docs.npmjs.com/cli/v8/using-npm/package-spec#aliases. The config format of
vuln-reach-cli
does not have enough information to resolve such packages (see example below).Aliases are certainly not the most common method of referencing packages, but since all transitive dependencies must be specified in the vuln-reach config, it seems like it is enough if one dependency in a project is specified via an alias to make vuln-reach not applicable.
Here is an example:
Corresponding lockfile entry:
If we use phylum cli to parse the transitive packages, we get
from which we might create the following config
When running
vuln-reach-cli
with this config, it failsExpected Behavior
vuln-reach
can download packages that have been specified via an aliasActual Behavior
vuln-reach
fails to download packages referenced by an aliasThe text was updated successfully, but these errors were encountered: