-
-
Notifications
You must be signed in to change notification settings - Fork 29
PLEASE READ THE FOLLOWING WHOLE DESCRIPTION FIRST
caused by https://owasp.slack.com/archives/C6R3R32H4/p1667674523556749
caused by CycloneDX/cyclonedx-node-npm#233
NodeJS's module system is file-system based. It works regardless of package dependencies,
When code in module "foo" tries to use/require/access code from a different module "bar", then node will look in "foo";s own/direct "node_module" folder (depth 1). if it did not find any "bar" there, then node traverses all folders upwards and does the same lookup there, until it finds any "bar".
Lets see the following simple file trees
-
my-app |- node_modules |- foo |- bar -
my-app |- node_modules |- foo |- node_modules |- bar -
my-app |- node_modules |- bar |- node_modules |- foo
what about a situation where "bar" is installed multiple times?
-
my-app |- node_modules |- bar |- foo |- node_modules |- bar
This is the problem to be solved: how can this "bar" be de-duplicated in the SBOM?
is it possible at all? lets discuss and evaluate via CycloneDX/cyclonedx-node-npm#307
List view
0 of 3 selected 0 issues of 3 selected
DOCS: describe how component de-duplication works
documentationImprovements or additions to documentationImprovements or additions to documentationhelp wantedExtra attention is neededExtra attention is neededStatus: Open.#304 In CycloneDX/cyclonedx-node-npm;FEAT: component de-duplication
enhancementNew feature or requestNew feature or requestquestionFurther information is requestedFurther information is requestedStatus: Open.#306 In CycloneDX/cyclonedx-node-npm;feat: artificial package deduplication
enhancementNew feature or requestNew feature or requestStatus: Draft (not ready).CycloneDX/cyclonedx-node-npmnumber 309#309 In CycloneDX/cyclonedx-node-npm;