gbzarelli/quaklog-api

This system is a Spring Boot-based backend service designed to manage and process game data. It provides REST endpoints for importing and retrieving game records, utilizing a MongoDB data access layer and a clean architecture for domain logic and log parsing. The application also handles client connections and game state events, while the underlying build environment has been modernized to Spring Boot 3 and Java 17.

The core module now implements a Clean Architecture structure, introducing new domain models for game entities (Game, Player, World, KillHistory), value objects (GameTime, GameUUID, Mod), and a comprehensive set of parsers to process game log lines. This includes a new GameParseProcessor and its implementation to handle client connections, user info changes, kills, and game shutdowns, alongside DTOs for use cases like importing and retrieving games.

core · high confidence

The application now supports importing and retrieving game data via new REST endpoints and a MongoDB-backed repository. Users can upload game files for import and query games by date or UUID. The backend uses Spring Data MongoDB with custom converters for date handling, caching, and a clean architecture separating entry points, use cases, and data providers.

app/src · high confidence

The \SwaggerConfig\ class, which previously configured Swagger 2 for API documentation, has been removed from the application. This change eliminates the Springfox-based API documentation setup, likely as part of a migration away from Swagger 2.

application · high confidence

The empty .gitkeep placeholder files in the application/core source and test directories have been removed. This cleanup eliminates unused files from the project structure.

application/core · high confidence

The project has been upgraded to Spring Boot 3.1.1, requiring a move to Java 17 and the migration from \javax.inject\ to \jakarta.inject\. Several dependencies have been updated to newer versions, including JUnit 5.9.3, Mockito 5.4.0, and Springfox Swagger 2.1.0. Additionally, the project structure has been simplified by moving \core\ and \app\ modules to the root, and the build configuration has been updated to use the \coveralls-gradle-plugin\ instead of the Palantir Jacoco plugin.

(dependencies) · medium confidence

The project's Gradle wrapper has been upgraded from version 5.5.1 to 8.1.1, which may require a compatible Java version and could affect build performance and compatibility.

gradle · high confidence

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

• CAI 65 → 63 (-1.9)
• Rubric changed (rubric-2026.08.19 → rubric-2026.09.15) — scores are not directly comparable.

• Code Health 100 → 100 (-0.4)
• Architecture 100 → 99 (-1.5)
• Maturity 57 → 57 (+0.0)
• Readiness 50 → 49 (-0.4)
• Security 96 → 85 (-10.9)

• Coverage not included — suite not readable by the collector
• Dependency hygiene not measured — dependency manifest found but not parsed for hygiene
• Medium IaC: CKV_DOCKER_3 (Dockerfile)
• No exposed public API
• Test reliability not included
• dormant codebase — no living knowledge left to concentrate

• Dependency hygiene PARTLY measured — Maven/Gradle declarations read, no dependency graph resolved
• Documentation: no contributor guidance (README.md)
• Documentation: no installation or build instructions (README.md)
• Documentation: no usage examples (README.md)
• Duplicated block (10 lines × 3) (core/src/main/java/br/com/helpdev/quaklog/processor/parser/impl/ClientBeginParser.java)
• Duplicated block (6 lines × 2) (app/src/main/java/br/com/helpdev/quaklog/dataprovider/mapper/PlayerStatusRepositoryMapper.java)
• High IaC: WD-COMPOSE-0002 (docker-compose-test.yml)
• High IaC: WD-COMPOSE-0002 (docker-compose-test.yml)
• High IaC: WD-COMPOSE-0002 (docker-compose.yml)
• High IaC: WD-COMPOSE-0002 (docker-compose.yml)
• High IaC: WD-COMPOSE-0002 (docker-compose.yml)
• High: security finding (details withheld)
• Medium IaC: WD-DOCKER-0003 (Dockerfile)
• No ADRs found
• No assertions: shouldExtractParametersFromClientChangedWithSuccess (core/src/test/java/br/com/helpdev/quaklog/parser/GameRegexUtilsTest.java)
• No assertions: shouldExtractParametersFromInitGameWithSuccess (core/src/test/java/br/com/helpdev/quaklog/parser/GameRegexUtilsTest.java)
• No dependency advisory monitoring

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

gbzarelli/quaklog-api 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.