Skip to content
| Marketplace
Sign in
Visual Studio Code>Linters>SpotBugsNew to Visual Studio Code? Get it now.
SpotBugs

SpotBugs

JIHUNKIM

|
1,666 installs
| (1) | Free
Visual Studio Code extension for SpotBugs
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

⚠️ This extension is under active development. Frequent changes and updates are expected.

VS Marketplace Version last-commit VS Marketplace Downloads

SpotBugs for VS Code

Analyze Java code with SpotBugs directly in VS Code. View findings in a dedicated tree view, jump to offending lines, and track issues with VS Code diagnostics.

SpotBugs demo

Features

  • Analyze a single file or an entire workspace (Maven/Gradle projects)
  • Group findings by category and pattern with severity icons
  • Navigate to bug locations in source files with matching diagnostics/squiggles
  • Export filtered findings to SARIF for code scanning tools

Requirements

  • Java 11 or later (JDK)
  • VS Code extension: “Language Support for Java by Red Hat” (redhat.java)

Getting Started

  1. Open a Java project folder in VS Code
  2. Run a command:
    • “SpotBugs: Analyze this workspace” (spotbugs.runWorkspace)
    • “SpotBugs: Analyze File/Folder” (context menu, spotbugs.run)
  3. Review results in the “SpotBugs” view (Activity Bar)

Commands

  • SpotBugs: Analyze File/Folder — Analyze selected file or folder
  • SpotBugs: Analyze this workspace — Build then analyze all projects in the workspace
  • SpotBugs: Export SpotBugs Findings (SARIF) — Save current findings to a SARIF report
  • SpotBugs: Reset SpotBugs Results — Clear the SpotBugs view and diagnostics

Settings

Analysis

  • spotbugs.analysis.effort: SpotBugs effort level (min, default, max). Default: default.
  • spotbugs.analysis.priorityThreshold: Report bugs with rank less than or equal to this value (1 = most severe, 20 = least). Default: 9.
  • spotbugs.analysis.extraAuxClasspaths: Additional SpotBugs aux classpath entries appended after Java LS runtime classpath entries. Supports absolute and workspace-relative jar/directory paths.

Source target resolution stays separate from aux classpath configuration. SpotBugs uses Java LS runtime classpaths plus any extraAuxClasspaths entries for aux analysis, and falls back to the runner's system classpath only when neither source provides any entries.

Filters

  • spotbugs.filters.includePaths: SpotBugs XML include filter paths (-include). Supports absolute and workspace-relative paths.
  • spotbugs.filters.excludePaths: SpotBugs XML exclude filter paths (-exclude). Supports absolute and workspace-relative paths.
  • spotbugs.filters.excludeBaselineBugsPaths: SpotBugs XML baseline bug collection paths (-excludeBugs). Supports absolute and workspace-relative paths.

If any configured filter file is invalid, analysis stops immediately and an error is shown with a code.

  • CFG_FILTER_NOT_FOUND
  • CFG_FILTER_NOT_FILE
  • CFG_FILTER_UNREADABLE
  • CFG_FILTER_XML_INVALID
  • CFG_BASELINE_XML_INVALID
  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
© 2026 Microsoft