azure-pipelines: Ignore .vscode-test directory in CG scans #1824
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
bwateratmsft
changed the title
bwateratmsft
commented
Nov 25, 2024
| @@ -47,6 +47,8 @@ extends: | |||
| sdl: | |||
| credscan: | |||
| suppressionsFile: $(Build.SourcesDirectory)\.azure-pipelines\compliance\CredScanSuppressions.json | |||
| componentgovernance: | |||
| ignoreDirectories: $(Build.SourcesDirectory)\**\.vscode-test | |||
There was a problem hiding this comment.
I don't know if this **\ syntax will work. If not, we will have to explicitly exclude all of the packages' .vscode-test directories.
alexweininger
approved these changes
Nov 25, 2024
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.
We're getting a large number of component governance alerts because certain VSCode built-in extensions (
handlebars,npm,json, etc.) have the same package names as NPM packages. The alerts are false on multiple levels--firstly, they're in.vscode-testwhich should not be scanned, and secondly, they aren't the actual NPM packages--just the package name and version matches a vulnerable NPM package.This should suppress those CG alerts.