archeb/opentrace

Open Source Visualized Route Tracing Tool for macOS, Windows, and Linux.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 57 minutes ago
Added to GitGenius on September 15th, 2026
Created on May 23rd, 2023
Open Issues & Pull Requests: 9 (+0)
GitHub issues: Enabled
Number of forks: 187
Total Stargazers: 4,445 (+0)
Total Subscribers: 14 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 11.8 hours
Mean response time: 66.7 days
90th percentile: 335.3 days
Tracked items: 39

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: 0
Avg open age: 403 days
Stale 30+ days: 7
Stale 90+ days: 7

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 (19)
  • bug (10)
  • help wanted (2)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

OpenTrace is a cross-platform visualized route tracing tool for macOS, Windows, and Linux.

OpenTrace solves the problem of performing network route tracing with a graphical interface rather than command-line tools. It wraps the NextTrace backend to provide MTR (My Traceroute) functionality and traditional traceroute capabilities. The tool displays routing information visually across different operating systems using native platform interfaces: WPF on Windows, GTK on Linux, and native macOS app bundles.

The tool suits network administrators and developers who need to diagnose network paths and latency but prefer a graphical interface. Windows users performing TCP/UDP traceroute need to install Npcap separately. The project supports custom DNS resolvers including DNS over HTTPS, integrates Cloudflare verification for NextTrace API tokens, and includes a local MMDB database option. Multi-language support covers English, Chinese, French, Spanish, Japanese, and Russian. Users can invoke traces from the command line and access beta builds through the project's Actions page.

Development activity shows consistent engagement with feature implementation across multiple platforms. The project maintains native platform-specific code paths rather than using cross-platform UI frameworks, indicating deliberate architectural choices for each operating system. Build infrastructure is documented for all three target platforms with platform-specific output directories and signing workflows for macOS distribution. The README explicitly welcomes feature requests, suggesting active consideration of user input for future development.