|Project Name||Stars||Downloads||Repos Using This||Packages Using This||Most Recent Commit||Total Releases||Latest Release||Open Issues||License||Language|
|Shadowsocks Qt5||7,866||4 years ago||75||lgpl-3.0||C++|
|A cross-platform shadowsocks GUI client|
|V2rayx||7,184||6 months ago||116||gpl-3.0||Objective-C|
|GUI for v2ray-core on macOS|
|Core||2,607||21 hours ago||178||bsd-2-clause||PHP|
|OPNsense GUI, API and systems backend|
|Zan Proxy||1,378||2||4 years ago||1||January 17, 2019||18||mit||TypeScript|
|An extensible proxy for PC/Mobile/APP developer|
|Clashy||1,200||a year ago||38||mit|
|A GUI proxy client for Windows / Mac / Ubuntu Desktop based on Clash and Electron. Windows / Mac / Ubuntu 适用的Clash客户端.|
|Koolshare Clash||873||3 years ago||41||gpl-3.0||ASP|
|:cat: Run Clash Tunnel on Koolshare OpenWrt|
|Youtube Dl Wpf||662||5 days ago||5||gpl-3.0||C#|
|A simple GUI wrapper for youtube-dl and yt-dlp.|
|Engintron||653||14 days ago||49||gpl-2.0||Perl|
|Engintron for cPanel/WHM is the easiest way to integrate Nginx on your cPanel/WHM server. Engintron will improve the performance & web serving capacity of your server, while reducing CPU/RAM load at the same time, by installing & configuring the popular Nginx webserver to act as a reverse caching proxy in front of Apache.|
|Frpmgr||515||10 days ago||9||apache-2.0||Go|
|Windows 平台的 FRP GUI 客户端 / A user-friendly desktop GUI client for FRP on Windows.|
|Furious||280||2 days ago||gpl-3.0||Python|
|A PySide6-based cross platform GUI client that launches your beloved GFW to outer space. Support Xray-core and hysteria.|
The OPNsense project invites developers to start contributing to the code base. For your own purposes or – even better – to join us in creating the best open source firewall available.
The build process has been designed to make it easy for anyone to build and write code. The main outline of the new codebase is available at:
Our aim is to gradually evolve to a new codebase instead of using a big bang approach into something new.
To create working software like OPNsense you need the sources and the tools to build it. The build tools for OPNsense are freely available.
Notes on how to build OPNsense can be found in the tools repository:
You can contribute to the project in many ways, e.g. testing functionality, sending in bug reports or creating pull requests directly via GitHub. Any help is always very welcome!
You can learn more about contributing on CONTRIBUTING.md.
OPNsense is and will always be available under the 2-Clause BSD license:
Every contribution made to the project must be licensed under the same conditions in order to keep OPNsense truly free and accessible for everybody.
The repository offers a couple of targets that either tie into tools.git build processes or are aimed at fast development.
A package of the current state of the repository can be created using this target. It may require several packages to be installed. The target will try to assist in case of failure, e.g. when a missing file needs to be fetched from an external location.
Several OPTIONS exist to customise the package, e.g.:
Options are passed in the following form:
# make package CORE_NAME=my_new_name
In general, options are either set to sane defaults or automatically detected at runtime.
Update will pull the latest commits from the current branch from the upstream repository.
Upgrade will run the package build and replace the currently installed package in the system.
Fetch changes from the running system for all known files.
Run several syntax checks on the repository. This is recommended before issuing a pull request on GitHub.
Run the PSR12 and PEP8 style checks on MVC PHP code and Python,
For php code you will need to have
You can use the package
php-codesniffer on Debian/Ubuntu.
Python code will require
For easier development you may want to use an OPNsense VM and run:
pkg install os-debug that will install all the necessary tools.
Run Linux Kernel cleanfile whitespace sanitiser on all files.