mbobiosio/ModularDynamicFeatureHilt
71.1
Strong · 21 September 2026
917
lines of production code
Kotlin
primary language
4
measurements over time
What this system is
This is an Android application built using Clean Architecture and MVVM, featuring distinct modules for Home, Account, and Favorites. The system provides user interface components like toolbars and floating action buttons to display content and trigger actions. It is supported by a centralized build configuration that manages dependencies and enforces code quality standards.
Features
Home screen gains floating action button and toolbar
The Home feature now displays a Material Toolbar and a Floating Action Button (FAB) on the home screen. The FAB, using the new ic\_add\_home icon, triggers a toast message displaying the home description when clicked. The layout was updated to include these UI elements, and the HomeFragment was refactored to handle the new view bindings and click listeners.
features/home · high confidence
Behavioural changes
Account and Favorite features gain toolbars and floating action buttons
The Account and Favorite feature modules have been updated to include a Material Toolbar and a Floating Action Button (FAB) in their respective layouts. The Account fragment now displays the account description in the toolbar title and shows a toast with the description when the FAB is clicked. Similarly, the Favorite fragment displays the favorite description in the toolbar title and shows a toast with the description upon FAB click. Additionally, the navigation graph has been updated to point to the new package locations for these fragments, and the bottom navigation menu titles have been corrected to 'Favorite' and 'Account' respectively.
app/src, features/account, features/favorite · high confidence
Migrated app-level theme and color resources to the common module
The app's light and dark theme definitions and Material 3 color palette have been moved from the app module to the common module. This change centralizes the application's visual identity, ensuring that the core color resources and base AppTheme styles are shared across the project rather than being defined locally in the app module. Additionally, minor formatting and import order adjustments were applied to the common module's unit and instrumented tests.
common · high confidence
Refactored build configuration and added static analysis tools
The build system was restructured to centralize dependency management and add code quality tools. A new Kotlin-based dependency handler was introduced to manage module-specific dependencies (app, home, favorite, account, common, data, domain) and test dependencies, replacing the previous flat object structure. Several dependencies were removed, including Compose, Coil, Lottie, PrettyTime, JodaTime, and SQLite Ktx. Additionally, static analysis tools Detekt and KtLint were added to the build process.
buildSrc · high confidence
Updated project documentation and configuration
The README.md has been significantly expanded to include a detailed overview of the project's architecture (Clean Architecture, MVVM, Hilt), setup instructions for Android Studio and command-line, and a list of tools like KtLint and Detekt. Additionally, the gradlew script's file permissions were updated to be executable.
(repo-wide) · high confidence
Upgraded Gradle wrapper to version 7.4.2
The Gradle wrapper has been updated from version 7.2 to 7.4.2, ensuring the project uses a newer, more stable build tooling version.
gradle · high confidence
Test coverage
Updated test file formatting and imports
The test files in the data and domain modules have been updated to fix import ordering and add a missing newline at the end of the files. Specifically, the \androidTest\ and \test\ directories for both modules now have consistent import statements and adhere to ktlint formatting rules.
data, domain · high confidence
Dependencies
Migrated build configuration to Kotlin DSL and centralized dependency management
The project's build system has been refactored from Groovy to Kotlin DSL, with all module build scripts converted to .kts files. Dependencies are now managed through centralized extension functions (e.g., appModuleDeps, unitTestDeps) rather than individual declarations, and the root build script applies code quality tools like Detekt and KtLint across all subprojects. Additionally, the settings file now uses a plugin management block to resolve specific versions for the AndroidX Navigation and Hilt Gradle plugins.
(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 66 → 71 (+5.1)
- Rubric changed (rubric-2026.08.19 → rubric-2026.09.15) — scores are not directly comparable.
Lenses
- Code Health 100 → 100 (-0.5)
- Architecture 100 → 100 (-0.3)
- Maturity 74 → 74 (+0.0)
- Readiness 57 → 57 (+0.0)
- Security 63 → 89 (+26.1)
Resolved (16)
- 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)
- High: security finding (details withheld)
- High: security finding (details withheld)
- High: security finding (details withheld)
- No exposed public API
- Test reliability not included
- complexity unreadable for .kt — churn × complexity hotspots could not be measured
- early-stage repository — too little history to judge knowledge freshness
- git history depth insufficient
- single-maintainer — knowledge-concentration (bus factor) risk
New (20)
- 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 (9 lines × 2) (features/account/src/main/java/com/mbobiosio/account/di/DynamicFeatureComponent.kt)
- 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)
- Medium: security finding (details withheld)
- Medium: security finding (details withheld)
- Medium: security finding (details withheld)
- No dependency advisory monitoring
- Workflow token permissions not restricted
Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
Survey your own repository
mbobiosio/ModularDynamicFeatureHilt 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 5a9caa07258a06596deaa07b32edce32c928eaf3 — 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.