Customizable and privacy-conscious open-source keyboard
This report summarizes scanner evidence for HeliBorg/HeliBoard, a Kotlin project with 6,468 GitHub stars. SynthScan examined 201,858 lines of code across 2076 source files, recording 123 pattern matches distributed across 9 syntactic categories. The legacy adjusted pattern signal is 0.7 (Low pattern signal); it is not an authorship estimate.
Use the findings to ask whether maintainers can explain intent, verify dependencies, simplify unnecessary scaffolding, and focus review effort. Risk Payload v1 adds ownership, supply-chain, over-engineering, and review-effort vectors when available. These are prompts for human verification, not probabilities, security findings, or measured maintenance costs.
Use each vector to guide manual verification of the underlying findings.
Payload schema: 1.0.0 · Engine: 2.0.0 · Scoring: heuristic-density-v1 · Scan date: 2026-10-31.
Can maintainers explain intent, assumptions, and trade-offs? 111 finding(s).
Are imports declared and package/API names verified? 12 finding(s).
Are wrappers, guards, and repeated structures necessary? 2 finding(s).
Which changes need focused human review? 123 finding(s).
This chart tracks the legacy adjusted pattern score across scan runs. Changes can reflect source changes, scan coverage, or detector/scoring versions; they do not measure AI adoption or prove that a team refactored code. Compare runs only when their scoring versions are compatible. The dashed line tracks the raw pattern-hit count.
Groups findings by configured severity weight. Severity is not a confidence estimate, security rating, or proof that a package is missing. Verify imports against the project's manifests and inspect each finding in its local design context.
This horizontal bar chart shows where configured pattern scores accumulate across directories. Treat the bars as locations to inspect, not as evidence of authorship or code quality. Use the file-level findings to decide whether a directory needs a focused ownership, dependency, complexity, or review check.
The scanner identified 123 distinct pattern matches across 9 syntactic categories. Each entry below represents a discrete location in the source code where the engine recorded a detector match to inspect in context. Expand any category row to inspect the individual file paths, line numbers, code snippets, and the lexical context (CODE, COMMENT, or STRING) in which each match was detected.
Reading the findings table: The Severity column indicates the configured finding weight (CRITICAL / HIGH / MEDIUM / LOW). The Context column identifies whether the match occurred inside executable code, an inline comment, or a string literal — legacy comment-context matches receive a ×1.5 score weight. The ⚡ bolt icon marks clustered matches: three or more patterns within a 10-line window, each receiving an additional ×1.5 density multiplier under the legacy scoring model.
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | …eys/src/main/resources/emoji/android-emoji-support.txt | 1 | # This file defines emoji compatibility through different Android releases. | COMMENT |
| LOW | …-keys/src/main/resources/emoji/ucd/14.0/emoji-test.txt | 1 | # emoji-test.txt | COMMENT |
| LOW | …-keys/src/main/resources/emoji/ucd/14.0/emoji-test.txt | 21 | # unqualified — a unqualified emoji (See ED-19 in UTS #51) | COMMENT |
| LOW | …-keys/src/main/resources/emoji/ucd/14.0/emoji-test.txt | 4981 | COMMENT | |
| LOW | …-keys/src/main/resources/emoji/ucd/17.0/emoji-test.txt | 1 | # emoji-test.txt | COMMENT |
| LOW | …-keys/src/main/resources/emoji/ucd/17.0/emoji-test.txt | 21 | # unqualified — an unqualified emoji (see ED-19 in UTS #51) | COMMENT |
| LOW | …-keys/src/main/resources/emoji/ucd/13.1/emoji-test.txt | 1 | # emoji-test.txt | COMMENT |
| LOW | …-keys/src/main/resources/emoji/ucd/13.1/emoji-test.txt | 21 | # unqualified — a unqualified emoji (See ED-19 in UTS #51) | COMMENT |
| LOW | …-keys/src/main/resources/emoji/ucd/16.0/emoji-test.txt | 1 | # emoji-test.txt | COMMENT |
| LOW | …-keys/src/main/resources/emoji/ucd/16.0/emoji-test.txt | 21 | # unqualified — a unqualified emoji (See ED-19 in UTS #51) | COMMENT |
| LOW | …-keys/src/main/resources/emoji/ucd/16.0/emoji-test.txt | 5321 | COMMENT | |
| LOW | …-keys/src/main/resources/emoji/ucd/15.0/emoji-test.txt | 1 | # emoji-test.txt | COMMENT |
| LOW | …-keys/src/main/resources/emoji/ucd/15.0/emoji-test.txt | 21 | # unqualified — a unqualified emoji (See ED-19 in UTS #51) | COMMENT |
| LOW | …-keys/src/main/resources/emoji/ucd/15.0/emoji-test.txt | 5021 | # unqualified : 242 | COMMENT |
| LOW | …-keys/src/main/resources/emoji/ucd/15.1/emoji-test.txt | 1 | # emoji-test.txt | COMMENT |
| LOW | …-keys/src/main/resources/emoji/ucd/15.1/emoji-test.txt | 21 | # unqualified — a unqualified emoji (See ED-19 in UTS #51) | COMMENT |
| LOW | …-keys/src/main/resources/emoji/ucd/15.1/emoji-test.txt | 5321 | # minimally-qualified : 1009 | COMMENT |
| LOW | …/main/java/helium314/keyboard/settings/SearchScreen.kt | 81 | // a solution would be using a list(visible to key) | COMMENT |
| LOW | …java/helium314/keyboard/latin/RichInputConnection.java | 441 | } | COMMENT |
| LOW | …java/helium314/keyboard/latin/RichInputConnection.java | 981 | final int oldSelEnd, final int newSelEnd, final int composingSpanStart, final int composingSpanEnd) { | COMMENT |
| LOW | …java/helium314/keyboard/latin/RichInputConnection.java | 1101 | (!TextUtils.isEmpty(selectedText) && mExpectedSelEnd == mExpectedSelStart)) { | COMMENT |
| LOW | …p/src/main/java/helium314/keyboard/latin/LatinIME.java | 841 | COMMENT | |
| LOW | …/helium314/keyboard/latin/DictionaryFacilitatorImpl.kt | 341 | // Even if the user capitalizes manually, they most likely don't want the capitalized form suggested. | COMMENT |
| LOW | …ain/java/helium314/keyboard/latin/utils/TextRange.java | 61 | // extends from 0 to 7. But if we call #getSpans(-1, 5) we'll get both the 0~4 and | COMMENT |
| LOW | …/helium314/keyboard/latin/utils/NgramContextUtils.java | 21 | // Intentional empty constructor for utility class. | COMMENT |
| LOW | …ain/java/helium314/keyboard/latin/utils/ScriptUtils.kt | 81 | // Russian and are not used by our dictionary. | COMMENT |
| LOW | …in/java/helium314/keyboard/latin/utils/SubtypeUtils.kt | 101 | COMMENT | |
| LOW | …java/helium314/keyboard/latin/utils/CapsModeUtils.java | 61 | // CAP_MODE_CHARACTERS is always on. | COMMENT |
| LOW | …java/helium314/keyboard/latin/utils/CapsModeUtils.java | 141 | // if i == j clause), so we need MODE_WORDS to be on. And we don't need to evaluate | COMMENT |
| LOW | …java/helium314/keyboard/latin/utils/CapsModeUtils.java | 181 | | TextUtils.CAP_MODE_SENTENCES) & reqModes; | COMMENT |
| LOW | …java/helium314/keyboard/latin/utils/CapsModeUtils.java | 201 | // letter => WORD | COMMENT |
| LOW | …a/helium314/keyboard/latin/common/WordBreakIterator.kt | 121 | // also we might want to treat ' and - differently (that's our only word connectors atm) | COMMENT |
| LOW | …14/keyboard/latin/makedict/BinaryDictEncoderUtils.java | 221 | // to merge tails, and removing the node from the list would be necessary. However, | COMMENT |
| LOW | …14/keyboard/latin/makedict/BinaryDictEncoderUtils.java | 581 | // until this is done, we'll write 0 and slightly overestimate this case. | COMMENT |
| LOW | …va/helium314/keyboard/latin/inputlogic/InputLogic.java | 401 | COMMENT | |
| LOW | …va/helium314/keyboard/latin/inputlogic/InputLogic.java | 421 | // into account, which means we have to reset the entire composing state whenever there | COMMENT |
| LOW | …va/helium314/keyboard/latin/inputlogic/InputLogic.java | 1041 | // and not for a correction | COMMENT |
| LOW | …va/helium314/keyboard/latin/inputlogic/InputLogic.java | 1061 | // We never go into composing state if suggestions are not requested. | COMMENT |
| LOW | …va/helium314/keyboard/latin/inputlogic/InputLogic.java | 1201 | // If we are in phantom space state, and the user presses a separator, we want to | COMMENT |
| LOW | …va/helium314/keyboard/latin/inputlogic/SpaceState.java | 21 | public static final int NONE = 0; | COMMENT |
| LOW | …/main/java/helium314/keyboard/event/DeadKeyCombiner.kt | 101 | // U+030B: COMBINING DOUBLE ACUTE ACCENT | COMMENT |
| LOW | …/main/java/helium314/keyboard/event/DeadKeyCombiner.kt | 121 | // U+0315: COMBINING COMMA ABOVE RIGHT | COMMENT |
| LOW | …/main/java/helium314/keyboard/event/DeadKeyCombiner.kt | 141 | // U+0344: COMBINING GREEK DIALYTIKA TONOS | COMMENT |
| LOW | app/src/main/java/helium314/keyboard/event/Event.kt | 21 | * user has slid out of the key), etc. It may also be a batch input from a gesture or handwriting | COMMENT |
| LOW | app/src/main/java/helium314/keyboard/event/Event.kt | 41 | val keyCode: Int = NOT_A_KEY_CODE, | COMMENT |
| LOW | app/src/main/java/helium314/keyboard/event/Event.kt | 101 | private enum class EventType { | COMMENT |
| LOW | …/src/main/java/helium314/keyboard/event/HapticEvent.kt | 1 | package helium314.keyboard.event | COMMENT |
| LOW | …/src/main/java/helium314/keyboard/event/HapticEvent.kt | 21 | // } else { | COMMENT |
| LOW | …ium314/keyboard/keyboard/KeyboardActionListenerImpl.kt | 421 | // current state | COMMENT |
| LOW | …va/helium314/keyboard/keyboard/internal/WeakStack.java | 1 | // SPDX-License-Identifier: GPL-3.0-only | COMMENT |
| LOW | …4/keyboard/keyboard/internal/KeyPreviewDrawParams.java | 21 | // <-width-> | COMMENT |
| LOW | app/src/main/jni/run-tests.sh | 1 | #!/bin/bash | COMMENT |
| LOW | …jni/com_android_inputmethod_latin_BinaryDictionary.cpp | 21 | #include <cstring> // for memset() | COMMENT |
| LOW | app/src/main/jni/src/defines.h | 21 | COMMENT | |
| LOW | app/src/main/jni/src/defines.h | 101 | #ifndef LOG_TAG | COMMENT |
| LOW | app/src/main/jni/src/defines.h | 161 | #define DO_ASSERT_TEST | COMMENT |
| LOW | app/src/main/jni/src/defines.h | 181 | #define DEBUG_NODE DEBUG_DICT_FULL | COMMENT |
| LOW | app/src/main/jni/src/defines.h | 201 | COMMENT | |
| LOW | app/src/main/jni/src/defines.h | 221 | COMMENT | |
| LOW | app/src/main/jni/src/defines.h | 241 | #define NOT_A_WORD_ID (S_INT_MIN) | COMMENT |
| 36 more matches not shown… | ||||
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | layouts.md | 145 | * use keys with `"type": "placeholder"` for | COMMENT |
| LOW | …src/test/java/helium314/keyboard/KeyboardParserTest.kt | 604 | { "type": "placeholder" } | CODE |
| LOW | …src/test/java/helium314/keyboard/KeyboardParserTest.kt | 616 | { "type": "placeholder" }, { "label": "k" } | CODE |
| LOW⚡ | …/assets/layouts/functional/functional_keys_tablet.json | 3 | { "$": "keyboard_state_selector", "dpad": { "type": "placeholder", "width": 0.1 } }, | CODE |
| LOW⚡ | …/assets/layouts/functional/functional_keys_tablet.json | 4 | { "type": "placeholder" }, | CODE |
| LOW⚡ | …/assets/layouts/functional/functional_keys_tablet.json | 8 | { "type": "placeholder" } | CODE |
| LOW⚡ | …/assets/layouts/functional/functional_keys_tablet.json | 11 | { "$": "keyboard_state_selector", "dpad": { "type": "placeholder", "width": 0.1 } }, | CODE |
| LOW⚡ | …/assets/layouts/functional/functional_keys_tablet.json | 12 | { "type": "placeholder" }, | CODE |
| LOW⚡ | …/assets/layouts/functional/functional_keys_tablet.json | 17 | { "type": "placeholder" }, | CODE |
| LOW | …rc/main/assets/layouts/functional/functional_keys.json | 4 | { "type": "placeholder" }, | CODE |
| LOW | …/assets/layouts/functional/functional_keys_khipro.json | 8 | { "type": "placeholder" }, | CODE |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | app/src/main/java/helium314/keyboard/latin/Suggest.kt | 233 | // We have a high score, so we need to check if this suggestion is in the correct | COMMENT |
| LOW⚡ | …java/helium314/keyboard/latin/utils/CapsModeUtils.java | 72 | // Step 1 : check for cap MODE_CHARACTERS. If it's looked for, it's always on. | COMMENT |
| LOW⚡ | …java/helium314/keyboard/latin/utils/CapsModeUtils.java | 79 | // Step 2 : Skip (ignore at the end of input) any opening punctuation. This includes | COMMENT |
| LOW | …java/helium314/keyboard/latin/utils/CapsModeUtils.java | 101 | // Step 3 : Search for the start of a paragraph. From the starting point computed in step 2, | COMMENT |
| LOW | …java/helium314/keyboard/latin/utils/CapsModeUtils.java | 148 | // Step 4 : Search for MODE_SENTENCES. | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW⚡ | …java/helium314/keyboard/latin/utils/CapsModeUtils.java | 72 | // Step 1 : check for cap MODE_CHARACTERS. If it's looked for, it's always on. | COMMENT |
| LOW⚡ | …java/helium314/keyboard/latin/utils/CapsModeUtils.java | 79 | // Step 2 : Skip (ignore at the end of input) any opening punctuation. This includes | COMMENT |
| LOW | …java/helium314/keyboard/latin/utils/CapsModeUtils.java | 101 | // Step 3 : Search for the start of a paragraph. From the starting point computed in step 2, | COMMENT |
| LOW | …java/helium314/keyboard/latin/utils/CapsModeUtils.java | 148 | // Step 4 : Search for MODE_SENTENCES. | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| MEDIUM | app/src/main/java/helium314/keyboard/latin/Suggest.kt | 309 | // TODO: Find a more robust way to detect distracters. | COMMENT |
| MEDIUM | …va/helium314/keyboard/latin/inputlogic/InputLogic.java | 1058 | // We only start composing if this is a word code point. Essentially that means it's a | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | tools/release.py | 41 | def check_default_values_diff(): | CODE |
| LOW | tools/release.py | 147 | def update_localized_number_row(): | CODE |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| MEDIUM | …/keyboard/settings/screens/gesturedata/ReviewScreen.kt | 468 | TopAppBar( // not in the scaffold, thus will not cover data column in wide screen layout | CODE |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | tools/diacritics.py | 3 | CODE |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | tools/diacritics.py | 32 | CODE |