Resolve basic-ftp security alert #3002
Open
Azure Pipelines / OfficeDev.microsoft-teams-library-js-PR (🔒 SDLSources SDL Sources Analysis (AppHostingSdk))
succeeded
Mar 23, 2026 in 4m 30s
🔒 SDLSources SDL Sources Analysis (AppHostingSdk) succeeded with issues
Annotations
Check failure on line 63 in Build log
azure-pipelines / OfficeDev.microsoft-teams-library-js-PR (🔒 SDLSources SDL Sources Analysis (AppHostingSdk))
Build log #L63
Error running eslint job: 1 of 1
Check failure on line 64 in Build log
azure-pipelines / OfficeDev.microsoft-teams-library-js-PR (🔒 SDLSources SDL Sources Analysis (AppHostingSdk))
Build log #L64
GuardianErrorExitCodeException: eslint completed with an Error exit code: 2. Linting was unsuccessful due to a configuration problem or an internal error. If you have enabled exit-on-fatal-error one or more of your files could possibly have a parsing error. Check the errors or the produced SARIF files to fix the parsing errors.
Check failure on line 67 in Build log
azure-pipelines / OfficeDev.microsoft-teams-library-js-PR (🔒 SDLSources SDL Sources Analysis (AppHostingSdk))
Build log #L67
Error running tool 1 of 1: eslint
Check failure on line 68 in Build log
azure-pipelines / OfficeDev.microsoft-teams-library-js-PR (🔒 SDLSources SDL Sources Analysis (AppHostingSdk))
Build log #L68
Error running eslint job: 1 of 1
Check failure on line 69 in Build log
azure-pipelines / OfficeDev.microsoft-teams-library-js-PR (🔒 SDLSources SDL Sources Analysis (AppHostingSdk))
Build log #L69
GuardianErrorExitCodeException: eslint completed with an Error exit code: 2. Linting was unsuccessful due to a configuration problem or an internal error. If you have enabled exit-on-fatal-error one or more of your files could possibly have a parsing error. Check the errors or the produced SARIF files to fix the parsing errors.
Loading