tk-codes/uno
60.4
Adequate · 22 September 2026
1.4k
lines of production code
Java
primary language
7
measurements over time
What this system is
This system is a Java-based UNO card game application that implements a complete domain model for game logic, player management, and UI interaction. It features a layered architecture with a domain model, an application service for game state management, and a Swing-based user interface. The codebase is built using Gradle and includes comprehensive unit tests for the game rules, deck handling, and player iterators.
How it got here
2015 — Build system migration and cleanup
3 changes.
This period focused on modernizing the project's build infrastructure by migrating from Eclipse to Gradle, while simultaneously removing the obsolete UNO game application and associated configuration files. The work involved replacing legacy build scripts and IDE-specific settings with a standardized Gradle wrapper and cleaning up temporary project artifacts.
2021 — UNO game domain and test implementation
9 changes.
This period focused on establishing the core UNO game domain model, including card types, game state management, and a Swing-based UI. Comprehensive unit tests were added to verify game logic, player behavior, and event publishing, supported by test helper factories and UML diagrams to document the architecture.
Features
Add UML diagrams for domain classes
Added UML diagrams in the doc directory to visualize the structure of the domain model. The new files (cards.uml, events.uml, game.uml, and player.uml) document the relationships between classes such as Card, Player, Game, and DomainEvent, providing a visual reference for the internal architecture.
doc · high confidence
Introduce UNO game domain model and UI
The application now includes the complete domain model for the UNO card game, featuring card types (number, action, wild), game state management, and player logic. The UI layer has been implemented with Swing components to display the game board, player hands, and game status, connecting to the domain via an application service that handles game logic and event publishing.
src/main · high confidence
Removals
Removal of the UNO game application
The entire UNO game application has been removed from the repository. This includes all Java source files for the game logic (Game, Player, Dealer, PC), card models (ActionCard, CardDeck, NumberCard, WildCard), UI components (MainFrame, Session, PlayerPanel, TablePanel, InfoPanel), and controller classes (Server, MyButtonListener, MyCardListener). Additionally, the Eclipse project configuration (.settings/org.eclipse.jdt.core.prefs) and UML class diagram files (UML.ucls, UML 2.ucls) have been deleted.
(repo-wide) · high confidence
Behavioural changes
Added Gradle wrapper configuration
The project now includes a Gradle wrapper configuration file (gradle/wrapper/gradle-wrapper.properties) that specifies Gradle version 6.7. This ensures consistent build environments across different machines by pinning the Gradle distribution URL and storage paths.
gradle · high confidence
Migrated project structure from Eclipse to Gradle
The project has been converted from an Eclipse-based Java project to a Gradle build system. This includes adding the Gradle wrapper scripts (gradlew, gradlew.bat) to allow running the application and tests via the terminal, and updating the .gitignore file to exclude Gradle and IDE-specific build artifacts. The legacy Eclipse configuration files (.classpath, .project) have been removed.
(repo-wide) · high confidence
Removal of Eclipse RemoteSystemsTempFiles project configuration
The .project file for the 'RemoteSystemsTempFiles' Eclipse project has been deleted. This removes the project definition that previously included the 'org.eclipse.rse.ui.remoteSystemsTempNature' nature, effectively cleaning up temporary remote system files from the workspace configuration.
RemoteSystemsTempFiles · high confidence
Test coverage
Added comprehensive test coverage for game domain logic; Added test helper factories for cards and players; Added tests for DomainEventPublisher; Added tests for card domain logic and deck composition; Added unit tests for player domain logic.
Dependencies
Initialize Gradle build with Log4j 2.20.0 and JUnit 5.6.3
The project is initialized with a Gradle build configuration that specifies Java, SonarQube, JaCoCo, and application plugins. It adds Log4j API and Core version 2.20.0 as implementation dependencies, and JUnit Jupiter 5.6.3 as a test dependency. The build also configures JaCoCo for test coverage reporting and SonarQube analysis, excluding UI classes from coverage metrics.
(dependencies) · high confidence
Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
How this codebase got here
This is the PUBLIC form of this artifact. Findings are listed in full, but the details of SECURITY findings — which rule fired, in which file, on which line, and how to fix it — are deliberately withheld, and any secret-scanner results are excluded entirely. Where detail is absent here it was REMOVED FOR PUBLICATION; it is not missing from the analysis. The complete artifact is available from the repository owner.
Score
- CAI 59 → 60 (+1.0)
- Rubric changed (rubric-2026.08.19 → rubric-2026.09.15) — scores are not directly comparable.
Lenses
- Code Health 100 → 100 (+0.0)
- Architecture 69 → 69 (+0.0)
- Maturity 43 → 43 (+0.0)
- Readiness 74 → 71 (-2.7)
- Security 75 → 93 (+17.8)
Resolved (9)
- Coverage not included — suite not readable by the collector
- Dependency hygiene not measured — dependency manifest found but not parsed for hygiene
- High: security finding (details withheld)
- High: security finding (details withheld)
- High: security finding (details withheld)
- High: security finding (details withheld)
- No exposed public API
- Test reliability not included
- dormant codebase — no living knowledge left to concentrate
New (41)
- Dependency hygiene PARTLY measured — Maven/Gradle declarations read, no dependency graph resolved
- Documentation: no installation or build instructions (README.md)
- Documentation: no usage examples (README.md)
- High: security finding (details withheld)
- High: security finding (details withheld)
- High: security finding (details withheld)
- High: security finding (details withheld)
- High: security finding (details withheld)
- High: security finding (details withheld)
- High: security finding (details withheld)
- Medium: security finding (details withheld)
- Medium: security finding (details withheld)
- Medium: security finding (details withheld)
- No ADRs found
- No assertions: WhenClockwise_ShouldHaveAscendingOrder (src/test/java/domain/player/TestPlayersIterator.java)
- No assertions: WhenInitialized_FirstPlayerShouldBeCurrent (src/test/java/domain/player/TestPlayersIterator.java)
- No assertions: WhenInitialized_ShouldHave76NumberCards (src/test/java/domain/card/TestCardDeck.java)
- No assertions: WhenInitialized_ShouldHave8DrawTwoCards (src/test/java/domain/card/TestCardDeck.java)
- No assertions: WhenInitialized_ShouldHave8ReverseCards (src/test/java/domain/card/TestCardDeck.java)
- No assertions: WhenInitialized_ShouldHave8SkipCards (src/test/java/domain/card/TestCardDeck.java)
- …and 21 more
Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
Survey your own repository
tk-codes/uno 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 22 September 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
- Measured at commit bf1249a2b5d39a6f8e6bbbf2e4351e5f7ec63f32 — the exact code this score is about.
- Scored under rubric-2026.09.15 — the same rubric and the same method as every other entry in this index.
- Measured by watchdog.canine.dev using codehealth-analyzer preprod-90d5d2fe38ee.