dx-code-analyzer-run

To scan Salesforce Apex code for security and vulnerability violations, run static analysis engines like PMD and SFGE against your workspace, folders, or git diffs to generate timestamped result files. You can then filter and summarize findings.

Yes, you can run ESLint and static analysis on Lightning Web Components (LWC) and JavaScript static resources. The scanner evaluates LWC files for best-practice, performance, and security violations using targeted rule selectors.

The best way to fix Apex static analysis violations is to apply deterministic engine-provided fixes after reviewing rule explanations and confirming the changes. The scanner identifies violations and applies safe auto-fixes with post-scan validation.

Yes, Salesforce static analysis supports Flow and Visualforce files for best-practice checks. The scanner applies Flow and Visualforce engines to detect duplication, performance, and vulnerability violations across your project paths.

You can filter Salesforce code quality findings by severity, engine, category, file, or rule without rescanning the workspace. The scanner performs post-scan filtering on the timestamped result files to rank and summarize existing findings.

Code Analyzer rule selectors are used for Salesforce code quality scans to target specific engines and rule sets across Apex, LWC, and Flow. They enable deterministic scanning, precise rule lookup, and structured violation summaries for AppExchange preparation.