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
`build`, `dist`, `.tox`, `.mypy_cache`, `.pytest_cache`, `*.egg-info`, `vendor`) is a sane
37
+
default, but some projects keep manifest files under those names — e.g. `build/requirements.txt`.
38
+
Pass `--include-dirs build,dist` to scan them. Names are matched against any path segment,
39
+
mirroring how the default exclude list is applied.
40
+
-`--include-module-folders` now functions as documented: it re-includes the JS/TS module
41
+
folders (`node_modules`, `bower_components`, `jspm_packages`) as a group. Previously the
42
+
flag was accepted but had no effect.
43
+
44
+
## 2.4.9
45
+
46
+
### Added: opt-in streaming log channel via `--upload-logs`
47
+
48
+
- New `--upload-logs` flag (default off). When set, each CLI invocation registers a run, reports a per-run status (`in_progress` / `success` / `failure` / `cancelled`), and uploads a transcript of its own log output to the Socket backend for that run, visible in the Socket admin views. The transcript is captured regardless of the local `--enable-debug` state; the existing terminal verbosity is unchanged.
49
+
- New `--no-upload-logs` flag (mutually exclusive with `--upload-logs`) explicitly opts the run out of uploading logs, even when an org-level override would otherwise enable it. Use this when you need a guaranteed no-upload guarantee (e.g. legal/consent reasons).
50
+
- The Socket backend can also force-enable streaming for specific orgs in the absence of an explicit opt-out. The feature is best-effort — registration or upload failures silently degrade and never block the scan.
@@ -205,13 +205,14 @@ If you don't want to provide the Socket API Token every time then you can use th
205
205
|`--workspace-name`| False || Workspace name suffix to append to repository name (repo-name-workspace_name). Must be used with `--sub-path`|
206
206
|`--excluded-ecosystems`| False | [] | List of ecosystems to exclude from analysis (JSON array string). You can get supported files from the [Supported Files API](https://docs.socket.dev/reference/getsupportedfiles) |
207
207
|`--exclude-paths`| False || Comma-separated paths/globs to exclude from **both** manifest discovery (every scan) **and** reachability analysis (e.g. `tests/**,packages/legacy,*.spec.ts`). Patterns are scan-root-relative, case-sensitive globs where `*` does not cross `/` and `**` does. Supersedes `--reach-exclude-paths`. |
208
+
|`--include-dirs`| False || Comma-separated directory **names** that are excluded from manifest discovery by default but should be scanned (e.g. `build,dist`). Names are matched against any path segment, mirroring the default exclude list (`node_modules`, `bower_components`, `jspm_packages`, `__pycache__`, `.venv`, `venv`, `build`, `dist`, `.tox`, `.mypy_cache`, `.pytest_cache`, `*.egg-info`, `vendor`). Use this when manifest files live under a normally-ignored folder, e.g. `build/requirements.txt`. |
|`--default-branch`| False |*auto*| Make this branch the default branch (auto-detected from git and CI environment when not specified) |
213
214
|`--pending-head`| False |*auto*| If true, the new scan will be set as the branch's head scan (automatically synced with default-branch) |
214
-
| `--include-module-folders` | False | False | If enabled will include manifest files from folders like node_modules |
215
+
| `--include-module-folders` | False | False | If enabled, re-includes the JS/TS module folders (`node_modules`, `bower_components`, `jspm_packages`) in manifest discovery. For other excluded directories, use `--include-dirs`. |
215
216
216
217
#### Output Configuration
217
218
| Parameter | Required | Default | Description |
@@ -240,9 +241,9 @@ If you don't want to provide the Socket API Token every time then you can use th
|`--reach`| False | False | Enable reachability analysis to identify which vulnerable functions are actually called by your code. Creates a tier-1 full-application reachability scan (`scan_type=socket_tier1`). |
243
-
|`--reach-version`| False | 15.3.24| Version of @coana-tech/cli to use. Defaults to the pinned version that ships with this CLI release, so the engine only changes when you upgrade the Socket CLI. Pass `latest` to always use the newest published version (opt-in auto-update), or an explicit version (e.g. `1.2.3`) to pin it. |
244
-
|`--reach-analysis-timeout`| False |600| Timeout in seconds forthe reachability analysis. Omitted by default, so coana applies its own default. Alias: `--reach-timeout`|
245
-
|`--reach-analysis-memory-limit`| False |8192| Memory limit in MB forthe reachability analysis. Omitted by default, so coana applies its own default. Alias: `--reach-memory-limit`|
244
+
|`--reach-version`| False | 15.5.0 | Version of @coana-tech/cli to use. Defaults to the pinned version that ships with this CLI release, so the engine only changes when you upgrade the Socket CLI. Pass `latest` to always use the newest published version (opt-in auto-update), or an explicit version (e.g. `1.2.3`) to pin it. |
245
+
|`--reach-analysis-timeout`| False |10m| Timeout foreach reachability analysis run, e.g. `90s`, `10m` or `1h`. Omitted by default, so coana applies its own default (`10m`). Alias: `--reach-timeout`|
246
+
|`--reach-analysis-memory-limit`| False |8GB| Memory limit foreach reachability analysis run, e.g. `512MB` or `8GB`. Omitted by default, so coana applies its own default (`8GB`). Alias: `--reach-memory-limit`|
246
247
|`--reach-concurrency`| False | 1 | Control parallel analysis execution (must be >= 1). Omitted by default, so coana applies its own default. |
247
248
|`--reach-additional-params`| False || Pass custom parameters to the coana CLI tool |
248
249
|`--reach-ecosystems`| False || Comma-separated list of ecosystems to analyze (e.g., "npm,pypi"). If not specified, all supported ecosystems are analyzed |
0 commit comments