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
{{ message }}
Repository navigation
Commit d9ee124
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: mcpb/manifest.json
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@
4
4
"display_name": "CodeAnt AI",
5
5
"version": "0.5.3",
6
6
"description": "Drive CodeAnt AI security scans and code review from Claude \u2014 org-wide secret triage, cross-repo SAST/SCA findings, on-demand scans, and local PR review.",
7
-
"long_description": "CodeAnt AI inside Claude. Ask things like \"show my highest-priority Hotlist findings\", \"list AWS cloud findings\", \"show this pentest report\", or \"review my staged changes\"\u2014 Claude calls the CodeAnt API directly via this MCP server.\n\nIncludes 22 read-only tools, covering repository, Hotlist, cloud security, anti-pattern, and pentest findings plus an authenticated GET escape hatch for new APIs, 2 sign-in tools, and 3 opt-in write tools gated behind a setting.\n\nRequires a CodeAnt account. Sign up at https://codeant.ai. To authenticate, call the `codeant_login` tool \u2014 it returns a sign-in link (and opens it in your browser when it can), then saves the token once you finish.\n\nCollects usage telemetry via PostHog by default (events are tied to your CodeAnt token); turn on \"Disable telemetry\" in the extension settings to opt out.",
7
+
"long_description": "CodeAnt AI inside Claude. Ask things like \"show my highest-priority Hotlist findings\", \"list AWS cloud findings\", \"show this pentest report\", or \"review my staged changes\"\u2014 Claude calls the CodeAnt API directly via this MCP server.\n\nIncludes 23 read-only tools, covering repository, Hotlist, cloud security, anti-pattern, and pentest findings plus an authenticated GET escape hatch for new APIs, 2 sign-in tools, and 3 opt-in write tools gated behind a setting.\n\nRequires a CodeAnt account. Sign up at https://codeant.ai. To authenticate, call the `codeant_login` tool \u2014 it returns a sign-in link (and opens it in your browser when it can), then saves the token once you finish.\n\nCollects usage telemetry via PostHog by default (events are tied to your CodeAnt token); turn on \"Disable telemetry\" in the extension settings to opt out.",
codeant scans results --repo acme/backend --types secrets --secrets-scope all
296
296
```
297
297
298
+
Latest history results retain the last completed assessment while a newer run is pending or failed; the run status still describes the latest job. An explicit `--history-run` retrieves only that run.
299
+
298
300
`--secrets-scope` accepts `current` (default), `history`, or `all`. `--history-run` selects one immutable run identity; otherwise the latest history run is read. Status values are `not_started`, `queued`, `running`, `awaiting_verification`, `completed`, `failed`, and `disabled`. Failed and disabled runs are terminal outcomes, not clean scans. Jobs stalled for over one hour are reported as failed. When available, `last_completed_run_id` identifies the previous successful run. Results from incomplete runs must not be treated as a complete assessment.
299
301
300
302
History findings expose `metadata.commit`, `branches`, `tags`, `scanned_at`, `only_in_history`, and native `verification_status`. Branches/tags contain the commit at scan time; they do not identify where it originated. `only_in_history` compares the secret identity against the selected, unfiltered snapshot, including findings dismissed or marked false positive. It is `null` when the baseline is unavailable. History-only retrieval works without a snapshot scan; in that case `scan` is `null`.
@@ -333,7 +335,7 @@ A vulnerable package can now include:
333
335
}
334
336
```
335
337
336
-
Use the direct introducer and manifest to select the dependency to edit. `fix_version` fixes the vulnerable package; it does not promise a safe version of its direct introducer. There can be multiple introducers and manifest locations. Lockfiles are null when unknown or generated rather than committed. Path status distinguishes `pending`, `resolved`, `partial`, and `unavailable`; a resolved empty list differs from unavailable evidence. Existing scans are readable, but missing evidence requires a new scan.
338
+
Use the direct introducer and manifest to select the dependency to edit. `fix_version` fixes the vulnerable package; it does not promise a safe version of its direct introducer. There can be multiple introducers and manifest locations. Very large path payloads are bounded; `dependency_paths_truncated: true` and a `partial` path status identify incomplete public evidence. Lockfiles are null when unknown or generated rather than committed. Path status distinguishes `pending`, `resolved`, `partial`, and `unavailable`; a resolved empty list differs from unavailable evidence. Existing scans are readable, but missing evidence requires a new scan.
337
339
338
340
Schema 1.1 adds `category_status` (including independent SCA `dependency_paths_status`), optional `history_run`, and category metadata. SCA IDs now include package/version/manifest context; history IDs include commit and secret identity. Existing current-secret IDs are unchanged. JSON and field projection preserve metadata; SARIF includes it in result properties, and CSV adds JSON-encoded `package` and `metadata` columns.
339
341
@@ -350,3 +352,5 @@ npm test -- tests/scans/history-secrets.test.js
350
352
```
351
353
352
354
This suite reads the specified fixture; it does not trigger scans or modify settings.
355
+
356
+
Scan-start aliases `anti_patterns` and `complex_functions` select the `antipatterns` scanner, which produces both result categories.
0 commit comments