Code Analyzer Command Reference (Retired)

This command reference contains information about Salesforce Code Analyzer commands and their flags.

To scan your code and output any violations found to a results file, run:

• sf scanner run --target somefile.js --outfile results.html

• somefile.js: The source code location.
• results.html: The output format.

To scan your code with a specific engine, run

• sf scanner run --target /some/dir --engine cpd

• /some/dir: The source code location.
• cpd: The engine or engines to run.

To continuously improve your code, integrate Code Analyzer results into your CI/CD tool. Your tool can interpret those violations and act on them.

To scan your code with Graph Engine data-flow analysis, run:

• sf scanner run dfa --target ./myproject/main/default/classes/*.cls --projectdir ./myproject/

• ./myproject/main/default/classes/*.cls: The source code location.
• ./myproject/: The root project directory.

j

Get Started

Overview of Salesforce Code Analyzer

Engines

Use CLI Commands to Analyze Your Code

Use the VS Code Extension to Analyze Your Code

Use Salesforce Agent Skills to Analyze Code in Natural Language

Use MCP Tools to Analyze Your Code

Create Custom PMD Rule Using MCP Tools

Suppress Violations

Customize the Configuration

CLI Command Reference

Output Schema Reference

CI/CD Integration

Migrate from v4 to v5

Produce Code Analyzer Reports for AppExchange Security Review

Release Notes

Salesforce Code Analyzer v4 (Retired)

Architecture (Retired)

Engines (Retired)

Use CLI Commands to Analyze Your Code (Retired)

Use the VS Code Extension to Analyze Your Code (Retired)

CI/CD Integration (Retired)

Command Reference (Retired)

scanner run (Retired)

scanner run dfa (Retired)

scanner rule list (Retired)

scanner rule describe (Retired)

scanner rule add (Retired)

scanner rule remove (Retired)

Customization (Retired)

Code Analyzer FAQ (Retired)

Troubleshooting (Retired)