nps

ehang-io/nps

一款轻量级、高性能、功能强大的内网穿透代理服务器。支持tcp、udp、socks5、http等几乎所有流量转发,可用来访问内网网站、本地支付接口调试、ssh访问、远程桌面,内网dns解析、内网socks5代理等等……,并带有功能强大的web管理端。a lightweight, high-performance, powerful intranet penetration proxy server, with a powerful web management terminal.

Ship status

Gone silent

No push in over 120 days. A quiet repo may also be a finished one.

Last push
May 30, 2024
855 days ago
Stars, last 7 weeks
Stars, weekly: 34,165 → 34,237 (Aug 18 – Sep 29, 2026)
+46 stars in the 28 days to 2026-09-29

Shipping: pushed in the last 30 days · slowed: quiet for 31–120 days · silent: no push in over 120 days.

Repo facts

What GitHub reports.

Stars
34.2K
Forks
6.1K
Open issues
527
Watchers
471
Primary language
Go
Created
Nov 4, 2018
Owner
ehang-io · Organization

Open issues are the issues and pull requests GitHub reports as open; watchers are the accounts subscribed to the repository. OSI-approved license — GitHub’s own license field, not legal advice. 99 startups in the directory ship primarily in Go.

Topics

#dns#firewall#go#gzip#http#https#nat#nps#snnapy#socks#socks5#ssh#tcp#tunnel#udp

How it got here

What the classifier decided, and when.

Classified as an open-source startup by Jev, TypeSafe’s classifier, on Sep 22, 2026 — os_startup 74%, self-hostable 90%, hosted offering 43%. The classifier reads only the repository’s name, description and homepage; it can be wrong, and a probability under 0.5 puts a listing in the review queue rather than out of the directory.

Listed since the 2025-09 crawl. Answered by jev-1.13.0. How the classification works →

Embed your status

Put this badge on your README.

OSSEAN ship status: silent — last push 2024-05-30This is the badge for ehang-io/nps, as served from the URL below.
[![OSSEAN: silent](https://ossean.com/badge/ehang-io/nps.svg)](https://ossean.com/ehang-io/nps)

Updates daily, from the last push GitHub saw.

Honest caveat: GitHub proxies README images through Camo and rewrites the anchor with rel=“nofollow”, so a README embed sends you referral traffic and brand, not link equity. The link is dofollow wherever you control the markup — your docs, your landing page, your blog. The snippet uses your frozen OSSEAN slug, so it survives a repo rename.