Downloads

CKey packages for Swift, the web, Android, .NET, C and C++, and the command line. Every file is listed with its SHA-256 checksum, so you can check it before you use it.

CKey packages are open source under the MIT licence. This website is proprietary and isn’t covered by it.

Release files

Checking for a published release…

Loading the release list…

Install

No CKey package is in a public registry yet. Until one is, install from the release files above, replacing VERSION with the version they list, or build from source.

  • Swift Package Manager

    iOS 15 and macOS 12 or later. In Xcode, choose File, Add Package Dependencies, and enter the repository URL.

    .package(url: "https://github.com/clearkeysolutions/ckey", from: "0.1.0"),
    .target(name: "MyApp", dependencies: [.product(name: "CKey", package: "ckey")]),
  • npm, for the web

    An ES module with the WebAssembly core, for browsers, workers and Node 22.

    npm install ./ckey-VERSION.tgz     # from the release files
    npm install ckey                   # once it is published
  • Maven, for Android

    Unzip the Maven repository from the release files into ./maven. Minimum SDK 24.

    repositories { maven { url = uri("maven") } }
    dependencies { implementation("org.openckey:ckey:VERSION") }
  • NuGet, for .NET

    For net8.0 and netstandard2.0, with CKey.Wpf for WPF.

    dotnet add package CKey --version VERSION --source ./packages
  • CMake, for C and C++

    Unpack the archive for your platform, then point CMake at it.

    # cmake -S . -B build -DCMAKE_PREFIX_PATH=/path/to/ckey-VERSION-<platform>
    find_package(CKey REQUIRED)
    target_link_libraries(app PRIVATE CKey::core)
  • Homebrew, for the command line

    The ckey tool, which writes SVG, PNG and PDF. It sends no telemetry.

    brew install --formula ./ckey.rb
    ckey encode-scalable --utf8 "https://openckey.org" --out code.svg

Each platform’s API is in the SDK quick starts.

Verify a download

Check a file before you build with it. A matching checksum shows it arrived intact; the attestation shows it was built by the CKey release workflow from the public repository.

  1. Compare the checksum

    The result must match the SHA-256 listed with the file.

    shasum -a 256 ckey-VERSION.tgz
  2. Check the build attestation

    Files from a GitHub Release carry a signed build provenance attestation. Check it with the GitHub CLI.

    gh attestation verify ckey-VERSION.tgz --repo clearkeysolutions/ckey