Thanks for your interest in improving InHive — a free, open-source VPN client and proxy core for censorship circumvention.
InHive is split across several repositories:
| Repo | What |
|---|---|
| inhive-core | Go proxy engine (sing-box fork) — builds the library consumed by the apps |
| inhive-android / windows / ios / macos | Release binaries + platform notes |
| utproto | Standalone FakeTLS transport library |
| inhive-rules | Compiled .srs blocklists |
The client app source lives in a separate product repository; the public app is distributed via the release mirrors above and at app.inhive.ru.
- Open an issue first for anything non-trivial — describe the problem or proposal before writing code, so we can align on direction.
- Fork and branch from the default branch.
- Keep changes focused — one logical change per pull request.
- Match existing style — read the surrounding code; consistency over personal preference.
- Test your change — describe how you verified it in the PR.
Use the issue templates. Include your platform, app/core version, and clear reproduction steps. For VPN connectivity issues, a sanitized log (no secrets, no real server addresses) helps enormously.
Do not file security vulnerabilities as public issues — see SECURITY.md.
By contributing, you agree your contributions are licensed under the same license as the repository you contribute to (GPL-3.0-or-later for the core).