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

Command line parameters

--help Displays a brief help page and exits (with code 0), like shown here: (please note that this is an example, your output may be different)

Meterian Client v1.2.24.4, build 13c1adb-730
© 2017-2022 Meterian Ltd - All rights reserved

 --tpn			Displays the third party notice for this application and exits(0)
 --help			Displays this help and exits(0)
 --clean		Cleans any previous build information on the client
 --folder		The root folder of the project (default: current folder) (example: --folder=/path/to/project)
 --local		Runs this build using the local build system (default: --local=true)
 --interactive		Allows the client to use the browser for interactive authentication (default: --interactive=true)
 --start-only		Uses two-phase build, start remotely and exit (default: --start-only=false)
 --auth-file		Uses an authorisation file (example: --auth-file=~/ci.json)
 --min-security		Specifies the minimum security level to pass the build (default: --min-security=90 or as set in the account)
 --min-stability	Specifies the minimum stability level to pass the build (default: --min-stability=80 or as set in the account)
 --min-licensing	Specifies the minimum licensing level to pass the build (default: --min-licensing=95 or as set in the account)
 --report-file		Produces an HTML report file (example: --report-file=~/report.html)
 --report-json		Produces an JSON report file (example: --report-json=~/report.json)
 --report-junit		Produces a JUNIT XML report file (example: --report-junit=~/report.xml)
 --report-pdf		Produces an PDF report file (example: --report-pdf=~/report.pdf)
 --report-threadfix	Produces an Threadfix-compatible report file (example: --report-threadfix=~/report.threadfix)
 --report-sbom		Produces a Software Bill Of Meterials report file, format can be specified (see the doc)  (example: --report-sbom=~/sbom.csv)
 --report-console	Ouputs the scan report on the console (default: color if not specified - options color|nocolor|security|stability|licensing
 --project-url		Specifies project url, if you are not using git (example: --project-url=https://svn.theforge.com/hubba/logos)
 --project-branch	Specifies project branch, if you are not using git (example: --project-branch=master)
 --project-commit	Specifies project commit, if you are not using git (example: --project-commit=9460cabbf623945495e6108c9d1979a9e7b5d8e7)
 --project-key		Specifies project to associate this analysys to (example: --project-key=f6239454)
 --project-tags		Allows to add a set of user defined Meterian tags (comme separated) to the project (example: --project-tags=production,platform)
 --concurrent-mode	Enables concurrent mode (default: --concurrent-mode=true)
 --scan-java		Forces java scan (default: will run if java code present)
 --scan-nodejs		Forces nodejs scan (default: will run if nodejs code present)
 --scan-dotnet		Forces dotnet scan (default: will run if dotnet code present)
 --scan-javascript	Forces javascript scan (true:false:maybe) (default: won't run)
 --scan-ruby		Forces ruby scan (default: will run if ruby code present)
 --scan-rust		Forces rust scan (default: will run if rust code present)
 --scan-elixir		Forces elixir scan (default: will run if rust code present)
 --scan-scala		Forces scala scan (default: will run if scala code present)
 --scan-python		Forces python scan (default: will run if python code present)
 --scan-perl		Forces perl scan (default: will run if perl manifests present)
 --scan-golang		Forces golang scan (default: will run if go manifests present)
 --scan-unity		Forces scan of unity packages (true:false) (default: won't run)
 --scan-cpp		Forces scan of C/CPP packages via conan (true:false) (default: will run if conan manifests are present)
 --scan-r		Forces R scan (true:false) (default: will run if renv manifests present)
 --autofix		Automatically fixes dependencies versions (see the online documentation)
 --dump			Dumps the requested report on the console (example: --dump=dependencies)
 --process-notebooks	Enables processing of (python only) jupyter notebooks
 --fail-gracefully	The system will fail gracefully in case of network errors
 --exclude-folders	Allow to excludes folder from analysis, where applicable (example: **/*.samples,**/*.labs)--exclude-folders=)
 --exclude-roots	Allow to exclude root dependencies of choice from the analysis (example: --exclude-roots=app,lib)

For any furher information please refer to the online documentation at docs.meterian.io

Meterian servers are reachable from this system

Please refer to the following subsections for further information.

PreviousSystem requirementsNextGeneral configuration

Last updated 4 months ago

Was this helpful?

It will also check that the connectivity with the Meterian cloud servers is in place: this is useful in case you want to validate your or you fear a corporate firewall is interfering.

proxy configuration