How whyoleg/cryptography-kotlin works
Project type and purpose
• This is a multiplatform Kotlin library (monorepo) providing a type-safe cryptography API.
• It does not run as a service or full-stack application; it is a modular library composed of core APIs (random, big integers, cryptographic operations), serialization modules, and pluggable “provider” implementations (JDK, OpenSSL3, Apple, WebCrypto).
File structure
• Top-level build and CI:
• build-logic, build-settings: custom Gradle scripts and plugins to standardize builds and publication.
• .github/workflows and .github/actions: CI pipelines for branch/PR validation, publishing artifacts, website deployment, compatibility tests.
• Main library modules under root:
• cryptography-random
• cryptography-bigint
• cryptography-core
• cryptography-serialization (ASN.1 + PEM)
• cryptography-providers/* (apple, base, jdk, openssl3, webcrypto)
• cryptography-providers-tests-api + cryptography-providers-tests: shared test harness and actual provider compatibility tests.
• Utility/testing/tooling:
• testtool/**: a custom Gradle plugin + client/server for running compatibility tests.
• tests-publication: smoke test for publication.
README for additional insights
• The README states:
• A common API (core) for hashing, ciphers, signatures, key derivation, key agreement.
• A separate random-number API.
• Multiple algorithms defined in core.
• Multiple providers that wrap platform-specific implementations.
• Each component (module or subsystem) must have a clear label.
• Blue for core modules (random, bigint, core, serialization).
• Green for provider layers.
• Orange for build/CI.
• Gray for docs/testing tooling.