[GH-ISSUE #7095] [Feature] Add integration for the Binary Ninja tool #4273

Closed
opened 2026-10-31 00:48:23 +00:00 by bsakaguchi · 4 comments
Owner

Originally created by @trgchinhh on GitHub (Oct 25, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/7095

Before submitting

  • I searched the open and closed issues and pull requests for a related proposal.
  • I understand the contribution scope must be reviewed before integration; open questions are welcome here.
  • This request does not include credentials, private samples, or sensitive target data.

Area

Not sure yet

Current limitation

I hope you will add Binary Ninja to REA, as it is a quite powerful reverse engineering tool on par with Ghidra, IDA, or Hopper

Use cases

No response

Desired outcome and success criteria

I hope you will add Binary Ninja to REA, as it is a quite powerful reverse engineering tool on par with Ghidra, IDA, or Hopper

Expected interaction with targets

Not sure yet

Target and scope details (optional)

No response

Verification available so far

Idea only; I need help defining checks

Verification details (optional)

No response

Alternatives considered

No response

Possible direction

No response

References

No response

Originally created by @trgchinhh on GitHub (Oct 25, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/7095 ### Before submitting - [x] I searched the open and closed issues and pull requests for a related proposal. - [x] I understand the [contribution scope](https://github.com/morluto/rea/blob/main/CONTRIBUTING.md#contribution-scope) must be reviewed before integration; open questions are welcome here. - [x] This request does not include credentials, private samples, or sensitive target data. ### Area Not sure yet ### Current limitation I hope you will add Binary Ninja to REA, as it is a quite powerful reverse engineering tool on par with Ghidra, IDA, or Hopper ### Use cases _No response_ ### Desired outcome and success criteria I hope you will add Binary Ninja to REA, as it is a quite powerful reverse engineering tool on par with Ghidra, IDA, or Hopper ### Expected interaction with targets Not sure yet ### Target and scope details (optional) _No response_ ### Verification available so far Idea only; I need help defining checks ### Verification details (optional) _No response_ ### Alternatives considered _No response_ ### Possible direction _No response_ ### References _No response_
bsakaguchi 2026-10-31 00:48:23 +00:00
Author
Owner

@XinwangTao commented on GitHub (Oct 25, 2026):

Binary Ninja 确实值得加入 REA 的逆向工具矩阵。它的 Python SDK 和 headless 模式与现有 Ghidra/Hopper provider 的接入方式契合,而且对中型二进制和非常见架构的分析体验很好,能补上 Ghidra 启动重、Hopper 平台受限之间的空档。建议先按现有 provider 接口做只读的基础能力(函数列表、反编译、注释读写),再逐步对齐高级特性。支持这个方向。

<!-- gh-comment-id:6395202711 --> @XinwangTao commented on GitHub (Oct 25, 2026): Binary Ninja 确实值得加入 REA 的逆向工具矩阵。它的 Python SDK 和 headless 模式与现有 Ghidra/Hopper provider 的接入方式契合,而且对中型二进制和非常见架构的分析体验很好,能补上 Ghidra 启动重、Hopper 平台受限之间的空档。建议先按现有 provider 接口做只读的基础能力(函数列表、反编译、注释读写),再逐步对齐高级特性。支持这个方向。
Author
Owner

@trgchinhh commented on GitHub (Oct 25, 2026):

Thank you so much

<!-- gh-comment-id:6396113364 --> @trgchinhh commented on GitHub (Oct 25, 2026): Thank you so much
Author
Owner

@XinwangTao commented on GitHub (Oct 25, 2026):

Binary Ninja would be a strong addition — its headless scripting (bnil, linear/medium-level IL) maps well onto REA's existing analysis lanes. Two considerations for scoping: (1) decide the boundary early — a thin wrapper around the Python API (like the Ghidra bridge) vs. a native headless mode, since licensing/headless availability differ from Ghidra; (2) align the capability matrix with the existing providers (open_binary/search_strings/decompile etc.) so the admission boundary and provider selection stay uniform. Happy to help flesh out the integration checklist if that's useful.

<!-- gh-comment-id:6399655607 --> @XinwangTao commented on GitHub (Oct 25, 2026): Binary Ninja would be a strong addition — its headless scripting (bnil, linear/medium-level IL) maps well onto REA's existing analysis lanes. Two considerations for scoping: (1) decide the boundary early — a thin wrapper around the Python API (like the Ghidra bridge) vs. a native headless mode, since licensing/headless availability differ from Ghidra; (2) align the capability matrix with the existing providers (open_binary/search_strings/decompile etc.) so the admission boundary and provider selection stay uniform. Happy to help flesh out the integration checklist if that's useful.
Author
Owner

@morluto commented on GitHub (Oct 26, 2026):

Thanks for suggesting Binary Ninja support. This overlaps the earlier request in #1551, where the GUI MCP and headless approaches and their different licensing and lifecycle boundaries are already being discussed. I am closing this duplicate so the discussion stays together. The related proposals #5794 and #7041 are open and still await the required scope decisions; support has not landed. Please reopen if there is a distinct use case the earlier issue misses.

<!-- gh-comment-id:6428348563 --> @morluto commented on GitHub (Oct 26, 2026): Thanks for suggesting Binary Ninja support. This overlaps the earlier request in #1551, where the GUI MCP and headless approaches and their different licensing and lifecycle boundaries are already being discussed. I am closing this duplicate so the discussion stays together. The related proposals #5794 and #7041 are open and still await the required scope decisions; support has not landed. Please reopen if there is a distinct use case the earlier issue misses.
Sign in to join this conversation.
No milestone
No project
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#4273
No description provided.