Ackites/Nrfr
45.0
Weak · 13 November 2026
2.5k
lines of production code
Kotlin
with TypeScript, Go, JavaScript
8
measurements over time
What this system is
Features
Initial project scaffolding and build configuration
The application is initialized with essential build infrastructure: a .gitignore file excludes build artifacts (APKs, AABs, dex files) and temporary directories; a proguard-rules.pro file provides commented-out ProGuard configuration for code shrinking and obfuscation; and the Gradle wrapper is configured to use Gradle 8.9 via the distribution URL in gradle-wrapper.properties.
app, gradle · high confidence
Initial release of the Nrfr app for modifying SIM carrier configurations
The app introduces a new interface for modifying SIM card country codes and carrier names, leveraging Shizuku for elevated permissions. Users can select a SIM slot, choose from preset country codes or enter a custom two-letter code, and select from a comprehensive list of preset carriers or enter a custom carrier name. The app also includes an 'About' screen with app information, author details, and open-source links, alongside a 'ShizukuNotReady' screen to guide users who haven't enabled Shizuku yet.
app/src · high confidence
Initial release of the nrfr-client desktop application
The nrfr-client application is introduced, providing a desktop interface for managing Android devices via ADB. The client automatically manages the ADB server lifecycle (starting and stopping the server on startup and shutdown) and provides a step-by-step workflow for users to select a device, check for and install required applications (Shizuku and Nrfr), and start services. The frontend is built with React and Tailwind CSS, while the backend handles device communication and system integration.
nrfr-client · high confidence
Dependencies
Initial project setup with Android, Go, and React dependencies
The project was initialized with build configurations and dependency manifests for multiple components. The Android app module (app/build.gradle.kts) defines the application with compileSdk 34, minSdk 26, and includes dependencies for AndroidX, Jetpack Compose, Shizuku, and testing libraries. The Go backend (nrfr-client/go.mod) specifies Go 1.22.0 with the Wails v2.9.2 framework and related Go libraries. The frontend (nrfr-client/frontend/package.json) establishes a React 19.0.0 application using Vite, TailwindCSS, and TypeScript. These files collectively establish the development environment and dependency graph for the application.
(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 43 → 45 (+1.5)
- Rubric changed (rubric-2026.10.5 → rubric-2026.11.3) — scores are not directly comparable.
Lenses
- Code Health 87 → 88 (+0.1)
- Architecture 78 → 78 (+0.0)
- Maturity 54 → 55 (+1.4)
- Readiness 25 → 25 (+0.0)
- Security 58 → 63 (+4.2)
- Accessibility 54 → 60 (+6.2)
- Performance 100 → 100 (+0.0)
Resolved (6)
- Duplicated block (12 lines × 2) (nrfr-client/app.go)
- Inconsistent naming convention for fullscreen operations. 'Fullscreen' is used as a verb (imperative) for entering fullscreen, but 'Unfullscreen' is a non-standard verb form. Standard convention would be 'EnterFullscreen'/'ExitFullscreen' or 'SetFullscreen(bool)'. The mix of imperative verbs and non-standard negation is confusing.
- Inconsistent spelling/terminology. 'Maximise' uses 's' (British English), while 'Minimise' also uses 's'. However, 'Fullscreen' and 'Unfullscreen' do not follow a clear pattern. More importantly, the API mixes 'Set' prefix methods (e.g., WindowSetTitle, WindowSetSize) with bare verb methods (e.g., WindowHide, WindowShow, WindowMaximise). This inconsistency makes it unclear whether a method sets a state or performs an action.
- No ADRs found
- Redundant/Confusing API surface for window state management. Having separate methods for Maximize, Unmaximize, and ToggleMaximize is inconsistent with standard UI library patterns (which usually provide SetMaximized(bool) or ToggleMaximized()). Furthermore, 'ToggleMaximise' implies a state change based on current status, while 'Maximise' and 'Unmaximise' are explicit state setters. This creates three ways to achieve similar goals (setting maximized state) and increases cognitive load.
- Same inconsistency as Maximise. Having separate Minimise and Unminimise methods is redundant compared to a single SetMinimized(bool) or ToggleMinimized() approach. It forces the caller to know the current state to use 'Unminimise' effectively or requires checking state before calling.
New (4)
- Edited copy of a member (14 corresponding lines) (nrfr-client/app.go)
- Edited copy of a member (45 corresponding lines) (nrfr-client/app.go)
- High CVE: [GHSA redacted] (nrfr-client/go.mod)
- No ADRs found (nrfr-client/app.go)
Architecture
- Unchanged — 0 containers · 1 contexts · 0 edges
Written by cca.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.
Survey your own repository
Ackites/Nrfr 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 13 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 c8044fe7d42beea496d66fae43b9683fcf942ce4 — the exact code this score is about.
- Scored under rubric-2026.11.3 — 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.63+preprod-4a8cc97a9484.