google/bindiff

Quickly find differences and similarities in disassembled code

View on GitHub ↗Jump to charts ↓Open shareable report →

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Added to GitGenius on September 21st, 2026
Created on September 20th, 2023
Open Issues & Pull Requests: 53 (+0)
GitHub issues: Enabled
Number of forks: 244
Total Stargazers: 3,201 (+0)
Total Subscribers: 33 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 5.8 hours
Mean response time: 38.9 days
90th percentile: 22.6 days
Tracked items: 30

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 23
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 572 days
Stale 30+ days: 22
Stale 90+ days: 21

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • enhancement (15)
  • bug (7)
  • question (5)
  • duplicate (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

BinDiff is a binary diffing tool that identifies differences and similarities between disassembled code.

The tool addresses the challenge of comparing compiled binaries by analyzing their disassembled representations to find what has changed between versions. It works by matching functions and basic blocks across two binaries, then visualizing the differences in a way that makes it easy to spot modifications, additions, and removals. This approach is particularly useful when source code is unavailable or when you need to understand what changed at the binary level.

BinDiff suits reverse engineers, security researchers, and developers who need to track changes in compiled software. It is especially valuable for vulnerability analysis, patch assessment, and malware research where understanding binary-level differences is critical. The tool integrates with IDA Pro as a plugin, making it accessible within an existing reverse-engineering workflow. Organizations maintaining legacy systems or analyzing third-party binaries will find it essential for determining what has actually changed between releases.

The project shows active maintenance with regular updates addressing bugs and compatibility issues. Development includes ongoing refinement of the matching algorithms that power the diffing engine. The codebase receives attention to keep pace with changes in the tools and platforms it depends on.