-
Notifications
You must be signed in to change notification settings - Fork 59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Third party dependencies contextual analysis for npm #941
Merged
EyalDelarea
merged 84 commits into
jfrog:dev
from
EyalDelarea:include_node_modules_applicabilities
Sep 13, 2023
Merged
Third party dependencies contextual analysis for npm #941
EyalDelarea
merged 84 commits into
jfrog:dev
from
EyalDelarea:include_node_modules_applicabilities
Sep 13, 2023
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sverdlov93
reviewed
Sep 13, 2023
EyalDelarea
had a problem deploying
to
frogbot
September 13, 2023 10:15 — with
GitHub Actions
Failure
EyalDelarea
had a problem deploying
to
frogbot
September 13, 2023 10:19 — with
GitHub Actions
Failure
EyalDelarea
had a problem deploying
to
frogbot
September 13, 2023 10:25 — with
GitHub Actions
Failure
…clude_node_modules_applicabilities
EyalDelarea
had a problem deploying
to
frogbot
September 13, 2023 10:26 — with
GitHub Actions
Failure
EyalDelarea
had a problem deploying
to
frogbot
September 13, 2023 10:28 — with
GitHub Actions
Failure
EyalDelarea
had a problem deploying
to
frogbot
September 13, 2023 11:30 — with
GitHub Actions
Failure
EyalDelarea
had a problem deploying
to
frogbot
September 13, 2023 11:41 — with
GitHub Actions
Failure
EyalDelarea
had a problem deploying
to
frogbot
September 13, 2023 11:44 — with
GitHub Actions
Failure
EyalDelarea
had a problem deploying
to
frogbot
September 13, 2023 13:54 — with
GitHub Actions
Failure
sverdlov93
reviewed
Sep 13, 2023
@@ -19,8 +19,12 @@ import ( | |||
"gopkg.in/yaml.v3" | |||
) | |||
|
|||
const ( | |||
NodeModulesPattern = "**/*node_modules*/**" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggested change
NodeModulesPattern = "**/*node_modules*/**" | |
nodeModulesPattern = "**/*node_modules*/**" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
been used from applicablitymanager.go so has to be public
sverdlov93
reviewed
Sep 13, 2023
EyalDelarea
had a problem deploying
to
frogbot
September 13, 2023 13:58 — with
GitHub Actions
Failure
EyalDelarea
had a problem deploying
to
frogbot
September 13, 2023 14:00 — with
GitHub Actions
Failure
EyalDelarea
changed the title
Third party contextual analysis for npm
Third party dependencies contextual analysis for npm
Sep 13, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When enabling the new flag of the CLI :
third-party-contextual-analysis
The applicability scanner will run on the environments folders as well. ( node_modules etc...)
In this case we will need to exclude the reported applicabilities which originated from the impacted source package.
For example:
protobufjs
CVE applicability was found:applicability location is inside node_modules/protobufjs -> disqualify
Other use case:
applicability location is inside node_modules/someOtherDep -> valid.