Licentivo Launch SDKs

Version 0.1.6 is distributed through the GitHub Release assets below. Check publication status for package registry availability.

Website · Documentation · Source code

Account login and license-protected application operations in Go, Python, C#, Java, JavaScript/TypeScript, Rust, Ruby, C and C++. MIT licensed.

Install only the Launch package for your language. Each package embeds the reviewed Licentivo SDK 0.11.6 and manages its adapter and SDK linking. Ordinary language dependencies still use their package manager.

The Launch merchant address is required at initialization. Select your existing software in Launch → 程序接入 → 接入检查与代码 to copy a connection function with the address, existing product mapping and public signing keys already filled in. The licensing service is fixed to https://www.licentivo.com. No client configuration file or manual entry of two internal product IDs is required.

Version: 0.1.6, with official SDK 0.11.6. The commands below target this release. Publication and fresh-consumer results are recorded in publication status and verification receipts; the 0.1.6 release record describes this update.

This update strengthens account logout persistence, restore coordination and the matching official runtime protections across all nine languages. Install one Launch package; it includes its reviewed Licentivo runtime.

Go requires 1.26+, Python 3.10+, .NET 8+, Java 17+, Node.js 20.3+, Rust 1.85+, Ruby 3.1+, C11 or C++17. Native packages must match the compiler ABI. Windows GNU/MinGW is the qualified native toolchain; other platforms require their normal curl/OpenSSL development libraries when building from source.

The manual nine-language guide covers installation, direct initialization, login, feature guards, restore, logout, device release, secure stores and errors. Each language has its own README and runnable examples. AI is optional; Launch's English prompts describe the same APIs and automatically filled parameters.

Initialization does not authorize a protected operation. Log in with the customer's merchant account, then execute protected business code through the package's feature guard. Preserve the SDK lifecycle for heartbeats and use only verified, policy-valid grants for offline operation. Explicit denial must not fall back to offline authorization.

The Launch server manages merchant accounts, payments and entitlement delivery. This repository contains client libraries, public examples and release tools. It contains no server startup configuration, merchant credentials or payment keys.

See maintainer release instructions. Public registry installation checks and local signed SDK fixtures do not establish external merchant/payment/license acceptance; see acceptance procedures.