You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+16Lines changed: 16 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -150,6 +150,12 @@ according to your preferences.
150
150
-**Proxy Configuration** :
151
151
<br >From IntelliJ IDEA Appearance & Behavior > System Settings > HTTP Proxy, you can configure a static proxy for all HTTP requests made by the plugin. This is useful when your environment requires going through a proxy to access external services. For example:`http://proxy.example.com:8080`
152
152
153
+
-**Batch Analysis** :
154
+
<br >Configure settings for batch workspace analysis, which analyzes all packages in a JS/TS monorepo or Cargo workspace at once.
155
+
<br >**Concurrency**: Maximum number of concurrent analyses during batch workspace analysis (default: 10).
156
+
<br >**Continue on Error**: Continue analyzing remaining packages when one package analysis fails (default: enabled).
157
+
<br >**Include Metadata**: Include additional metadata in batch analysis results (default: enabled).
158
+
153
159
-**Manifest Exclusion Patterns** :
154
160
<br >You can exclude manifest files from component analysis using glob patterns. This is useful for excluding third-party dependencies, test files, or other manifests that should not be analyzed.
155
161
<br >Enter one pattern per line. Examples: `**/node_modules/**/package.json` to exclude all package.json files in node_modules directories, or `test/**/pom.xml` to exclude all Maven files in test directories.
@@ -396,6 +402,16 @@ When modifying the grammar or lexer files, you need to regenerate the parser cla
396
402
<br >Right-click on any manifest file and select **Exclude from Component Analysis** to quickly add an exclusion pattern for that specific file.
397
403
398
404
405
+
-**Batch Workspace Analysis**
406
+
<br >For JS/TS monorepos (npm, pnpm, yarn workspaces) and Cargo workspaces, you can run a batch analysis that scans
407
+
all packages in the workspace at once and generates a combined vulnerability report.
408
+
<br >To run a batch analysis, right-click in the **Project** window and click **Batch Workspace Analysis Report**.
409
+
<br >The workspace root must contain a supported workspace layout:
410
+
- JS/TS workspace: `package.json` with a lock file (`package-lock.json`, `pnpm-lock.yaml`, or `yarn.lock`)
411
+
- Cargo workspace: `Cargo.toml` with `Cargo.lock`
412
+
<br >Exclusion patterns configured in **Manifest Exclusion Patterns** are applied during workspace discovery to skip
413
+
specific packages from the batch analysis.
414
+
399
415
-**Red Hat Dependency Analytics report**
400
416
<br >The Red Hat Dependency Analytics report is a temporary HTML file that exist if the **Red Hat Dependency Analytics
0 commit comments