Meterian
  • Meterian
    • The Platform
    • SSO and MFA
    • Support
  • Codebase scanner
    • The Thin Client
      • How does the client work?
      • How does the client authenticate me?
      • How do I get the client?
      • What if I need a previous release?
      • Use the thin client on Windows
    • Using the client from your command line
      • Authorization in interactive mode
      • Interrupting the client
      • Example: running the client in interactive mode
    • Using the client in your CI/CD pipeline
      • Authorization in non-interactive mode
      • Providing the project branch
      • Concurrent mode
      • Two phases build
      • Controlling the exit code
      • Example: running the client in non-interactive mode
    • General operations
      • Running the analysis remotely
      • Interrupting the client
      • Generating a report
      • Forcing or avoiding specific scans
      • Excluding (and including) specific folders
      • Connecting through a proxy
    • System requirements
    • Command line parameters
      • General configuration
      • Overriding scores
      • Overriding scopes
      • Producing reports
      • Selecting scanners
      • Defining projects
      • Advanced options
        • Autofix
        • Pull Requests
      • System information
      • Specific controls
        • Maven specific controls
        • Dotnet specific controls
        • Npm/Yarn specific controls
        • Gradle specific controls
        • Ant/Ivy specific controls
    • The Dockerized Client
      • Basic usage
      • Advanced usage
        • Invoking via Docker
        • Platform-specific images
        • Usage on a CI/CD platform
        • Disable the client auto-update
      • Troubleshooting
        • Client auto update failure
        • Docker specifics
    • How scores work
    • Guide: your first scan!
      • Your first scan (java thin client)
      • Your first scan (dockerized client)
      • Your first scan (GitHub Action)
  • Scan behaviour matrix
  • THE METERIAN DASHBOARD
    • The Web Dashboard
      • Projects
      • Insights
      • Tokens
      • Badges
      • Policies
      • Tags
      • Teams
      • Configuration
        • Automatic Temporary Branches Clean-up
    • Advanced functionalities
      • Multi-factor Authentication
      • Safe versions
      • Software Bill Of Materials (SBOM)
      • Auto-grouping
        • Domain auto-grouping
        • Github auto-grouping
      • How to set a vulnerability exclusion
        • From the report page
        • From the dashboard
        • The .meterian file
        • Generate the .meterian file
    • Troubleshooting
      • Login with credentials
  • Notifications
    • Sentinel
      • Notifications for Slack
      • Notifications for Email
    • Allerta
  • Github Badges
    • Introduction
    • Public repository
    • Private repository
  • ONLINE INTEGRATIONS
    • Introduction
    • GitHub Action
      • Using the Thin Client
      • Code scanning
    • Bitbucket Pipe
    • Azure DevOps Pipelines
  • Languages support
    • Introduction
    • C/C++
    • Clojure
    • Dart / Flutter
    • Elixir (erlang)
    • Golang
    • Java/Kotlin/Scala
      • Scanning EAR or WAR files
    • Javascript
    • .NET
      • Scanning DLLs
    • NodeJS
    • Perl
    • PHP
    • Python
    • R
    • Ruby
    • Rust
    • Swift / Objective-C
    • Generic (third party)
  • Special platfoms
  • Unity Packages
  • Jupyter Notebooks
    • License detection
  • Yocto license manifests
  • Container scanner
    • Container Scanner
      • Introduction
      • General usage
      • Command line parameters
        • General configuration
        • Overriding scores
        • Producing reports
        • Defining projects
        • Advanced Options
        • System information
      • How to set a vulnerability exclusion
  • IaC SCANNER
    • Introduction
    • General usage
    • Command line parameters
      • Producing reports
      • Defining projects
    • Policy management page
    • How to set a vulnerability exclusion
  • CI INTEGRATIONS
    • Introduction
    • AWS CodeBuild
    • Azure DevOps
      • Using the Docker image
      • Using the Java Thin client
    • Bamboo
    • Bitrise
    • CircleCI
    • CodeShip
    • Concourse CI
    • Generic CI
    • GitLab CI/CD
      • Docker-in-Docker configuration
      • Meterian Docker image configuration
      • Non-Meterian Docker image configuration
    • Jenkins
      • Pipeline
    • TeamCity
    • TravisCI
  • DevOps Integrations
    • GitLab Ultimate
    • SonarQube
      • Compatibility
      • Download and installation
      • Plugin properties
      • Usage
      • Report page
  • Management Platforms
    • Threadfix
    • DefectDojo
      • Uploading from a CI
    • Armorcode
    • Jira
  • Dedicated Instance
    • Introduction
    • On Cloud (MC/CC)
    • On Premises (OP)
      • Requirements and install
      • Managing the system
        • Admin dashboard
        • Managing your license
        • Managing accounts
    • Using the scanners
      • Thin client
      • Dockerized client
      • Container Scanner
      • IaC Scanner
  • Meterian API
  • API basics
  • Authorizing the APIs
  • Account APIs
    • Knowing your account
    • Listing your projects
  • Samples
  • Guides
    • Managing teams and members
    • Generating reports via APIs
Powered by GitBook
On this page

Was this helpful?

  1. Codebase scanner
  2. Command line parameters

Selecting scanners

Parameters used to enable or disable scanners

PreviousProducing reportsNextDefining projects

Last updated 2 years ago

Was this helpful?

The client will generally automatically detect manifest files and select/activate scanners accordingly. However some scanners are not enabled by default and, sometimes, it may be preferable to run separate analysis with different scanners enabled in order to get different reports. These parameters provide the control required.

--scan-java Controls if the Java scanner is run Default: Will run if a compatible manifest is present (see the for further information) Example: --scan-java=false (to disable it)

--scan-nodejs Controls if the NodeJS scanner is run Default: Will run if a compatible manifest is present (see the for further information) Example: --scan-nodejs=false (to disable it)

--scan-dotnet Controls if the .NET scanner is run Default: Will run if a compatible manifest is present (see the for further information) Example: --scan-dotnet=false (to disable it)

--scan-javascript Controls if the Vanilla Javascript scanner is run Default: Due to the fact that this scanner will potentially need to analyse any single file in the codebase, recursively, it will NOT run unless requested. (see the for further information) Example: --scan-javascript=true (to enable it)

--scan-ruby Controls if the Ruby scanner is run Default: Will run if a compatible manifest is present (see the for further information) Example: --scan-ruby=false (to disable it)

--scan-rust Controls if the Rust scanner is run Default: Will run if a compatible manifest is present (see the for further information) Example: --scan-rust=false (to disable it)

--scan-elixir Controls if the Elixir scanner is run Default: Will run if a compatible manifest is present (see the for further information) Example: --scan-elixir=false (to disable it)

--scan-scala Controls if the Scala scanner is run Default: Will run if a compatible manifest is present (see the the for further information) Example: --scan-scala=false (to disable it)

--scan-python Controls if the Python scanner is run Default: Will run if a compatible manifest is present (see the for further information) Example: --scan-python=false (to disable it)

--scan-perl Controls if the Perl scanner is run Default: Will run if a compatible manifest is present (see the for further information) Example: --scan-perl=false (to disable it)

--scan-golang Controls if the Golang scanner is run Default: Will run if a compatible manifest is present (see the for further information) Example: --scan-golang=false (to disable it)

--scan-cpp Controls if the C/C++ scanner is run Default: Will run if a compatible manifest is present (see the for further information) Example: --scan-cpp=false (to disable it)

--scan-r Controls if the R scanner is run Default: Will run if a compatible manifest is present (see the for further information) Example: --scan-r=false (to disable it)

--scan-unity Controls if the Unity/.NET scanner is run Default: Due to the fact that the manifest files used by the Unity Package Manager are very similar to the ones used by other package managers, it will NOT run unless requested. (see the for further information) Example: --scan-unity=true (to enable it)

--enabled-scanners Allows to activate only certain scanners by specifying a list of languages. Default: All scanners will be active during an analysis. It can be used in conjunction with the other options detailed here. Example: --enabled-scanners=swift,ruby,java (enables only swift, ruby and java)

specific section
specific section
specific section
specific section
specific section
specific section
specific section
specific section
specific section
specific section
specific section
specific section
specific section
specific section