codegate-ai 0.14.3 → 0.14.4

package/dist/cli.js

@@ -296,16 +296,22 @@ function addScanCommand(program, version, deps) {
                         ? true
                         : (baseConfig.workflow_audits?.enabled ?? false),
                 },
-                // When the target was a single local file that got staged into a
-                // temp dir (explicitCandidates set), walking the full user-scope
-                // tree is off-target: the user asked to scan one file, not their
-                // whole home. Leaving user-scope on here let sibling findings
-                // (e.g. `~/.agents/skills/*/SKILL.md`) leak into single-file
-                // scans of configs like `.claude/settings.json`. Explicit opt-in
-                // via `--include-user-scope` still forces it on.
+                // When the raw input was a single local file (now staged into a
+                // temp dir), walking the full user-scope tree is off-target — the
+                // user asked to scan one file, not their whole home. Without
+                // this guard, sibling findings (e.g. `~/.agents/skills/*/SKILL.md`)
+                // leak into scans of files like `.claude/settings.json` or
+                // `.idea/workspace.xml`.
+                //
+                // Earlier we gated on `explicitCandidates.length > 0`, but that
+                // falsely passed for files whose extension is not in the
+                // text-like format list (XML, binary-ish configs, etc.) — those
+                // produce zero explicit candidates and the guard never fired.
+                // Using `stagedFromLocalFile` is the reliable signal.
+                // Explicit opt-in via `--include-user-scope` still forces it on.
                 scan_user_scope: options.includeUserScope === true
                     ? true
-                    : resolvedTarget.explicitCandidates && resolvedTarget.explicitCandidates.length > 0
+                    : resolvedTarget.stagedFromLocalFile === true
                         ? false
                         : (baseConfig.scan_user_scope ?? false),
             };

package/dist/scan-target/staging.js

@@ -78,6 +78,7 @@ export function stageLocalFile(absolutePath) {
             scanTarget: tempRoot,
             displayTarget: absolutePath,
             explicitCandidates: collectExplicitCandidates(tempRoot),
+            stagedFromLocalFile: true,
             cleanup: () => cleanupTempDir(tempRoot),
         };
     }
@@ -89,6 +90,7 @@ export function stageLocalFile(absolutePath) {
         scanTarget: tempRoot,
         displayTarget: absolutePath,
         explicitCandidates: collectExplicitCandidates(tempRoot),
+        stagedFromLocalFile: true,
         cleanup: () => cleanupTempDir(tempRoot),
     };
 }

package/dist/scan-target/types.d.ts

@@ -10,6 +10,14 @@ export interface ResolvedScanTarget {
     scanTarget: string;
     displayTarget: string;
     explicitCandidates?: ExplicitScanCandidate[];
+    /**
+     * `true` when the raw input was a local file that got staged into a
+     * temp directory. This is the signal the CLI uses to disable the
+     * user-scope walk, regardless of whether `explicitCandidates` could be
+     * inferred for the file (an XML / binary / unrecognised extension
+     * would still benefit from the scope guard).
+     */
+    stagedFromLocalFile?: boolean;
     cleanup?: () => Promise<void> | void;
 }
 export interface ResolveScanTargetInput {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "codegate-ai",
-  "version": "0.14.3",
+  "version": "0.14.4",
   "description": "Pre-flight security scanner for AI coding tool configurations.",
   "license": "MIT",
   "type": "module",