

┌─────────────┐
│ Scan Status │
└─────────────┘
  Scanning 2 files tracked by git with 1 Code rule:
  Scanning 2 files.
  Current version has 14 findings.

Creating git worktree from 'bar' to scan baseline.
  Will report findings introduced by these commits (may be incomplete for shallow checkouts):
    * ff8459e commit #9
    * a0592d5 commit #8
    * 4ec8882 commit #7
    * 620f8c9 commit #6
    * d373a3a commit #5
    * 7d69b10 commit #4
    * 4cb3ddb commit #3
    * d623cf5 commit #2
    * 19cc9d5 commit #1
    * a9cab85 merging 4a372020118b6787c208de20e374aac0cdc2b841
    *   6d572d7 merging 657cdbabbd73778d81796d0128207fee79136f10
    |\  
    | * 657cdba commit #5
    | * 4c7d0ba commit #4
    * | e564346 merging b62d8d638ebfd9494bd16634cf8783db074836ea
    * | 866f275 merging 5275d4bb21ad3fd0c6361b4e252b7d46ce3a6583
    |\| 
    | * 5275d4b commit #3
    | * 9121d4d commit #2
    * ab8ab0a merging e554aecf7fc79d7dafcf8e763ec65fd626828f28
    * 23c546f commit #1
  The current branch is missing these commits from the baseline branch:
    * ea6d96d commit #9
    * 0367792 commit #8
  Any finding these commits fixed will look like a new finding in the current branch.
  To avoid reporting such findings, compare to the branch-off point with:
    --baseline-commit=$(git merge-base bar HEAD)



┌─────────────┐
│ Scan Status │
└─────────────┘
  Scanning 1 file tracked by git with 1 Code rule:
  Scanning 1 file.


┌──────────────┐
│ Scan Summary │
└──────────────┘
✅ Scan completed successfully.
 • Findings: 13 (13 blocking)
 • Rules run: 1
 • Targets scanned: 2
 • Parsed lines: ~100.0%
 • Scan was limited to files changed since baseline commit.
 • For a detailed list of skipped files and lines, run semgrep with the --verbose flag
Ran 1 rule on 2 files: 13 findings.
