Rayato159/quests-tracker
46.9
Weak · 8 November 2026
2.3k
lines of production code
Rust
primary language
7
measurements over time
What this system is
Features
Add authentication, quest management, and crew switchboard endpoints
The infrastructure layer now exposes HTTP endpoints for user authentication (login and token refresh for both adventurers and guild commanders), quest operations (add, edit, remove), journey ledger status updates, and crew switchboard actions (join, leave). These are backed by new Axum routers, middleware for JWT-based authorization, and PostgreSQL repositories for data access. A graceful shutdown signal and a health check endpoint are also added.
src/infrastructure · high confidence
Add database migration scripts for game entities
Added SQL migration scripts to initialize the database schema. The 'up' script creates tables for quests, adventurers, guild commanders, and the junction table linking quests to adventurers, along with necessary foreign key constraints. The 'down' script provides the corresponding cleanup by dropping these tables.
assets · high confidence
Added domain entities for adventurers, guild commanders, and quests
New domain entity structs have been introduced to represent core game data: AdventurerEntity and RegisterAdventurerEntity for the adventurers table, GuildCommanderEntity and RegisterGuildCommanderEntity for the guild\_commanders table, and QuestEntity, AddQuestEntity, and EditQuestEntity for the quests table. These structs define the data models and database mappings for these entities, enabling the application layer to interact with the database using Diesel.
src/domain/entities · medium confidence
Introduce structured configuration loading from environment variables
The application now loads configuration from environment variables using the \dotenvy\ crate. This introduces new structs for server settings (port, body limit, timeout), database URL, and JWT secrets for adventurers and guild commanders, all parsed from the environment. It also adds a \Stage\ enum to represent the current environment (Local, Development, Production).
src/config · medium confidence
Introduces domain value objects for quests, adventurers, and guild commanders
The src/domain/value\_objects module now includes new Rust structs and enums that define the data structures for quest management, adventurer registration, guild commander registration, and quest status filtering. These value objects serve as the domain layer's interface for creating, editing, and querying quests, as well as linking adventurers to quests. The changes add serialization/deserialization support (via serde) and database mapping (via diesel) to these models, enabling the application layer to interact with the domain entities.
_src/domain/value\objects · high confidence
New application use cases for adventurers, authentication, and quests
The application layer now includes use cases for registering and managing adventurers and guild commanders, handling login and token refresh for both user types, and managing quest operations such as joining, leaving, and tracking journey status. These additions provide the core business logic for user authentication, quest participation, and quest lifecycle management.
src/application · high confidence
New domain repository interfaces for core game entities
The application layer now exposes repository interfaces for managing adventurers, guild commanders, quests, and journey states. Specifically, the system introduces \AdventurersRepository\ for registering and finding adventurers, \GuildCommandersRepository\ for commander registration and lookup, \QuestOpsRepository\ for adding, editing, and removing quests, and \QuestViewingRepository\ for viewing quest details and board listings. Additionally, \JourneyLedgerRepository\ tracks quest completion or failure states, while \CrewSwitchboardRepository\ handles joining or leaving quest-adventurer junctions. A \TransactionProvider\ is also introduced to manage database transactions.
src/domain/repositories · high confidence
Behavioural changes
Initialize application with Postgres and HTTP server
The application now initializes by loading environment variables, establishing a connection to a Postgres database, and starting an HTTP server. Previously, the main entry point only printed a message to the console; it now integrates configuration loading, database connection pooling, and server startup logic.
src · medium confidence
Removal of domain services
The services module has been removed from the domain layer. This eliminates the services layer from the domain, leaving only entities, repositories, and value objects as the primary domain components.
src/domain · medium confidence
Removed obsolete config loader files
The 'config' directory's 'dotenvy\_loader.rs' and 'mod.rs' files have been deleted. This removes the previous configuration loading mechanism, likely as part of a broader refactor to a new config folder location.
config · medium confidence
Dependencies
Update Rust edition and add new dependencies
The project has been upgraded to the 2024 Rust edition. Several new dependencies have been added to support application features: \anyhow\ for error handling, \argon2\ for password hashing, \rand\ for random number generation, and \jsonwebtoken\ for JWT handling. Additionally, the \diesel\ dependency has been updated to include the \r2d2\ feature, and \chrono\ has been updated to include the \serde\ feature. The \axum-extra\ crate has also been added.
(dependencies) · high 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 47 → 47 (-0.2)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.2) — scores are not directly comparable.
Lenses
- Code Health 76 → 76 (+0.0)
- Architecture 79 → 79 (+0.0)
- Maturity 46 → 46 (+0.0)
- Readiness 35 → 35 (+0.0)
- Security 52 → 50 (-1.3)
- Domain Modelling 100 → 100 (+0.0)
- Performance 100 → 100 (+0.0)
Resolved (3)
- Inconsistent parameter passing for removal operations. QuestOpsRepository.remove takes individual IDs (quest_id, guild_commander_id), while CrewSwitchboardRepository.leave takes a composite object (QuestAdventurerJunction). This inconsistency makes the repository interface harder to use uniformly.
- Separation of concerns confusion. QuestEntity requires an external adventurers_count to convert to a model, implying the entity is not self-sufficient for DTO creation. Meanwhile, QuestViewingRepository has a specific method adventurers_counting_by_quest_id which suggests the count is fetched separately. This leads to a fragmented API where the entity cannot be fully converted to a model without external data injection, and the repository has a dedicated counting method that might be better integrated or abstracted.
- Test/Debug methods exposed in public API surface. The repository exposes internal transaction testing helpers (for_transaction_test_1, for_transaction_test_2) which are implementation details and should not be part of the domain repository interface. Additionally, join_and_delete_transaction in the UseCase is a specific transactional workflow that duplicates the intent of join and leave but with transactional guarantees, yet it lacks clear naming distinction from standard operations.
New (13)
- Medium advisory (unmaintained): RUSTSEC-2026-0441 (Cargo.lock)
- Medium advisory (unsound): RUSTSEC-2026-0386 (Cargo.lock)
- Medium advisory (unsound): RUSTSEC-2026-0395 (Cargo.lock)
- Medium advisory (unsound): RUSTSEC-2026-0397 (Cargo.lock)
- Medium advisory (unsound): RUSTSEC-2026-0399 (Cargo.lock)
- Medium advisory (unsound): RUSTSEC-2026-0400 (Cargo.lock)
- Medium advisory (unsound): RUSTSEC-2026-0401 (Cargo.lock)
- Medium advisory (unsound): RUSTSEC-2026-0402 (Cargo.lock)
- Medium advisory (unsound): RUSTSEC-2026-0404 (Cargo.lock)
- Medium advisory (unsound): RUSTSEC-2026-0406 (Cargo.lock)
- Medium vulnerability: RUSTSEC-2026-0391 (Cargo.lock)
- Medium vulnerability: RUSTSEC-2026-0403 (Cargo.lock)
- Medium vulnerability: RUSTSEC-2026-0410 (Cargo.lock)
Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
Survey your own repository
Rayato159/quests-tracker 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 8 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 9ef1fc8289346114972eda42bb562fc4527142c6 — the exact code this score is about.
- Scored under rubric-2026.11.2 — 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.3+preprod-45ab2cab63de.