| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
The @vscode/test-electron package downloads VS Code Insiders binaries into .vscode-test/ at test time for extension integration tests. This directory is already in .gitignore but is present on disk when the OneBranch async SDL scanner runs after 'Invoke-Build Test'. The CodeQL SM04514 'Weak hashes' alert (S360/ADO #35101062) fires against VS Code's own cliProcessMain.js inside this directory — code that the PowerShell team has no ownership of or ability to fix. Adding ob_sdl_codeql_pathsToExclude prevents future false-positive alerts from third-party VS Code binary artifacts. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Clarified comment regarding exclusion of VS Code test binaries from CodeQL scans.
|
Travis Plunk (@TravisEz13) the OneBranch team promised months ago that they would exlcude that folder by default, since it's not us it's the VS Code team's test package. I'll take this, but it is frustrating they didn't follow through. |
Sorry, something went wrong.
There was a problem hiding this comment.
Updates the OneBranch pipeline configuration to prevent CodeQL from scanning the locally-downloaded VS Code Insiders test binaries under .vscode-test/, avoiding an SDL false-positive.
Changes:
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Summary
This pull request makes a small update to the pipeline configuration to improve security scan accuracy. It excludes the .vscode-test/ directory—where VS Code Insiders binaries are downloaded for testing—from CodeQL scans, preventing false positives and unnecessary scan noise.
Root Cause
The @vscode/test-electron\ package downloads VS Code Insiders binaries into .vscode-test/\ when \Invoke-Build Test\ runs during the OneBranch pipeline. The directory is already in .gitignore\ but is present on disk when the async SDL/CodeQL scanner runs after the test step.
The CodeQL SM04514 'Weak hashes' alert fires against \cliProcessMain.js\ inside .vscode-test/vscode-win32-x64-archive-insiders/resources/app/out/vs/code/node/\ — this is VS Code's own bundled JavaScript, not PowerShell code. The PowerShell team has no ownership of or ability to fix hash usage inside VS Code's CLI runtime.
Fix
Adds \ob_sdl_codeql_pathsToExclude: .vscode-test/**\ to the OneBranch job variables, preventing the CodeQL scanner from analyzing downloaded VS Code test binaries.
Why this is safe