morluto/rea
1
0
Fork 0
mirror of https://github.com/morluto/rea.git synced 2026-11-05 06:45:22 +00:00
Code Issues 1.3k Projects Packages Wiki Activity

[PR #1800] [CLOSED] feat(ghidra): disable named auto-analyzers via REA_GHIDRA_DISABLED_ANALYZERS #4825

New issue
Closed
opened 2026-10-31 00:55:25 +00:00 by bsakaguchi · 0 comments
bsakaguchi commented 2026-10-31 00:55:25 +00:00
Owner
Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/1800
Author: @akushonkamen
Created: 10/11/2026
Status: ❌ Closed

Base: main ← Head: fix/1783-ghidra-analyzer-overrides

📝 Commits (9)

  • 8bc9b47 feat(ghidra): disable named auto-analyzers via REA_GHIDRA_DISABLED_ANALYZERS
  • f9cc9e6 test(ghidra): cover the analyzer-options preScript in the packaged Windows verifier
  • df0d2b0 fix(ghidra): fail closed when a requested analyzer is unknown or stays enabled
  • ac583cf fix(ghidra): canonicalize disabled analyzer settings
  • 4c18c34 refactor(ghidra): share analyzer provider fixture outside suite callback
  • 453fbbd test(ghidra): separate Windows launcher runtime coverage
  • 94c6570 chore: merge current main into PR #1800
  • 12d071d Merge branch 'main' into fix/1783-ghidra-analyzer-overrides
  • 53d8d67 Merge branch 'main' into fix/1783-ghidra-analyzer-overrides

📊 Changes

5 files changed (+53 additions, -27 deletions)

View changed files

📝 docs/installation.md (+3 -0)
📝 src/config/ghidraDisabledAnalyzers.ts (+5 -2)
📝 src/ghidra/GhidraDisabledAnalyzers.test.ts (+7 -2)
📝 src/ghidra/GhidraProvider.behavior.test.ts (+36 -23)
📝 tests/boundary/providers/ghidra/ghidraLauncher.test.ts (+2 -0)

📄 Description

Summary

Fixes #1783. Ghidra's default auto-analysis can stall indefinitely in a single analyzer (ObjcMessageAnalyzer on a 1.85 MB Swift/ObjC arm64 Mach-O), and REA gave the caller no way to skip it and no record of what ran: the analysis profile always said analyzer_preset: "ghidra-default". This adds REA_GHIDRA_DISABLED_ANALYZERS, a comma-separated list of exact analyzer names that are disabled via a pre-analysis script before default auto-analysis, recorded in the analysis profile so snapshots and Evidence stay bound to the analysis that actually ran.

Problem and expected behavior

src/ghidra/GhidraLauncher.ts's ghidraHeadlessArguments only injected -preScript for the DOS COM loader branch and seed files — there was no channel for analyzer options (verified on main @ ce845ba4: interface 371–386, argv builder 388–468; the DOS COM -preScript sits at what is now 446–449 after unrelated main-side churn, content unchanged), and src/ghidra/GhidraAnalysisProfile.ts:152 hardcodes analyzer_preset: "ghidra-default" with no configurable analyzer field. The issue's out-of-REA controls show the same binary analyzing to completion in 76 s with one analyzer turned off, versus a 300 s analysis timeout with defaults — so a supported skip is the fix. Expected: a caller can name analyzers to disable for a session, and the profile records the override.

Change and scope

  • New packaged pre-script bridge/ghidra/ReaGhidraAnalysisOptions.java (modeled on the existing ReaGhidraPrepareCom precedent): requires exactly one comma-separated argument and calls setAnalysisOption(currentProgram, "<name>", "false") for each name.
  • New src/config/ghidraDisabledAnalyzers.ts parses REA_GHIDRA_DISABLED_ANALYZERS: comma-separated, blank entries dropped, at most 32 names of at most 120 chars, each matching ^[A-Za-z0-9][A-Za-z0-9 ._-]*$ (a name can neither start with - nor contain a comma — Ghidra's headless parser would eat those as its own options). Anything else fails config admission.
  • Plumbing: src/config/environment.ts:43 → src/config/parseConfig.ts:91-93 → src/config/types.ts:17 → src/ghidra/GhidraProvider.ts:195 → src/ghidra/GhidraProviderClient.ts → src/ghidra/GhidraLauncher.ts:468-475, where the -preScript is injected after the seed script and before the post-analysis repair/bridge postScripts.
  • The analysis profile records the override truthfully: analyzer_preset: "ghidra-default+disabled:<names>" plus structured analysis_options.disabled_analyzers (src/ghidra/GhidraAnalysisProfile.ts). Mirroring the language-override binding, ghidraProfileDisabledAnalyzers reads the commitment back and a session fails closed (refuses to open) when its committed profile and the active setting disagree.
  • docs/installation.md documents the setting, its name rules, and that disabling an analyzer skips the facts it would have produced.
  • Not included: a general analyzer-preset selector, deadline diagnostics on timeout (the issue's second suggested remedy), and any change to default behavior — with the setting unset, argv is byte-identical to before (covered by test).

Contract and boundary impact

  • Semantic owner and earliest changed stage: Ghidra headless launcher argv construction and analysis-profile resolution (src/ghidra/GhidraLauncher.ts, src/ghidra/GhidraAnalysisProfile.ts).
  • CLI and MCP/tool-catalog contract: none; the setting is environment/config-only, no CLI flag or MCP field added.
  • Provider, bridge, target-format, or platform compatibility: new packaged bridge script bridge/ghidra/ReaGhidraAnalysisOptions.java (added to package.json files and the packaged-Windows verifier manifest); no change to existing scripts.
  • Evidence, artifact, provenance, or reconstruction contract: the analysis profile now records analyzer_preset: "ghidra-default+disabled:<names>" and analysis_options.disabled_analyzers, and session open fails closed on profile/setting mismatch, so snapshots stay bound to the analysis that ran.
  • Process execution, authorization, cleanup, or containment impact: one additional Ghidra pre-script in the same bridge directory under the existing -scriptPath; no new processes or cleanup paths.
  • Generated metadata, package, or installation impact: package.json ships the new bridge file; docs/installation.md documents the setting. No committed generated outputs change.

Evidence and regression coverage

  • Tests added or updated:
    • src/config/ghidraDisabledAnalyzers.ts covered by new src/ghidra/GhidraDisabledAnalyzers.test.ts (10 tests: parsing, limits, name rules).
    • tests/boundary/providers/ghidra/ghidraLauncher.test.ts: argv injection, ordering after seed / before -postScript, byte-identical argv when unset (3 new tests).
    • src/ghidra/GhidraProvider.behavior.test.ts: profile recording, fail-closed binding, end-to-end provider threading (3 new tests).
    • scripts/verify-packaged-ghidra-windows.mjs covers the new pre-script in the packaged Windows verifier manifest (second commit).
  • Base reproduction: after rebasing onto main @ 40d9c7b8 (7 commits advanced since the branch point ce845ba4, clean rebase), the red state was reproduced by restoring all non-test source files to origin/main while keeping the new tests, then:
    • timeout 300 npx vitest run tests/boundary/providers/ghidra/ghidraLauncher.test.ts — 3 failed | 16 passed | 1 skipped.
    • timeout 300 npx vitest run src/ghidra/GhidraDisabledAnalyzers.test.ts — Error: Cannot find module '../config/ghidraDisabledAnalyzers.js'.
    • timeout 300 npx vitest run src/ghidra/GhidraProvider.behavior.test.ts -t "disabled analyzer" — 3 failed | 40 skipped.
      All pass with the fix restored (numbers under Validation performed).
  • User-visible CLI/MCP output (if applicable): none by default; with REA_GHIDRA_DISABLED_ANALYZERS="Objective-C Message Analyzer" the session's profile carries analyzer_preset: "ghidra-default+disabled:Objective-C Message Analyzer".
  • Remaining proof gaps: real Ghidra was not exercised — this machine has no Ghidra installation (which analyzeHeadless → not found; no ~/ghidra*, /opt/ghidra*, /Applications/ghidra*; GHIDRA_INSTALL_DIR empty), so the Ghidra 12.1.4 stall reproduction and the disable-one-analyzer 76 s control come from the issue report's out-of-REA analyzeHeadless runs, as stated in the commit message.

For evidence-bearing changes:

  • Observed, derived, and inferred claims remain distinguishable.
  • Artifact identity, source provenance, and failed attempts remain preserved.
  • Unsupported, incomplete, unavailable, or uncertain outcomes remain visible.

Validation performed

Rebased onto origin/main @ 40d9c7b8 (branch point ce845ba4), then, on macOS arm64 / Node 24.14.0 — red state first as listed above, then with the fix restored:

  • timeout 300 npx vitest run tests/boundary/providers/ghidra/ghidraLauncher.test.ts — 19 passed | 1 skipped.
  • timeout 300 npx vitest run src/ghidra/GhidraDisabledAnalyzers.test.ts — 10 passed.
  • timeout 300 npx vitest run src/ghidra/GhidraProvider.behavior.test.ts — 43 passed (full file, incl. the 3 new tests).
  • timeout 300 npx vitest run src/ghidra/GhidraDosComLoadImage.test.ts — 13 passed.
  • timeout 300 npx vitest run src/config.test.ts src/ghidra/GhidraLanguageOverride.test.ts src/ghidra/GhidraAnalysisSeeds.test.ts src/ghidra/GhidraLauncherEnvironment.test.ts — 76 passed.
  • timeout 300 npx vitest run tests/boundary/providers/ghidra/ — 54 passed | 1 skipped.
  • timeout 300 npx vitest run tests/boundary/mcp/ghidraEvidenceMcp.test.ts — 4 passed.
  • timeout 570 npx vitest run src/ghidra/ — 17 files, 314 passed.
  • npm run check:fast — 2 successful (turbo typecheck + lint, lint includes verify:module-boundaries).
  • npm run verify:test-discovery — "Discovered all 823 test files exactly once."
  • npm run build:cached — exit 0; then node scripts/check-doc-facts.mjs — exit 0.
  • node scripts/generate-package-metadata.mjs --check, node scripts/generate-skill-metadata.mjs --check, node scripts/generate-product-catalog.mjs --check, node scripts/generate-completion-ledger.mjs --check, node scripts/generate-error-schema.mjs --check — each exit 0. (completion-ledger's first run failed on the git-ignored docs/verification/managed-conformance-manifest.json; npm run docs:generate regenerated it, after which the check passes. Working tree stayed clean.)
  • npm run verify:ghidra (real Ghidra e2e) — not run: no Ghidra installation on this machine (see Remaining proof gaps).

Compatibility, safety, and release

  • Breaking changes or migration steps: none. With the setting unset, launcher argv is byte-identical to before and the profile records "ghidra-default" as before.
  • Real Hopper/Ghidra, browser, or OS coverage: real Ghidra not available here; the report's Ghidra 12.1.4 controls cover the runtime behavior of the pre-script mechanism (setAnalysisOption in a pre-script) outside REA. Unit/boundary coverage covers everything REA adds around it.
  • Package or release metadata impact: bridge/ghidra/ReaGhidraAnalysisOptions.java added to the packaged file list and the packaged-Windows verifier manifest.
  • Security, privacy, process, or containment review: analyzer names are strictly whitelisted (length, count, character set) and injected as a single pre-script argument into the existing bridge -scriptPath; no shell interpolation, no new scripts sourced from user paths, no change to process cleanup.

Review checklist

  • This PR addresses a concrete problem or an agreed enhancement.
  • The PR has one focused outcome and the title follows type(scope): outcome.
  • Related issue is linked, or the reason for not linking one is stated above.
  • Tests cover changed observable behavior and meaningful failure paths.
  • Owning docs, contracts, and generated metadata are updated where needed.
  • User-visible CLI/MCP changes include representative output.
  • I checked the final diff for secrets, unrelated cleanup, and unsupported claims.

Disclosure: this contribution is prepared with AI assistance (Claude), reviewed and verified by me (same disclosure as the issue claim comment).

Summary by CodeRabbit

  • New Features
    • Added an option to disable selected Ghidra analyzers during analysis. Configure analyzer names as a comma-separated list; the setting is validated and applied before auto-analysis.
    • Analysis profiles record the selected analyzers. Sessions won’t open if their saved settings don’t match the current configuration.
  • Documentation
    • Documented the analyzer setting, accepted names and limits, and its effect: disabled analyzers won’t produce their usual analysis results.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/morluto/rea/pull/1800 **Author:** [@akushonkamen](https://github.com/akushonkamen) **Created:** 10/11/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `fix/1783-ghidra-analyzer-overrides` --- ### 📝 Commits (9) - [`8bc9b47`](https://github.com/morluto/rea/commit/8bc9b47c205897b3d89fe8b120cd2ec6e27caebf) feat(ghidra): disable named auto-analyzers via REA_GHIDRA_DISABLED_ANALYZERS - [`f9cc9e6`](https://github.com/morluto/rea/commit/f9cc9e6f166bcebc47f234689bf752cbd6150c72) test(ghidra): cover the analyzer-options preScript in the packaged Windows verifier - [`df0d2b0`](https://github.com/morluto/rea/commit/df0d2b01ba51ac78485a7fef2efb8f1f895a97ca) fix(ghidra): fail closed when a requested analyzer is unknown or stays enabled - [`ac583cf`](https://github.com/morluto/rea/commit/ac583cf8eb9b54ebdba251b3a5630f6e15c39e34) fix(ghidra): canonicalize disabled analyzer settings - [`4c18c34`](https://github.com/morluto/rea/commit/4c18c340a21befd6e371b1513f1869987a72320d) refactor(ghidra): share analyzer provider fixture outside suite callback - [`453fbbd`](https://github.com/morluto/rea/commit/453fbbdc91416c89b7c485197201897ec16c5153) test(ghidra): separate Windows launcher runtime coverage - [`94c6570`](https://github.com/morluto/rea/commit/94c65708f61ec0958229690a5bc7e5d999839d5c) chore: merge current main into PR #1800 - [`12d071d`](https://github.com/morluto/rea/commit/12d071de07d28c7b195888dd6dd4df2847069ee9) Merge branch 'main' into fix/1783-ghidra-analyzer-overrides - [`53d8d67`](https://github.com/morluto/rea/commit/53d8d67828d60491b6f36e699d0718e287710d69) Merge branch 'main' into fix/1783-ghidra-analyzer-overrides ### 📊 Changes **5 files changed** (+53 additions, -27 deletions) <details> <summary>View changed files</summary> 📝 `docs/installation.md` (+3 -0) 📝 `src/config/ghidraDisabledAnalyzers.ts` (+5 -2) 📝 `src/ghidra/GhidraDisabledAnalyzers.test.ts` (+7 -2) 📝 `src/ghidra/GhidraProvider.behavior.test.ts` (+36 -23) 📝 `tests/boundary/providers/ghidra/ghidraLauncher.test.ts` (+2 -0) </details> ### 📄 Description ## Summary Fixes #1783. Ghidra's default auto-analysis can stall indefinitely in a single analyzer (`ObjcMessageAnalyzer` on a 1.85 MB Swift/ObjC arm64 Mach-O), and REA gave the caller no way to skip it and no record of what ran: the analysis profile always said `analyzer_preset: "ghidra-default"`. This adds `REA_GHIDRA_DISABLED_ANALYZERS`, a comma-separated list of exact analyzer names that are disabled via a pre-analysis script before default auto-analysis, recorded in the analysis profile so snapshots and Evidence stay bound to the analysis that actually ran. ## Problem and expected behavior `src/ghidra/GhidraLauncher.ts`'s `ghidraHeadlessArguments` only injected `-preScript` for the DOS COM loader branch and seed files — there was no channel for analyzer options (verified on `main` @ `ce845ba4`: interface 371–386, argv builder 388–468; the DOS COM `-preScript` sits at what is now 446–449 after unrelated main-side churn, content unchanged), and `src/ghidra/GhidraAnalysisProfile.ts:152` hardcodes `analyzer_preset: "ghidra-default"` with no configurable analyzer field. The issue's out-of-REA controls show the same binary analyzing to completion in 76 s with one analyzer turned off, versus a 300 s analysis timeout with defaults — so a supported skip is the fix. Expected: a caller can name analyzers to disable for a session, and the profile records the override. ## Change and scope - New packaged pre-script `bridge/ghidra/ReaGhidraAnalysisOptions.java` (modeled on the existing `ReaGhidraPrepareCom` precedent): requires exactly one comma-separated argument and calls `setAnalysisOption(currentProgram, "<name>", "false")` for each name. - New `src/config/ghidraDisabledAnalyzers.ts` parses `REA_GHIDRA_DISABLED_ANALYZERS`: comma-separated, blank entries dropped, at most 32 names of at most 120 chars, each matching `^[A-Za-z0-9][A-Za-z0-9 ._-]*$` (a name can neither start with `-` nor contain a comma — Ghidra's headless parser would eat those as its own options). Anything else fails config admission. - Plumbing: `src/config/environment.ts:43` → `src/config/parseConfig.ts:91-93` → `src/config/types.ts:17` → `src/ghidra/GhidraProvider.ts:195` → `src/ghidra/GhidraProviderClient.ts` → `src/ghidra/GhidraLauncher.ts:468-475`, where the `-preScript` is injected after the seed script and before the post-analysis repair/bridge postScripts. - The analysis profile records the override truthfully: `analyzer_preset: "ghidra-default+disabled:<names>"` plus structured `analysis_options.disabled_analyzers` (`src/ghidra/GhidraAnalysisProfile.ts`). Mirroring the language-override binding, `ghidraProfileDisabledAnalyzers` reads the commitment back and a session fails closed (refuses to open) when its committed profile and the active setting disagree. - `docs/installation.md` documents the setting, its name rules, and that disabling an analyzer skips the facts it would have produced. - Not included: a general analyzer-preset selector, deadline diagnostics on timeout (the issue's second suggested remedy), and any change to default behavior — with the setting unset, argv is byte-identical to before (covered by test). ## Contract and boundary impact - Semantic owner and earliest changed stage: Ghidra headless launcher argv construction and analysis-profile resolution (`src/ghidra/GhidraLauncher.ts`, `src/ghidra/GhidraAnalysisProfile.ts`). - CLI and MCP/tool-catalog contract: none; the setting is environment/config-only, no CLI flag or MCP field added. - Provider, bridge, target-format, or platform compatibility: new packaged bridge script `bridge/ghidra/ReaGhidraAnalysisOptions.java` (added to `package.json` files and the packaged-Windows verifier manifest); no change to existing scripts. - Evidence, artifact, provenance, or reconstruction contract: the analysis profile now records `analyzer_preset: "ghidra-default+disabled:<names>"` and `analysis_options.disabled_analyzers`, and session open fails closed on profile/setting mismatch, so snapshots stay bound to the analysis that ran. - Process execution, authorization, cleanup, or containment impact: one additional Ghidra pre-script in the same bridge directory under the existing `-scriptPath`; no new processes or cleanup paths. - Generated metadata, package, or installation impact: `package.json` ships the new bridge file; `docs/installation.md` documents the setting. No committed generated outputs change. ## Evidence and regression coverage - Tests added or updated: - `src/config/ghidraDisabledAnalyzers.ts` covered by new `src/ghidra/GhidraDisabledAnalyzers.test.ts` (10 tests: parsing, limits, name rules). - `tests/boundary/providers/ghidra/ghidraLauncher.test.ts`: argv injection, ordering after seed / before `-postScript`, byte-identical argv when unset (3 new tests). - `src/ghidra/GhidraProvider.behavior.test.ts`: profile recording, fail-closed binding, end-to-end provider threading (3 new tests). - `scripts/verify-packaged-ghidra-windows.mjs` covers the new pre-script in the packaged Windows verifier manifest (second commit). - Base reproduction: after rebasing onto `main` @ `40d9c7b8` (7 commits advanced since the branch point `ce845ba4`, clean rebase), the red state was reproduced by restoring all non-test source files to `origin/main` while keeping the new tests, then: - `timeout 300 npx vitest run tests/boundary/providers/ghidra/ghidraLauncher.test.ts` — 3 failed | 16 passed | 1 skipped. - `timeout 300 npx vitest run src/ghidra/GhidraDisabledAnalyzers.test.ts` — `Error: Cannot find module '../config/ghidraDisabledAnalyzers.js'`. - `timeout 300 npx vitest run src/ghidra/GhidraProvider.behavior.test.ts -t "disabled analyzer"` — 3 failed | 40 skipped. All pass with the fix restored (numbers under Validation performed). - User-visible CLI/MCP output (if applicable): none by default; with `REA_GHIDRA_DISABLED_ANALYZERS="Objective-C Message Analyzer"` the session's profile carries `analyzer_preset: "ghidra-default+disabled:Objective-C Message Analyzer"`. - Remaining proof gaps: real Ghidra was not exercised — this machine has no Ghidra installation (`which analyzeHeadless` → not found; no `~/ghidra*`, `/opt/ghidra*`, `/Applications/ghidra*`; `GHIDRA_INSTALL_DIR` empty), so the Ghidra 12.1.4 stall reproduction and the disable-one-analyzer 76 s control come from the issue report's out-of-REA `analyzeHeadless` runs, as stated in the commit message. For evidence-bearing changes: - [x] Observed, derived, and inferred claims remain distinguishable. - [x] Artifact identity, source provenance, and failed attempts remain preserved. - [x] Unsupported, incomplete, unavailable, or uncertain outcomes remain visible. ## Validation performed Rebased onto `origin/main` @ `40d9c7b8` (branch point `ce845ba4`), then, on macOS arm64 / Node 24.14.0 — red state first as listed above, then with the fix restored: - `timeout 300 npx vitest run tests/boundary/providers/ghidra/ghidraLauncher.test.ts` — 19 passed | 1 skipped. - `timeout 300 npx vitest run src/ghidra/GhidraDisabledAnalyzers.test.ts` — 10 passed. - `timeout 300 npx vitest run src/ghidra/GhidraProvider.behavior.test.ts` — 43 passed (full file, incl. the 3 new tests). - `timeout 300 npx vitest run src/ghidra/GhidraDosComLoadImage.test.ts` — 13 passed. - `timeout 300 npx vitest run src/config.test.ts src/ghidra/GhidraLanguageOverride.test.ts src/ghidra/GhidraAnalysisSeeds.test.ts src/ghidra/GhidraLauncherEnvironment.test.ts` — 76 passed. - `timeout 300 npx vitest run tests/boundary/providers/ghidra/` — 54 passed | 1 skipped. - `timeout 300 npx vitest run tests/boundary/mcp/ghidraEvidenceMcp.test.ts` — 4 passed. - `timeout 570 npx vitest run src/ghidra/` — 17 files, 314 passed. - `npm run check:fast` — 2 successful (turbo typecheck + lint, lint includes `verify:module-boundaries`). - `npm run verify:test-discovery` — "Discovered all 823 test files exactly once." - `npm run build:cached` — exit 0; then `node scripts/check-doc-facts.mjs` — exit 0. - `node scripts/generate-package-metadata.mjs --check`, `node scripts/generate-skill-metadata.mjs --check`, `node scripts/generate-product-catalog.mjs --check`, `node scripts/generate-completion-ledger.mjs --check`, `node scripts/generate-error-schema.mjs --check` — each exit 0. (completion-ledger's first run failed on the git-ignored `docs/verification/managed-conformance-manifest.json`; `npm run docs:generate` regenerated it, after which the check passes. Working tree stayed clean.) - `npm run verify:ghidra` (real Ghidra e2e) — not run: no Ghidra installation on this machine (see Remaining proof gaps). ## Compatibility, safety, and release - Breaking changes or migration steps: none. With the setting unset, launcher argv is byte-identical to before and the profile records `"ghidra-default"` as before. - Real Hopper/Ghidra, browser, or OS coverage: real Ghidra not available here; the report's Ghidra 12.1.4 controls cover the runtime behavior of the pre-script mechanism (`setAnalysisOption` in a pre-script) outside REA. Unit/boundary coverage covers everything REA adds around it. - Package or release metadata impact: `bridge/ghidra/ReaGhidraAnalysisOptions.java` added to the packaged file list and the packaged-Windows verifier manifest. - Security, privacy, process, or containment review: analyzer names are strictly whitelisted (length, count, character set) and injected as a single pre-script argument into the existing bridge `-scriptPath`; no shell interpolation, no new scripts sourced from user paths, no change to process cleanup. ## Review checklist - [x] This PR addresses a concrete problem or an agreed enhancement. - [x] The PR has one focused outcome and the title follows `type(scope): outcome`. - [x] Related issue is linked, or the reason for not linking one is stated above. - [x] Tests cover changed observable behavior and meaningful failure paths. - [x] Owning docs, contracts, and generated metadata are updated where needed. - [x] User-visible CLI/MCP changes include representative output. - [x] I checked the final diff for secrets, unrelated cleanup, and unsupported claims. Disclosure: this contribution is prepared with AI assistance (Claude), reviewed and verified by me (same disclosure as the issue claim comment). <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Added an option to disable selected Ghidra analyzers during analysis. Configure analyzer names as a comma-separated list; the setting is validated and applied before auto-analysis. - Analysis profiles record the selected analyzers. Sessions won’t open if their saved settings don’t match the current configuration. - **Documentation** - Documented the analyzer setting, accepted names and limits, and its effect: disabled analyzers won’t produce their usual analysis results. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-10-31 00:55:25 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
codex/procedure-reference-stacked
release-please--branches--main--components--rea-agents
release-please--branches--main--components--rea-agents--release-notes
codex/kuna-independent-retry
codex/byte-search-overlay-coverage
codex/open-failure-target-receipt
codex/kuna-xref-evidence
codex/ghidra-ambiguous-procedure-recovery
codex/function-source-bundle
codex/trace-function-integration-prototype
codex/snapshot-source-closure
codex/recorded-evidence-array-pages
codex/evidence-recovery-redesign
codex/trace-feature-address-scope
codex/call-discovery-scope
codex/ghidra-literal-candidate-evidence
codex/decompile-directory-independent-retry
codex/retry-provenance-base
codex/value-flow-capability-experiment
codex/ghidra-containing-instruction
cursor/readme-discord-button-ef9f
dependabot/github_actions/actions/setup-node-7.1.0
dependabot/github_actions/actions/upload-artifact-7.0.2
dependabot/npm_and_yarn/npm-minor-and-patch-d8d97ce6df
codex/kuna-1989
fix/8559-native-ui-fixture-ownership
fix/8555-go-verifier-mcp-ownership
codex/provider-capability-recovery
fix/8642-rizin-target-stdin
codex/ghidra-memory-effect-scope
codex/ghidra-annotation-entry-selector
codex/ghidra-readonly-recovery
codex/ghidra-regex-verifier-recovery
codex/evidence-discovery-view-guidance
fix/8545-bulk-append-overflow
fix/8428-navigation-refusal-alternatives
codex/address-context-recovery
codex/matching-member-limitations
codex/unknown-scope-contract
codex/evidence-view-guidance
feat/8373-native-trace-views
codex/ghidra-snapshot-verifier-binding
codex/elf-export-visibility
codex/evidence-view-recovery
codex/native-reference-cli-help
codex/provider-candidate-observation-scope
codex/kuna-session-verification
codex/ghidra-switch-lifetime-guidance
codex/pseudocode-paging-discovery
codex/clarify-evidence-view-support
codex/kuna-xrefs-selector-recovery
codex/context-capacity-recovery
codex/evidence-closure-large-links
codex/same-function-evidence-identity
codex/ghidra-verifier-inspected-jdk
codex/audit-guided-workflows
codex/crash-prompt-retained-dossiers
codex/analysis-view-error-recovery
codex/kuna-verifier-target-selection
codex/ghidra-selected-project-call-coverage
codex/docs-native-analysis-scope
codex/ghidra-java-socket-boundary
codex/ghidra-retained-snapshot-verifier
codex/ghidra-search-inventory-facts
fix/8284-zero-argument-parameter-bindings
fix/8198-ui-action-handler-offset
fix/8257-elf-entry-label-identity
fix/8304-deferred-output-schema-projection
fix/8277-call-path-computed-target-uncertainty
fix/pr-8089-conflicts
fix/ci-static-duplicate-export
dependabot/npm_and_yarn/lint-staged-17.6.0
dependabot/github_actions/actions/download-artifact-8.0.2
dependabot/npm_and_yarn/write-file-atomic-8.0.0
dependabot/npm_and_yarn/canonicalize-5.1.0
dependabot/github_actions/actions/cache/restore-6.1.0
dependabot/npm_and_yarn/toon-format/toon-4.4.0
dependabot/github_actions/actions/deploy-pages-5.0.1
codex/review-fixes-pr-2403
codex/review-fixes-pr-2400
codex/process-terminal-width
codex/test-brittleness-cleanup
verify/7167-browser-connect-macos
fix/7167-browser-connect
feat/native-matching-allowance-setting
feat/browser-scenario-dry-run
test/managed-caller-parameters-20261024
codex/parser-fortythird-boundaries
fix/6926-pinvoke-platform-decorations-20261023
fix/6889-har-body-encoding-20261023
fix/6888-sqlite-schema-budget-20261023
fix/dependency-security-gates-6708
cursor/evidence-overwrite-rebase-b4ac
feat/4057-verify-native-exports
fix/windows-acl-observer-overhead-20261022
cursor/erlang-beam-restack-4476
cursor/pe-certificate-review-bf32
fix/6116-javascript-application-fs-errors
fix/6061-unmapped-runtime-script-unknown
feat/browser-scenario-summary
fix/pe-certificates
codex/verify-3407
cursor/rebase-5699
cursor/rebase-5352
cursor/rebase-5600
cursor/fix-cli-schema-omission-10a8
codex/audit-hopper-shutdown-reasons-20261021
fix/demangle-swift-omitted-record
fix/nib-boolean-value-types
cursor/cancellation-partial-observation-a5ac
fix/ib-object-limit-reasons
fix/electron-fuse-limit-advice
fix/kuna-doctor-dangling-cache
fix/fixed-budget-refusal-advice
fix/js-ipc-listener-dedup
fix/js-return-member-provenance
fix/dmg-integrity-retry-advice
fix/ida-doctor-readiness
fix/kuna-version-probe-output-drain
fix/legacy-swift-runtime-name-matching
fix/dylib-lazy-load-commands
fix/browser-scenario-startup-cancel
fix/swift-nested-punycode-classification
fix/compare-unselected-scopes
fix/objc-method-budget-coverage
fix/dmg-mounted-root-observations
audit/ci-tests-20261019-round2
release/6.7.0
fix/wabt-cleanup-retry-resolution
fix/electron-fuse-elf-pe-architecture
fix/native-plist-descriptor-ownership
fix/kuna-caller-cleanup-ownership
experiment/atomic-codemode-20261016
review/first-contributor-3776
fix/call-resolution-full-read-cycles
fix/member-mutation-selection-repeat
experiment/atomic-re-tools-20261015
perf/member-mutation-lazy-origins
perf/static-network-mutation-index
fix/hopper-startup-lifecycle
audit/3050-windows-proof-20261015
feat/windows-window-capture-2183
audit/3049-windows-proof-20261015
audit/3735-macos-fixtures-20261015
fix/batch-decompile-null-pseudocode
fix/kuna-inventory-honors-jobs
experiment/browser-codemode-tool-design-20261015
fix/hopper-clean-runtime-argv
codex/review-2049-27f1b367
review-fixes/pr-2787-routing
fix/3360-scoped-this-emitters
fix/3367-replaced-global-effects
fix/3838-compact-any-value-items
test/hopper-download-probe-20261015
codex/windows-runtime-creation-red-green-20261015
codex/windows-readonly-root-red-green-20261015
codex/windows-root-share-red-green-20261015
codex/exp-1685-win-mcp-startup
codex/bug-sweep-20261015
investigate/2190-windows-package-phases
investigate/3543-macos-cli-deadline
perf/3281-reverse-tools-feedback-quality
fix/3406-hopper-doctor-fixture
fix/3341-wrapper-require-test-context
fix/3301-owned-uninstall-fixtures
fix/3164-compiler-input-ownership
fix/pcap-cleanup-stdout-newline-20261014
perf/interface-builder-summary
codex/review-fixes-pr-1977
fix/ghidra-effective-jvm-platform
fix/docs-turkish-rust-link-20261013
fix/main-maintenance-ci-20261010
fix/recover-binary-session-process-effects
codex/review-fixes-pr-2457
codex/ci-required-cancellation-gate
fix/main-format-baseline-20261013
fix/setup-preserve-entry-fields
cursor/restore-main-checks-1ffc
fix/ghidra-bridge-hashmap-import
codex/shared-ci-jadx-json-default-20261013
codex/shared-ci-ghidra-test-groups-20261013
codex/shared-ci-java-fixture-format-20261013
codex/fix-intrinsic-invocation-boundaries
test/release-preflight-reusable-jobs
test/js-parameter-provenance-expectation
fix/linux-hopper-verification-current
test/2419-ghidra-elf-probe-size
followup/pr-1544-native-ida
codex/fold-pr-2230-contribution
docs/readme-responsible-use
fix/issue-2064
fix/issue-2050
fix/issue-2053
fix/issue-1968
fix/issue-1945
experiment/codemode-bridge-20261011
fix/tool-effects-negative-wording-1904-20261012
fix/1842-electron-interop-provenance
feat/recover-javascript-multi-input
refactor/website-i18n-prep
fix/nativeaot-pe-virtual-extent
fix/browser-verifier-ci-hang
fix/pe-resources-input-selection
docs/beginner-friendly-guides
docs/beginner-setup-guide
fix/javascript-analysis-worker-1563
fix/1649-ghidra-duplicate-names
fix/javascript-export-keys-integration-1369
test/maintenance-boundary-contracts-20261011
review/javascript-export-keys-1369
review/process-live-progress-1483
test/javascript-1495-growth-ratio
fix/ci-escape-timing
docs/normalized-terminal-geometry-1450
release/6.3.0
archive/release-6.3.0-pr1381
release/6.2.0
fix/electron-preload-dynamic-override
fix/javascript-self-referential-bundler-edges
release/6.1.0
cursor/grok-client-cherry-pick-0b56
feat/signature-posture
feat/dyld-shared-cache
feat/artifact-integrity-policy
feat/pkg-inventory
release/6.0.0
chore/sync-release-5.0.0
release/5.0.0
cursor/cloud-agent-node-787e
fix/javascript-xhr-open-endpoints
review/pr-711-realpath-fallback-wording
cleanup/replay-confinement
codex/test-suite-performance
codex/issue-foundations
codex/address-open-issues-2026-07-20
agent/javascript-vite-rollup-esbuild-adapters
agent/process-cleanup
agent/triage-integration
agent/unknown-commands-registry
feat/mcp-identity-metadata
morlvps/issue_cleanup
codex/installer-redesign
morl/roadmap-investigation-core
morl/roadmap-investigation-docs
release-please--branches--main--components--rea
rea-agents-6.8.0
rea-agents-6.7.0
rea-agents-6.6.0
experiment/atomic-codemode-wait-runtime-20261016
rea-agents-6.5.0
rea-agents-6.4.0
rea-agents-6.3.0
rea-agents-6.2.0
rea-agents-6.1.0
rea-agents-6.0.0
rea-agents-5.0.0
rea-agents-4.1.0
rea-agents-4.0.1
rea-agents-4.0.0
rea-agents-3.2.1
rea-agents-3.2.0
rea-agents-3.1.0
rea-agents-3.0.0
rea-agents-2.7.0
rea-agents-2.6.0
rea-agents-2.5.1
rea-agents-2.5.0
rea-agents-2.4.0
rea-agents-2.3.0
rea-agents-2.2.0
rea-agents-2.1.0
rea-agents-2.0.0
rea-agents-1.7.0
rea-agents-1.6.0
rea-agents-1.5.0
rea-agents-1.4.0
rea-agents-1.3.0
rea-agents-1.2.0
rea-agents-1.1.0
rea-agents-1.0.0
rea-agents-0.5.0
rea-agents-0.4.0
rea-agents-0.3.0
rea-0.2.1
rea-0.2.0
Labels
Clear labels   
area: bridge

   
area: bridge

   
area: build

   
area: build

   
area: build

   
area: cli

   
area: domain

   
area: evidence

   
area: mcp

   
area: native

   
area: providers

   
area: runtime

   
area: server

   
area: setup

   
area: tests

   
bug

   
design

   
documentation

   
enhancement

   
enhancement

   
enhancement

   
experiment

   
help wanted

   
i18n

   
invalid

   
P0: critical

   
P1: high

   
P2: medium

   
P2: medium

   
P2: medium

   
P3: low

   
performance

   
provider-request

   
pull-request
Mirrored from GitHub Pull Request

  
question

   
roadmap

   
triage
No labels
area: bridge
area: bridge
area: build
area: build
area: build
area: cli
area: domain
area: evidence
area: mcp
area: native
area: providers
area: runtime
area: server
area: setup
area: tests
bug
design
documentation
enhancement
enhancement
enhancement
experiment
help wanted
i18n
invalid
P0: critical
P1: high
P2: medium
P2: medium
P2: medium
P3: low
performance
provider-request
pull-request
question
roadmap
triage
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
morluto/rea#4825
No description provided.