developer-shivam/Klimatic

59.7

Adequate · 21 September 2026

1.9k

lines of production code

Kotlin

with Java

4

measurements over time

What this system is

This is an Android weather application that allows users to search for and view weather conditions for specific locations. The system manages user preferences, including a persisted last-chosen location and a customizable color theme selection. Internally, it utilizes a centralized dependency management strategy and a distinct domain layer to handle location state and data models.

Features

Add location search and theme selection features

Users can now search for and select a specific location to view weather for, with the app remembering the last chosen location on launch. Additionally, users can choose from five color themes (Blue, Red, Green, Orange, Purple) in the new Settings screen, with the selection persisted and applied to the app's UI.

app/src/main/java · high confidence

Behavioural changes

Refactored location management and search capabilities

The app now uses a shared BaseCurrentSelectedLocationViewModel to manage the user's current selected location, which is then leveraged by the SearchViewModel to provide location-based search functionality. The WeatherViewModel has been updated to inherit from this new base class, allowing it to access the selected location. Additionally, the Location data model now includes an 'id' field, and the ViewState utility has been simplified by replacing ShowLoading/HideLoading with a single Loading state.

domain · medium confidence

Test coverage

Updated test dependency injection modules; Updated weather view model tests to include shared preferences.

Dependencies

Centralize dependency management and introduce domain module

The project now uses a centralized \dependencies.gradle\ file to manage all library versions and dependency declarations, replacing the previous inline version definitions in \app/build.gradle\. This refactoring improves maintainability by allowing version updates in a single location. Additionally, a new \domain\ module has been introduced, with its own \build.gradle\ and inclusion in \settings.gradle\, allowing the application to depend on a separate domain layer.

(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 53 → 60 (+6.6)
Rubric changed (rubric-2026.08.19 → rubric-2026.09.15) — scores are not directly comparable.

Lenses

Code Health 96 → 98 (+1.5)
Architecture 100 → 86 (-13.6)
Maturity 50 → 66 (+15.2)
Readiness 41 → 50 (+8.2)
Security 66 → 82 (+15.9)
Domain Modelling 70 → 60 (-9.9)

Resolved (13)

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)
High: security finding (details withheld)
No exposed public API
Rotate the exposed credentials — git history can't be un-committed
Secret: gcp-api-key (app/google-services.json)
Test reliability not included
early-stage repository — too few commits for a meaningful bus factor
early-stage repository — too little history to judge knowledge freshness

New (18)

Dependency hygiene PARTLY measured — Maven/Gradle declarations read, no dependency graph resolved
Documentation: no installation or build instructions (README.md)
Documentation: no licence statement (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)
High: security finding (details withheld)
High: security finding (details withheld)
Medium: security finding (details withheld)
Medium: security finding (details withheld)
No ADRs found
No dependency advisory monitoring
Workflow token permissions not restricted

Architecture

Containers 0 added · 0 removed · contexts 1 added · 1 removed · edges 0 added · 0 removed

Added bounded contexts (1)

Removed bounded contexts (1)

domain

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

Survey your own repository

developer-shivam/Klimatic 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 21 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 a46582676223c4faaba5e8dad436dbc46da70f8b — 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-fa71c66cabd8.