How sorairolake/abcrypt works
Main Components
• Core Library (abcrypt): This is the heart of the project (located under crates/abcrypt). It defines the encryption format, the algorithms for encryption/decryption, and parameter management.
• CLI Tool (abcrypt-cli): Provides the command-line interface that leverages the core library functions.
• C Bindings (abcrypt-capi): Exposes a C API so that other applications written in C/C++ or other languages interfacing with C can use the encryption library.
• WebAssembly Bindings (abcrypt-wasm): Enables the library to be used in JavaScript/web contexts, typically distributed via npm.
• Python Bindings (abcrypt-py): Allows the core functionality to be accessed from Python applications.
Architectural Patterns & Design Principles
• Modularization: The project is effectively split into distinct modules (core, CLI, C API, WASM, Python), each isolated in its own crate. This separation makes it easy to develop, test, and deploy independently.
• Adapter/Wrapper Pattern: The CLI, C API, WASM, and Python components are adapters/wrappers around the core library, ensuring that the encryption functionality can be accessed in different environments.
• Documentation & DevOps: With the comprehensive docs (Antora and man pages) and automated workflows, there is a strong emphasis on maintainability and continuous integration.