lazy-luo/smargate

内网穿透,c++实现,无需公网IP,小巧,易用,快速,安全,最好的多链路聚合(p2p+proxy)模式,不做之一...这才是你真正想要的内网穿透工具!

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 1 hour ago
Added to GitGenius on September 15th, 2026
Created on November 6th, 2018
Open Issues & Pull Requests: 1 (+0)
GitHub issues: Enabled
Number of forks: 468
Total Stargazers: 4,358 (+0)
Total Subscribers: 64 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 0.0 hours
Mean response time: 11.0 hours
90th percentile: 2.2 days
Tracked items: 8

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 1
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 328 days
Stale 30+ days: 1
Stale 90+ days: 1

Recent activity

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

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Smargate is an intranet penetration tool that enables access to private networks without requiring a public IP address.

The tool solves the problem of exposing services on private networks to external access by implementing a multi-path aggregation approach that combines peer-to-peer and proxy modes. This dual-mode strategy allows traffic to flow through either direct P2P connections when available or fall back to proxy routing, providing flexibility in how connections are established and maintained across network boundaries.

The tool is designed for users who need lightweight, straightforward intranet penetration without the complexity of managing public IP infrastructure. It suits scenarios where services need to be accessible from outside a private network but where traditional solutions requiring public IPs are impractical or unavailable. The project emphasizes being compact, easy to use, and fast, making it appropriate for both simple and complex network setups.

Development activity shows consistent engagement with the codebase through regular commits addressing various aspects of the tool. The project maintains active responsiveness to issues raised by users, indicating ongoing attention to problems and feature requests. Pull requests are regularly reviewed and integrated, demonstrating a workflow that incorporates external contributions. The maintainer actively pushes updates that span bug fixes, optimizations, and feature additions, suggesting sustained investment in the tool's evolution and reliability.