hasherezade/pe-bear

Portable Executable reversing tool with a friendly GUI

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 1 hour ago
Added to GitGenius on September 18th, 2026
Created on September 18th, 2022
Open Issues & Pull Requests: 16 (+0)
GitHub issues: Enabled
Number of forks: 246
Total Stargazers: 3,810 (+0)
Total Subscribers: 45 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 13.9 hours
Mean response time: 31.3 days
90th percentile: 11.3 days
Tracked items: 20

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 5
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 475 days
Stale 30+ days: 4
Stale 90+ days: 3

Recent activity

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

Top labels

  • bug (3)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

PE Bear is a portable executable reversing tool with a graphical user interface.

The tool addresses the need to inspect, analyze, and modify Windows PE files during malware analysis and reverse engineering work. It provides a GUI-based approach to examining PE file structure, which makes the task more accessible than command-line alternatives. The tool handles the complexity of PE format parsing and presentation, allowing analysts to navigate file sections, headers, imports, exports, and other structural elements visually.

Analysts performing malware triage, vulnerability research, or general reverse engineering should consider PE Bear when they need interactive exploration of PE files without switching between multiple specialized tools. The project suits workflows where visual inspection of executable structure is preferable to scripting or hex editing. The tool's multiplatform support means it can run across different operating systems, reducing friction for teams with heterogeneous environments.

Development activity shows consistent engagement with the codebase. The project receives regular updates that address bugs and add refinements to existing functionality. Maintenance efforts focus on stability and incremental improvements rather than major architectural shifts. The tool maintains active responsiveness to issues raised by users, indicating ongoing attention to practical problems encountered in the field.