jonathansalwan/triton

Triton is a dynamic binary analysis library. Build your own program analysis tools, automate your reverse engineering, perform software verification or just...

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 43 minutes ago
Added to GitGenius on September 16th, 2026
Created on January 25th, 2015
Open Issues & Pull Requests: 36 (+0)
GitHub issues: Enabled
Number of forks: 598
Total Stargazers: 4,302 (+0)
Total Subscribers: 130 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 16.4 hours
Mean response time: 25.0 days
90th percentile: 112.4 days
Tracked items: 48

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 8
New in 7 days: 0
Closed in 7 days: 2
Avg open age: 403 days
Stale 30+ days: 8
Stale 90+ days: 7

Recent activity

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

Top labels

  • Help & Info (9)
  • libTriton (6)
  • Bindings (2)
  • Bug (2)
  • Compile (2)
  • Enhancement (2)
  • AST Lifting (1)
  • External tool (1)

Most active issues this week

Detailed Description

Triton is a dynamic binary analysis library that enables developers to build custom program analysis tools, automate reverse engineering workflows, perform software verification, and emulate code execution.

The library addresses the need for flexible binary analysis by providing a unified framework that combines multiple analysis techniques. It supports symbolic execution to explore program paths and reason about code behavior, taint analysis to track data flow through programs, instruction semantics to understand what code actually does, and binary translation to lift machine code into intermediate representations. These capabilities work together to let analysts understand, verify, and manipulate compiled binaries without access to source code.

Triton suits security researchers, reverse engineers, and verification engineers who need to analyze compiled binaries deeply. It works well for deobfuscation tasks, automated vulnerability discovery, and understanding obfuscated or proprietary code. The library is particularly valuable when you need to combine multiple analysis techniques—symbolic execution alone or taint analysis alone often cannot answer complex questions about program behavior, but Triton's integrated approach handles these scenarios. Teams building custom analysis tools will find the library more flexible than monolithic analysis platforms, since it provides the building blocks to assemble exactly the analysis pipeline required for their problem.

The project shows sustained development with regular commits addressing bug fixes, feature additions, and improvements to the symbolic execution engine and instruction semantics. Maintenance activity indicates ongoing attention to core functionality and compatibility with evolving binary formats and architectures. The codebase receives updates that expand supported instruction sets and refine the accuracy of instruction-level analysis. Documentation and examples are maintained alongside code changes, suggesting the maintainers support practical adoption by new users.