HectorMRC/rauth
55.7
Adequate · 14 November 2026
4k
lines of production code
Rust
primary language
9
measurements over time
What this system is
This system is a Rust-based authentication and user-management service that exposes session and user operations over both gRPC and REST. It supports account signup, email verification, password reset, account deletion, and TOTP two-factor authentication, while persisting users, secrets, and metadata in Postgres and using Redis for token or session state. It also publishes user-created events to RabbitMQ, sends email through SMTP, and is packaged as containerized gRPC and REST processes.
How it got here
2020 — authentication and user service contracts
3 changes.
This period was focused on defining the authentication and user-management surface for rauth, adding proto contracts for session login/logout and user signup, reset, deletion, and TOTP operations. It also introduced the Rust dependency manifest for the rauth package, pinning core libraries and optional integrations for gRPC, REST, Postgres, RabbitMQ, and Redis, while many repo-wide changes and fixes touched session-related behavior.
2021 — authenticator core and user management
5 changes.
This period built the shared Rust library layer for an authenticator, adding modules for cryptography, configuration, email handling, validation, and error handling. It introduced user account management with signup, email verification, password reset, deletion, and TOTP support, along with Postgres-backed metadata and secret storage and a script to assemble database setup files.
2022–2023 — authentication service scaffolding
4 changes.
This period established the core runtime and data model for an authentication service, adding database tables for users, metadata, and immutable secrets along with Redis configuration for bounded token storage. It also introduced container build definitions and separate REST and gRPC server entrypoints, wiring repositories, token storage, an event bus, mailer configuration, and session logic into deployable services.
Features
Add REST and gRPC server entrypoints
This change adds new runnable server entrypoints for the authentication service: a REST server built with Actix Web that exposes the session REST service, and a gRPC server built with tonic that exposes user and session gRPC services. The gRPC entrypoint wires together Postgres metadata, secret, and user repositories, Redis token storage, a RabbitMQ user event bus, SMTP mailer configuration, and token/session application logic, while the REST entrypoint wires token storage and the session service. Both entrypoints load environment configuration through dotenv and use tracing for logging, giving operators separate processes for the REST and gRPC APIs.
src/bin · high confidence
Add script to assemble a PostgreSQL setup file from migration files
A new build\_db\_setup\_script.py script can generate a single database setup script by scanning a migrations directory, selecting files that match a configured pattern, and concatenating their contents in sorted order into a target SQL file. By default it looks in ./migrations for files matching up.sql and writes to ./migrations/.postgres/setup.sql, but the migrations path, target path, and file pattern can be configured through environment variables. This makes database setup generation more repeatable and less dependent on manually maintaining one combined SQL file.
scripts · high confidence
Container build definitions for gRPC and REST services
Adds containerfile definitions for the gRPC and REST components, creating multi-stage images that build the Rust binaries and run them as a non-root appuser in a Debian slim runtime. This makes containerized deployment of the gRPC and REST services available, while the shown change is limited to the added container files and does not include the event, RabbitMQ, or REST implementation changes suggested by the commit messages.
container · medium confidence
New user account module: signup, email verification, password reset, deletion, and two-factor (TOTP) support
This adds a dedicated user-management layer to the system. It introduces a User domain model (validating email and Base64 password format, with name defaulting to the email), application logic for signing up, verifying a signup via an emailed token, resetting a password, deleting an account, and enabling/disabling TOTP two-factor authentication (with password and TOTP checks enforced before destructive actions). It exposes these operations through a gRPC service (signup, reset, delete, and TOTP handlers), persists users in Postgres via a repository, and publishes a 'user created' event to RabbitMQ through an event bus. For a product reader, this means the platform can now create and manage user accounts end-to-end — including email verification, password reset, account deletion, and two-factor authentication — and can notify downstream consumers when a new account is created.
src/user · high confidence
Secret domain and Postgres repository layer added
This change introduces a dedicated secret module with a Secret domain model and an async SecretRepository interface, including a Postgres-backed implementation that can create secrets, find them by id or by user and name, update them, save changes, and delete them. It also adds a mock repository for tests and wires the module through a new src/secret entry point. For users, this establishes the internal foundation for storing and retrieving secrets through a Postgres-backed repository, though the diff does not show user-facing endpoints or UI.
src/secret · medium confidence
API
Added session and user service contracts
The proto definitions now introduce a Session service with Login and Logout operations, where Login accepts an identifier, password, and TOTP code, and a User service with Signup, Reset, Delete, and Totp operations. The user contract supports email/password signup, password reset with TOTP, account deletion with password and TOTP, and enabling or disabling TOTP. These new proto3 definitions establish the API surface for authentication and user management, though the diff shows only the contract definitions and not implementation or runtime behavior.
proto · medium confidence
Architecture
Added database schema for metadata, users, and secrets
New migrations introduce the Metadata, Users, and Secrets tables. Users now store name, email, actual email, password, and a metadata reference, while Secrets store a name and data value per user with a unique name-per-user constraint and a metadata reference. A database trigger also prevents updates to a secret's id, name, data, or user, making those fields immutable after creation.
migrations · medium confidence
Core library modules added for the Rust authenticator
The src tree introduces a new shared library layer for the authenticator, adding modules for base64 decoding, environment-driven configuration, JWT/TOTP/RSA cryptography, email suffix handling, gRPC and REST header extraction, SMTP template sending, regex validation, custom error codes, and time utilities. This establishes the common foundation used by the service’s authentication, session, secret, and email flows.
src · medium confidence
Metadata storage layer introduced
The metadata area now has a dedicated module with a Metadata record containing id, created\_at, updated\_at, and deleted\_at, plus an async MetadataRepository interface for find, create, save, and delete operations. A Postgres-backed implementation is included behind the postgres feature, using sqlx to insert, query, update, and delete metadata rows, while a mock repository is provided for tests. This standardizes how metadata is persisted and makes the metadata module testable, though the diff does not show it wired into a user-facing workflow.
src/metadata · medium confidence
Behavioural changes
166 commits (11 fixes) modifying (repo-wide)
A change to existing behaviour in (repo-wide) — 166 commits (11 fixs), 7 files.
(repo-wide), src/session · low confidence · unverified
Redis now runs with bounded memory and LRU eviction
A new Redis configuration file sets a 2 MB memory limit, enables allkeys-lru eviction when memory is reached, and caps the tracking table at 1,000,000 keys. This makes Redis usage more predictable and prevents unbounded memory growth by evicting least-recently-used keys under pressure.
redis · medium confidence
Dependencies
Rust dependency manifest defines rauth's core and optional integrations
The new Cargo.toml for the rauth package pins core dependencies such as tokio 1.28.2, serde 1.0.164, jsonwebtoken 8.3.0, base64 0.21.2, chrono 0.4.26, regex 1.8.4, and tracing 0.1, and declares optional integration crates including actix-web 4.3.1, tonic 0.9.2, prost 0.11.9, protoc 2.28.0, sqlx 0.6.3, redis 0.23.0, reool 0.30.0, deadpool-lapin 0.10.0, and lapin 2.2.1. It also sets default features to config, grpc, rest, postgres, rabbitmq, and redis-cache, so the manifest defines the dependency set and feature-gated integrations available for building the project.
(dependencies) · medium confidence
Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
How this codebase got here
Score
- CAI 55 → 56 (+0.4)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.4) — scores are not directly comparable.
Lenses
- Code Health 99 → 95 (-4.3)
- Architecture 94 → 93 (-0.2)
- Maturity 41 → 41 (+0.0)
- Readiness 69 → 74 (+4.3)
- Security 48 → 48 (+0.0)
- Domain Modelling 100 → 100 (+0.0)
- Performance 100 → 100 (+0.0)
Resolved (2)
- Duplicated block (11 lines × 2) (src/secret/repository.rs)
- No ADRs found
New (12)
- Duplicated block (9 lines × 2) (src/secret/repository.rs)
- Edited copies of one member (3 members, 15+ corresponding lines) (src/metadata/repository.rs)
- Edited copies of one member (3 members, 18+ corresponding lines) (src/metadata/repository.rs)
- Edited copies of one member (3 members, 29+ corresponding lines) (src/user/application.rs)
- Edited copies of one member (4 members, 13+ corresponding lines) (src/user/application.rs)
- Edited copies of one member (5 members, 22+ corresponding lines) (src/secret/repository.rs)
- Edited copy of a member (11 corresponding lines) (src/secret/repository.rs)
- Edited copy of a member (14 corresponding lines) (src/crypto.rs)
- Edited copy of a member (18 corresponding lines) (src/smtp.rs)
- Edited copy of a member (21 corresponding lines) (src/secret/repository.rs)
- Edited copy of a member (31 corresponding lines) (src/crypto.rs)
- No ADRs found (Cargo.toml)
Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
Survey your own repository
HectorMRC/rauth was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point a surveyor at a repository you know and see whether you agree with it.
About this page
- The score is its most recent published measurement, taken on 14 November 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
- Measured at commit 7cac505c11249a2dd1cee8a2ad4d0d3d5022f090 — the exact code this score is about.
- Scored under rubric-2026.11.4 — the same rubric and the same method as every other entry in this index.
- Measured by Canine Code Analyzer (cca.canine.dev) using cca measure-2026.11.65+preprod-e1a3b69fc8ee.