How samuelgodoy/arca works
Project type and purpose
• ARCA is a native command‐line encryption tool (an open-source CLI utility), not a multi-tier web app.
• Its sole purpose is to securely encrypt/decrypt a local “vault” of secrets using AES-GCM-SIV + Scrypt, with zero external dependencies and maximum portability (polyglot binary via cosmocc).
File structure
• Top-level directories:
• cmd/ – (empty or future subcommands)
• / – public headers: aes.h, scrypt.h, trng.h, mensagens.h
• src/ – implementation modules: main.c, aes.c, scrypt.c, trng.c
• img/ – README illustrations
• Taskfile.yml – build/task runner (invokes cosmocc)
• Pattern: a simple multi-module C project with a CLI “frontend” (main.c) and three core engine modules (AES, Scrypt, TRNG).
• Build and packaging handled by Taskfile.yml and cosmocc to create a single polyglot binary.
Key insights from the README
• Core algorithms: AES-GCM-SIV (encryption), Scrypt (key derivation), TRNG (secure random).
• Cross-platform, zero dependencies, polyglot single binary.
• Future extension point: user-defined AEAD authenticated data.
Detail without over-complicating
• Module separately; don’t lump all crypto into one monolith.
• Both the offline build flow (Taskfile.yml → cosmocc → final binary) and the runtime flow (user → CLI → modules → disk).