Current repository readingScanned Jul 24, 2026, 4:59 AM UTC
azooKey-Desktop Codebase Valuation
azooKey-Desktop is an open-source Japanese input method for macOS, written in Swift and powered by the Zenzai neural kana-kanji converter. It provides live conversion, optional LLM-based “Magic Conversions”, and Tuner-backed personalization for a smooth, desktop typing experience.
azooKey-Desktop is an open-source Japanese input method for macOS, written in Swift and powered by the Zenzai neural kana-kanji converter. It provides live conversion, optional LLM-based “Magic Conversions”, and Tuner-backed personalization for a smooth, desktop typing experience.
RepoWorth$1,386Current measured development value · Less than one active build day
Rebuild complexity68.341/100Profile: Complex
111.9K code tokens83 source filesSwift primary language
Authored code111.9K tokens · 13,822 source lines
Complexity68.341/100 · Complex
Primary stackSwift
Scan coverage99.54% · Content scan
RepoWorth development valuation
One valuation, with the evidence behind it.
RepoWorth models the current development value represented by the visible repository evidence. It does not include ideation, intellectual property, business value, product discovery, or sale price.
RepoWorthCurrent measured development value$1,386
Modeled range $1,109 to $1,664
0.9 active build days7.4 engineering hours92.1K implementation tokens
Repository evidenceMeasured at the scanned commit111.9K tokens
13,822 source lines across 83 authored files
13 test files0 dependencies99.54% scan coverage
Measured RepoWorth history
The current RepoWorth starts the measured history.
This current scan is the first measured point. Later scans add comparable history when the repository changes. RepoWorth is not back-cast onto commits that were never scanned.
Recorded RepoWorth$1,386
Current measured reading
Measurement basisCurrent readingCurrent published repository scanEvidence coverage100%current scanComplexity68/100Measured from code scale and structural signalsMaintainability74/100Current structure, tests, and generated-code balance
This current scan establishes the RepoWorth baseline. Comparable value changes appear only after another completed scan under the same measurement basis.
RepoWorth history compares completed repository scans only when their measurement basis is compatible. Commit activity is shown separately so delivery volume is not presented as code value.
Repository contributors
Top contributors.
Ranked from the public GitHub contributor evidence available at the latest scan. This table describes measured repository activity, not ownership or original authorship.
azooKey-Desktop is an open-source Japanese input method for macOS, written in Swift and powered by the Zenzai neural kana-kanji converter. It provides live conversion, optional LLM-based “Magic Conversions”, and Tuner-backed personalization for a smooth, desktop typing experience.
azookeyimeinput-methodinputmethodkitmacosswift
License
MIT
Default branch
main
GitHub stars
973
Forks
79
Last public push
Jun 14, 2026
Repository state
Active public repository
Detected language profile532.1KB authored source
Swift98.39%
Shell1.61%
Measured technical evidence
A fuller view of what the scanner found.
These values come from the same immutable repository scan as the headline RepoWorth. They stay tied to the scanned commit so the reading can be inspected against one exact source state.
Maintainability signal74/100
Established based on deterministic repository structure and complexity signals.
Production source99.4K tokens
First-party implementation tokens eligible for the modeled code-scale input.
Test evidence12.5K tokens
13 detected test files contribute separately from production code.
Configuration and infrastructure0 tokens
0 manifests and 0 workspace boundaries were detected.
Documentation3K tokens
2 documentation files remain visible as a distinct enablement signal.
Integration surface167 signals
0 dependency declarations and 79 public-interface signals were measured.
Repository structure5 levels deep
0 large files and 2,094 branch signals add structural context.
Excluded from authored evidence0 files
1 generated files were identified. Ignored and generated material does not inflate RepoWorth.
Technical effort profile
What makes this repository harder to rebuild.
Code scale, branching, dependencies, languages, structure, and visible test evidence shape the implementation and verification effort represented by this repository.
Code scaleModerate
Measured from the current source archive.
ComplexityHigh
Derived from branch density, dependencies, languages, and code scale.
VerificationModerate
Measures visible test code relative to the source corpus.
Development effort composition
Source volume alone does not explain the work.
This view separates authored evidence from the implementation, integration, verification, and engineering oversight represented by the current repository.
Reading boundary: These are modeled development inputs for the visible code. They do not include product discovery, company value, private systems, or commercial outcomes.
Weighted authored evidence92.1KProduction, tests, configuration, and documentation
Estimated implementation output92.1KImplementation, retries, integration, and verification
Engineering oversight7.4 hoursOrientation, integration, tests, and review
Active build time0.9 daysModeled effort represented by the current source state
Evidence boundary
What this valuation includes.
CodeValuation.com counted supported authored source on commit 9e27e24331d9c1b67a8c105489ec6aff173d2477, measured deterministic repository signals, then estimated implementation, rework, testing, integration, and engineering oversight.
Common generated and vendored files, build output, dependencies, lockfiles, minified assets, binaries, media, and private systems outside this repository.
Not claimed
Ideation, intellectual-property rights, security posture, production reliability, company value, sale price, revenue, user value, proprietary data, or the cost of discovering the original product.
This is a modeled current development valuation for the repository's visible code at a specific commit. It reflects code volume, implementation output, complexity, and engineering oversight. It is not a business valuation, investment appraisal, security review, or estimate of sale price, ideation, intellectual property, revenue, users, brand, proprietary data, undocumented domain knowledge, or private infrastructure.
Check another repository
Run RepoWorth on your own codebase.
Enter a public GitHub URL to create a current repository reading.
