@mobb.ai/cli 0.0.1 → 1.4.50

package/.env

@@ -0,0 +1,10 @@
+# production@v21
+API_URL="https://api.mobb.ai/v1/graphql"
+WEB_APP_URL="https://app.mobb.ai"
+GITLAB_API_TOKEN=""
+GITHUB_API_TOKEN=""
+ADO_TEST_ACCESS_TOKEN=""
+HASURA_ACCESS_KEY=""
+LOCAL_GRAPHQL_ENDPOINT=""
+GIT_PROXY_HOST="http://tinyproxy:8888"
+DD_RUM_TOKEN="pubf59c0182545bfb4c299175119f1abf9b"

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Mobb.dev Ltd.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,216 @@
+# Bugsy
+
+Bugsy is a command-line interface (CLI) tool that provides automatic security vulnerability remediation for your code. It is the community edition version of [Mobb](https://mobb.ai), the first vendor-agnostic automated security vulnerability remediation tool. Bugsy is designed to help developers quickly identify and fix security vulnerabilities in their code.
+
+<img width="1888" alt="Bugsy" src="./img/bugsy2.png">
+
+## What is [Mobb](https://mobb.ai)?
+
+[Mobb](https://mobb.ai) is the first vendor-agnostic automatic security vulnerability remediation tool. It ingests SAST results from Checkmarx, CodeQL (GitHub Advanced Security), OpenText Fortify, and Snyk and produces code fixes for developers to review and commit to their code.
+
+## What does Bugsy do?
+
+Bugsy has two modes - Scan (no SAST report needed) & Analyze (the user needs to provide a pre-generated SAST report from one of the supported SAST tools).
+
+Scan
+
+- Uses Checkmarx or Snyk CLI tools to run a SAST scan on a given open-source GitHub/GitLab/ADO repo
+- Analyzes the vulnerability report to identify issues that can be remediated automatically
+- Produces the code fixes and redirects the user to the fix report page on the Mobb platform
+
+Analyze
+
+- Analyzes the a Checkmarx/CodeQL/Fortify/Snyk vulnerability report to identify issues that can be remediated automatically
+- Produces the code fixes and redirects the user to the fix report page on the Mobb platform
+
+## Disclaimer
+
+This is a community edition version that only analyzes public GitHub repositories. Analyzing private repositories is allowed for a limited amount of time.
+Bugsy does not detect any vulnerabilities in your code, it uses findings detected by the SAST tools mentioned above.
+
+## Usage
+
+### Command Line Interface
+
+You can simply run Bugsy from the command line, using npx:
+
+```shell
+npx mobbdev
+```
+
+This will show you Bugsy's usage help:
+
+```shell
+Bugsy - Trusted, Automatic Vulnerability Fixer 🕵️‍♂️
+
+Usage:
+mobbdev <command> [options]
+
+
+Commands:
+  mobbdev scan     Scan your code for vulnerabilities, get automated fixes right away.
+  mobbdev analyze  Provide a vulnerability report and relevant code repository, get automated fixes right away.
+
+Options:
+  -h, --help  Show help                                                                                        [boolean]
+
+Examples:
+  mobbdev scan -r https://github.com/WebGoat/WebGoat  Scan an existing repository
+
+Made with ❤️ by Mobb
+```
+
+To run a new SAST scan on a repo and get fixes, run the **Bugsy Scan** command. Example:
+
+```shell
+npx mobbdev scan --repo https://github.com/mobb-dev/simple-vulnerable-java-project
+```
+
+To get fixes for a pre-generated SAST report, run the **Bugsy Analyze** command. Example:
+npx mobbdev analyze --scan-file sast_results.json --repo https://github.com/mobb-dev/simple-vulnerable-java-project
+
+Bugsy will automatically generate a fix for each supported vulnerability identified in the results, and refer the developer to review and commit the fixes to their code.
+
+To see all the options Bugsy allows, use the Scan or Analyze commands with the -h option:
+
+```shell
+npx mobbdev scan -h
+npx mobbdev analyze -h
+```
+
+### Model Context Protocol (MCP) Server
+
+Bugsy can also be used as an MCP server, allowing AI assistants like Claude to automatically scan and fix vulnerabilities in your code repositories.
+
+#### Prerequisites
+
+1. **API Key**: You need a Mobb API key to use the MCP server functionality
+   - Sign up at [mobb.ai](https://app.mobb.ai) to get your API key
+   - Set the `API_KEY` environment variable: `export API_KEY=your_api_key_here`
+
+2. **Local Git Repository**: The MCP server analyzes git repositories with uncommitted changes
+   - Make sure your code is in a local git repository
+   - Have some modified, added, or staged files to analyze
+
+#### Installation
+
+Run mobb-mcp from command line:
+
+```shell
+npx mobbdev mcp
+```
+
+#### Configuration
+
+Add Mobb MCP to your Cursor MCP client configuration:
+`API_URL` is only required if you are not using https://app.mobb.ai
+
+```json
+{
+  "mcpServers": {
+    "mobb-mcp": {
+      "command": "npx",
+      "args": ["mobbdev", "mcp"],
+      "env": {
+        "API_KEY": "your_mobb_api_key_here",
+        "API_URL": "optional__your_mobb_api_url_here",
+        "MVS_AUTO_FIX": "true"
+      }
+    }
+  }
+}
+```
+
+**Environment Variables:**
+- `API_KEY`: Your Mobb API key (required)
+- `API_URL`: Custom Mobb API URL (optional, defaults to https://app.mobb.ai)
+- `MVS_AUTO_FIX`: Override auto-fix setting - set to `"true"` or `"false"` to force enable/disable automatic fix application regardless of user's database setting (optional)
+
+#### Usage
+
+Once configured, you can use the MCP server through your AI assistant:
+
+1. **Ask Claude to scan for vulnerabilities**:
+   ```
+   run a scan with mobb-mcp
+   ```
+   or
+   ```
+   run fix-vulnerabilities mcp tool
+   ```
+
+2. **The MCP server will**:
+   - Validate the repository path
+   - Check for git changes (modified, added, or staged files)
+   - Upload the changed files for analysis
+   - Generate automated fixes for detected vulnerabilities
+   - Return detailed fix recommendations
+
+#### Available MCP Tools
+
+- **`fix_vulnerabilities`**: Scans the current code changes and returns fixes for potential vulnerabilities
+  - **Parameter**: `path` (string) - The path to the local git repository
+  - **Returns**: Detailed vulnerability fixes with code patches and explanations
+
+#### Example MCP Workflow
+
+1. Make changes to your code
+2. Stage or modify files in git
+3. Ask your AI assistant: "Can you check my code for security vulnerabilities?"
+4. The assistant will use the MCP server to analyze your changes
+5. Receive detailed fix recommendations with code patches
+
+#### Troubleshooting
+
+- **"API_KEY environment variable is not set"**: Make sure you've set your Mobb API key
+- **"Path is not a valid git repository"**: Ensure you're pointing to a valid git repository
+- **"No changed files found"**: Make sure you have modified, added, or staged files in your repository
+
+## Using Bugsy as part of a CI/CD pipeline
+
+If you utilize SAST scans as part of the CI/CD pipeline, Bugsy can be easiy added and provide immediate fix for every issue detected.
+Here is a simple example of a command line that will run Bugsy in your pipeline:
+
+```shell
+npx mobbdev analyze --ci --scan-file $SAST_RESULTS_FILENAME --repo $CI_PROJECT_URL --ref $CI_COMMIT_REF_NAME --api-key $MOBB_API_KEY
+```
+
+### Polling Mode
+
+By default, Bugsy uses WebSocket connections for real-time status updates during analysis. However, some proxy environments or firewalls may block WebSocket connections. In these cases, you can use the `--polling` flag to use HTTP polling instead:
+
+```shell
+npx mobbdev analyze --scan-file report.json --repo https://github.com/org/repo --polling
+```
+
+**When to use `--polling`:**
+- Your network blocks WebSocket connections (ws:// or wss://)
+- You're behind a corporate proxy that doesn't support WebSocket
+- You experience connection timeouts with the default WebSocket mode
+
+**Polling characteristics:**
+- Polling interval: 5 seconds
+- Timeout: 30 minutes
+- Slightly higher latency compared to WebSocket mode, but works in restricted environments
+
+## Contribution
+
+Install the dependencies and run the tests:
+
+```shell
+pnpm install
+
+# or use npm run build:dev to watch for changes
+pnpm run build
+
+# or use npm test:watch to watch for changes
+pnpm run test
+```
+
+### Debugging
+
+If you're using VSCode, you can use the `launch.json` file to debug the code. Run the `CLI tests` configuration to continuously run and debug the tests.
+
+## Getting support
+
+If you need support using Bugsy or just want to share your thoughts and learn more, you are more than welcome to join our [discord server](https://bit.ly/Mobb-discord)

package/bin/cli.mjs

@@ -0,0 +1,2 @@
+#!/usr/bin/env node
+import '../dist/index.mjs'

package/dist/args/commands/upload_ai_blame.d.mts

@@ -0,0 +1,164 @@
+import * as Yargs from 'yargs';
+import z from 'zod';
+
+declare enum AiBlameInferenceType {
+    Chat = "CHAT",
+    HumanEdit = "HUMAN_EDIT",
+    TabAutocomplete = "TAB_AUTOCOMPLETE"
+}
+
+type SanitizationCounts = {
+    detections: {
+        total: number;
+        high: number;
+        medium: number;
+        low: number;
+    };
+};
+
+type Logger = {
+    info: (msg: string, data?: unknown) => void;
+    error: (msg: string, data?: unknown) => void;
+};
+declare const PromptItemZ: z.ZodObject<{
+    type: z.ZodEnum<{
+        USER_PROMPT: "USER_PROMPT";
+        AI_RESPONSE: "AI_RESPONSE";
+        TOOL_EXECUTION: "TOOL_EXECUTION";
+        AI_THINKING: "AI_THINKING";
+        MCP_TOOL_CALL: "MCP_TOOL_CALL";
+    }>;
+    attachedFiles: z.ZodOptional<z.ZodArray<z.ZodObject<{
+        relativePath: z.ZodString;
+        startLine: z.ZodOptional<z.ZodNumber>;
+    }, z.core.$strip>>>;
+    tokens: z.ZodOptional<z.ZodObject<{
+        inputCount: z.ZodNumber;
+        outputCount: z.ZodNumber;
+    }, z.core.$strip>>;
+    text: z.ZodOptional<z.ZodString>;
+    date: z.ZodOptional<z.ZodDate>;
+    tool: z.ZodOptional<z.ZodObject<{
+        name: z.ZodString;
+        parameters: z.ZodString;
+        result: z.ZodString;
+        rawArguments: z.ZodOptional<z.ZodString>;
+        accepted: z.ZodOptional<z.ZodBoolean>;
+        mcpServer: z.ZodOptional<z.ZodString>;
+        mcpToolName: z.ZodOptional<z.ZodString>;
+    }, z.core.$strip>>;
+}, z.core.$strip>;
+type PromptItem = z.infer<typeof PromptItemZ>;
+declare const PromptItemArrayZ: z.ZodArray<z.ZodObject<{
+    type: z.ZodEnum<{
+        USER_PROMPT: "USER_PROMPT";
+        AI_RESPONSE: "AI_RESPONSE";
+        TOOL_EXECUTION: "TOOL_EXECUTION";
+        AI_THINKING: "AI_THINKING";
+        MCP_TOOL_CALL: "MCP_TOOL_CALL";
+    }>;
+    attachedFiles: z.ZodOptional<z.ZodArray<z.ZodObject<{
+        relativePath: z.ZodString;
+        startLine: z.ZodOptional<z.ZodNumber>;
+    }, z.core.$strip>>>;
+    tokens: z.ZodOptional<z.ZodObject<{
+        inputCount: z.ZodNumber;
+        outputCount: z.ZodNumber;
+    }, z.core.$strip>>;
+    text: z.ZodOptional<z.ZodString>;
+    date: z.ZodOptional<z.ZodDate>;
+    tool: z.ZodOptional<z.ZodObject<{
+        name: z.ZodString;
+        parameters: z.ZodString;
+        result: z.ZodString;
+        rawArguments: z.ZodOptional<z.ZodString>;
+        accepted: z.ZodOptional<z.ZodBoolean>;
+        mcpServer: z.ZodOptional<z.ZodString>;
+        mcpToolName: z.ZodOptional<z.ZodString>;
+    }, z.core.$strip>>;
+}, z.core.$strip>>;
+type PromptItemArray = z.infer<typeof PromptItemArrayZ>;
+type RepoState = {
+    repositoryUrl: string | null;
+    branch: string | null;
+    commitSha: string | null;
+};
+/**
+ * Reads git state for tracy event attribution: repo URL, current branch, and
+ * HEAD commit SHA. Each field is read fresh — no caching across calls. Detached
+ * HEAD (rebase, bisect) returns `branch: null` rather than the literal string
+ * "HEAD" that `git rev-parse --abbrev-ref HEAD` would produce.
+ *
+ * Both the CLI daemon and the VS Code extension flow through the shared
+ * `GitService.getCurrentRepoState()` so detached-HEAD handling and SHA
+ * normalization stay in lockstep across the two clients.
+ *
+ * The repository URL is the canonical form (parseScmURL().canonicalUrl) for any
+ * SCM host, including self-hosted / enterprise remotes (scmType "Unknown"); only
+ * an absent or genuinely unparseable remote resolves to `repositoryUrl: null`.
+ *
+ * Never throws — a non-existent dir, missing git binary, or absent/unparseable
+ * remote resolves to null so the daemon hot path can rely on a value.
+ */
+declare function readRepoState(workingDir?: string): Promise<RepoState>;
+/**
+ * Gets the canonical remote repository URL for the working directory's repo, for
+ * any SCM host (GitHub, GitLab, Azure DevOps, Bitbucket, and self-hosted /
+ * enterprise). Returns null when there is no remote or it can't be parsed.
+ */
+declare function getRepositoryUrl(workingDir?: string): Promise<string | null>;
+/**
+ * Get system information for tracking inference source.
+ * Works cross-platform (Windows, macOS, Linux).
+ * Handles errors gracefully for containerized environments where user info may not be available.
+ */
+declare function getSystemInfo(): {
+    computerName: string;
+    userName: string | undefined;
+};
+type UploadAiBlameOptions = {
+    prompt: string[];
+    inference: string[];
+    aiResponseAt?: string[];
+    model?: string[];
+    toolName?: string[];
+    blameType?: AiBlameInferenceType[];
+    sessionId?: string[];
+    'ai-response-at'?: string[];
+    'tool-name'?: string[];
+    'blame-type'?: AiBlameInferenceType[];
+    'session-id'?: string[];
+};
+declare function uploadAiBlameBuilder(args: Yargs.Argv<unknown>): Yargs.Argv<UploadAiBlameOptions>;
+type UploadAiBlameResult = {
+    promptsCounts: SanitizationCounts;
+    inferenceCounts: SanitizationCounts;
+    promptsUUID?: string;
+    inferenceUUID?: string;
+    sanitizationDurationMs?: number;
+};
+declare function uploadAiBlameHandlerFromExtension(args: {
+    prompts: PromptItemArray;
+    inference: string;
+    model: string;
+    tool: string;
+    responseTime: string;
+    blameType?: AiBlameInferenceType;
+    sessionId?: string;
+    apiUrl?: string;
+    webAppUrl?: string;
+    repositoryUrl?: string | null;
+    sanitize?: boolean;
+}): Promise<UploadAiBlameResult>;
+type UploadAiBlameHandlerOptions = {
+    args: UploadAiBlameOptions;
+    exitOnError?: boolean;
+    apiUrl?: string;
+    webAppUrl?: string;
+    logger?: Logger;
+    repositoryUrl?: string | null;
+};
+declare function uploadAiBlameHandler(options: UploadAiBlameHandlerOptions): Promise<void>;
+declare function uploadAiBlameCommandHandler(args: UploadAiBlameOptions): Promise<void>;
+
+export { type PromptItem, type PromptItemArray, type RepoState, type UploadAiBlameOptions, type UploadAiBlameResult, getRepositoryUrl, getSystemInfo, readRepoState, uploadAiBlameBuilder, uploadAiBlameCommandHandler, uploadAiBlameHandler, uploadAiBlameHandlerFromExtension };