CLI Reference¶

polyscan exposes two commands. analyze accepts one or more paths, and every path may be a file or a directory.

Command	Purpose	Fails the build?
`analyze`	Run the full analysis and produce a report	No
`version`	Print version information	No

$ polyscan --help
polyscan is a static analyzer that measures code quality across languages.
It currently analyzes cyclomatic complexity and code clones for Go, Rust and C++.

Usage:
  polyscan [command]

Available Commands:
  analyze     Analyze source files
  completion  Generate the autocompletion script for the specified shell
  help        Help about any command
  version     Print version information

Flags:
  -h, --help      help for polyscan
  -v, --version   version for polyscan

Use "polyscan [command] --help" for more information about a command.

To fail a pipeline on the results, gate on the JSON output — there is no separate check command. The CI/CD page shows how. If you are looking for jscan's check, deps or init commands, see migrating from jscan.

Which files polyscan reads¶

analyze walks the directory tree and collects files by extension, dispatching each to its language:

Language	Extensions
JavaScript	`.js`, `.jsx`, `.mjs`, `.cjs`
TypeScript	`.ts`, `.tsx`, `.mts`, `.cts`
Go	`.go`
Rust	`.rs`
C++	`.cpp`, `.cc`, `.cxx`, `.hpp`, `.hh`, `.hxx`, `.h`, `.ipp`, `.inl`

Header files, .h included, are analyzed as C++.

The JavaScript/TypeScript collection additionally honors the project's configuration file and the .gitignore at the root of the analyzed path, exactly as jscan did. The other languages are collected by extension alone.