Confeature SDKs and CLI

The client SDKs and the command-line tool for Confeature, the hosted feature-flag service. Every SDK is a drop-in replacement for the matching ConfigCat SDK: same method names, same options, same polling and cache behaviour. Moving from ConfigCat means changing the base URL, or the SDK key, and nothing else.

Everything here is MIT-licensed (see LICENSE). All 21 SDKs, the shared evaluation engine and the wire-case corpus they are tested against live in this one repository, so a change to the evaluation rules is tested across every language at once.

The JVM repository. Confeature's JVM SDKs are served from maven.confeature.io, not Maven Central. Add the repository once, next to the ones your build already uses:

// build.gradle.kts, or dependencyResolutionManagement in settings.gradle.kts
repositories {
    mavenCentral()
    maven { url = uri("https://maven.confeature.io") }
}

<!-- pom.xml -->
<repositories>
  <repository>
    <id>confeature</id>
    <url>https://maven.confeature.io</url>
  </repository>
</repositories>

Every published file carries Maven checksums and a GitHub artifact attestation: gh attestation verify <file> --repo confeature/sdks checks one.

The PHP and Swift SDKs are published from read-only mirrors of their directories here, confeature/confeature-php-sdk and confeature/confeature-swift: Packagist and Swift Package Manager read a repository whose manifest sits at its root. Changes are made here, in apps/sdk-php/ and apps/sdk-swift/.

Each SDK's own README, under apps/sdk-<name>/, covers its options, its examples and the details of moving from ConfigCat.

The confeature CLI manages flags from a terminal. It installs from cli.confeature.io:

# macOS and Linux
curl --proto '=https' --tlsv1.2 -fsSL https://cli.confeature.io/install.sh | sh

# Windows
irm https://cli.confeature.io/install.ps1 | iex

Its source is in apps/cli.

• apps/sdk-<name>/: one SDK per directory, each built and tested with its own language's toolchain.
• apps/cli/: the CLI, a Deno project.
• packages/sdk-shared/: the evaluation engine the JavaScript SDKs share.
• packages/test-fixtures-sdk-parity/: the wire-case and parity corpus every SDK replays.
• packages/contract/: a read-only copy of the published API contract.
• tools/test-harness-live-contract/: a local reference server the SDKs' live suites run against.
• dagger/: the containerised test pipeline for every SDK.

Every push to main and every pull request runs two required checks:

• pnpm run verify (.github/workflows/verify.yml) runs the repository's own gates and the CLI's suite.
• sdk gates (.github/workflows/sdk-gates.yml) runs each SDK's own suite, which includes its API-surface conformance test against the official ConfigCat SDK, the parity corpus and the wire-case corpus. It also runs the SDK's live suite against the local reference origin.
  • Linux SDKs run through their Dagger function.
  • Swift runs natively on macOS.
  • Unreal has no engine on hosted runners, so it gets a labelled source-quality smoke instead of a build.
  • Which SDKs run: a pull request runs only the SDKs it touches, plus the SDKs that depend on them. A push to main, and a daily run, judge all 21.

See CONTRIBUTING.md. To report a vulnerability, see SECURITY.md, and do not open a public issue.

MIT, copyright MakerLabs. See LICENSE.