Third-party Libraries

Third-Party Licenses - Happ Android

Core Libraries (AndroidX, Google, Kotlin, System)

Networking, Security & Storage Libraries

Legacy / Rx / UI Utility Libraries

External Tools (Bundled / Runtime Dependencies)

Summary by License Type

License Compliance Notes

MPL 2.0 (Xray-core)

• Requires providing access to modified Xray-core source code if distributed.
• Does not affect your proprietary application code.
• Include MPL 2.0 license text in your distribution.

Apache 2.0 (Most Dependencies)

• Requires preserving copyright notice.
• Requires including license text.
• Patents grant included.

MIT (java-jwt, Sentry)

• Very permissive.
• Only attribution required.

BSD-3 (MMKV)

• Permissive; attribution required.

EPL 1.0 (JUnit)

• Test-only dependency; no runtime distribution obligations.

Full License Texts

• Apache 2.0 — https://www.apache.org/licenses/LICENSE-2.0
• MIT — https://opensource.org/licenses/MIT
• BSD-3 Clause — https://opensource.org/licenses/BSD-3-Clause
• EPL 1.0 — https://www.eclipse.org/legal/epl-v10.html
• MPL 2.0 — https://www.mozilla.org/en-US/MPL/2.0/

Last updated: 2025-12-01

Third-Party Licenses - Happ iOS

Core Libraries (iOS)

Networking & System Tools

Summary by License Type

License Compliance Notes

MIT License (DeviceKit, SwiftyJSON, SwiftyPing)

• Very permissive license.
• Requires including copyright notice and the full license text.
• No copyleft requirements.

BSD-3 Clause License (BadVPN)

• Similar to MIT, permissive.
• Requires inclusion of license text and copyright.
• Allows static or dynamic linking without obligations on your own code.

Mozilla Public License 2.0 (Xray-core)

• A file-level copyleft license.
• You must include MPL 2.0 license text in your distribution.
• If you modify Xray-core source code, only the modified files must be published.
• Your main proprietary application code is not affected as long as Xray-core is used as a separate component.

Full License Texts

• MIT License — https://opensource.org/licenses/MIT
• BSD-3 Clause License — https://opensource.org/licenses/BSD-3-Clause
• Mozilla Public License 2.0 — https://www.mozilla.org/en-US/MPL/2.0/

Last updated: 2025-12-01

Third-Party Licenses - Happ Desktop

Core Libraries (Bundled/Linked)

External Tools (Downloaded & Bundled at Build Time)

Build & Deployment Tools

Summary by License Type

License Compliance Notes

Copyleft Licenses (Require Attention)

sing-box (GPL v3+)

The GPL requires that if you distribute binaries, you must offer source code. Since sing-box is distributed as a separate executable (not linked), your application code is NOT affected, but you must:

• Include GPL license text
• Provide/offer source code access for sing-box

Mullvad Split Tunnel (GPL v3)

Same requirements as sing-box.

Xray-core (MPL 2.0)

More permissive than GPL. You must:

• Include MPL license text
• Make source code available for any modifications to Xray-core itself

Qt 6 (LGPL v3)

You must:

• Use dynamic linking (DLLs/.so files) - already implemented
• Provide Qt source code or link to it
• Include LGPL license text
• Allow users to relink with different Qt version

Permissive Licenses (Minimal Obligations)

Apache 2.0 (OpenSSL, QZXing, xpack)

• Include license and copyright notices

MIT (SingleApplication, tun2proxy, byedpi, linuxdeploy)

• Include license and copyright notices

Full License Texts

For full license texts, please refer to the following:

• Apache 2.0: https://www.apache.org/licenses/LICENSE-2.0
• MIT: https://opensource.org/licenses/MIT
• LGPL v3: https://www.gnu.org/licenses/lgpl-3.0.html
• GPL v3: https://www.gnu.org/licenses/gpl-3.0.html
• MPL 2.0: https://www.mozilla.org/en-US/MPL/2.0/

Last updated: 2025-12-01