SS
← All projectsSeedSigner

SeedSigner

Stateless, air-gapped Bitcoin signing software for Raspberry Pi hardware.

BitcoinHardware walletsNormal
Repository coverage

285 commits in the local evidence base

Every captured commit receives deterministic security triage and a separate communication-quality score. Security candidates and broader second-pass signals receive full-patch Ollama analysis.

214security candidates37second-pass queue278AI analyses
14commits · 30 days
52commits · 60 days
111commits · 180 days
230commits · 365 days
Backfill bands
Aug 5 → Feb 6150 seen8 candidatesComplete
Feb 6 → Jun 629 seen0 candidatesComplete
Jun 6 → Jul 60 seen0 candidatesComplete
Jul 6 → Aug 57 seen1 candidatesComplete
Commit communication

Does the history explain itself?

Message quality measures whether a commit identifies its scope, purpose, rationale, testing, and supporting references. It does not change the security-severity score.

53/100 average clarity
30Strong · 80–100
77Adequate · 60–79
108Thin · 40–59
70Opaque · 0–39
46security candidates with opaque commit messaging
Read the scoring rubric →
Developer activity

Who is changing the project?

Public Git author strings; identities are not independently verified.

DeveloperCommitsCandidatesAnalyzedHigh riskMessage avg.
Nick Klockenga413337769
kdmukai158114158348
okaybro282427068
newtonick181317049
PROWLERx15101010020
alvroble12711055
FazleRabbbiferdaus172868061
biel414037
SeedSigner111058
Chaitanya-Keyal111057
Kshitij111033
S1DDHEY111045
Analysis record

Published AI watches

Last scanned 25 minutes ago

High 80 AI analysisMessage 78 · Adequate
SS SeedSignerSeedSigner BitcoinHardware wallets

Merge pull request #1073 from kdmukai/2026-10_psbt_change_path_rules

This commit adds security checks to SeedSigner, an offline Bitcoin signing device, to prevent malicious or buggy wallet software from tricking users into sending change to derivation paths their wallet will never scan. It now verifies that…

New fatal error class PSBTChangeDerivationPathError for non-standard change derivation pathsNew fatal error class PSBTUnverifiableMixedInputBasePathsError for unverifiable mixed-base-path segwit v0 inputsChange output base path must match a verified input base path
5f321768by Nick Klockenga+1863−1397 files
Vendor flagged security relevance
High 81 AI analysisMessage 78 · Adequate
SS SeedSignerSeedSigner BitcoinHardware wallets

Merge pull request #1060 from kdmukai/2026-10_psbt_input_claims

This commit hardens SeedSigner's PSBT (Bitcoin transaction) parser so it no longer trusts a coordinator's claim that an input belongs to your seed. Before, the device only checked that your seed could derive the claimed key. Now it also re…

New attack-level exception: PSBTInputOwnershipContradictionError when an input claims the seed's key but the committed script does not use itInput ownership now verified by rebuilding the scriptPubKey from the claimed key rather than trusting PSBT bip32 derivationsTaproot key-path spends verified by re-applying the merkle-root tweak to the internal key and comparing to the committed output
995ce5c6by Nick Klockenga+990−1406 files
Vendor flagged security relevance
Informational 15 AI analysisMessage 78 · Adequate
SS SeedSignerSeedSigner BitcoinHardware wallets

Reword the input claim checks' docstrings

This commit only rewrites comments and documentation strings in code and tests. No program logic, behavior, or security checks were changed.

081b1f40by kdmukai+13−155 files
No security note in commit
Moderate 69 AI analysisMessage 95 · Strong
SS SeedSignerSeedSigner BitcoinHardware wallets

Refuse mixed base paths on single sig segwit v0

This commit fixes a security flaw in SeedSigner, a small hardware wallet used to sign Bitcoin transactions. The bug could let a malicious transaction coordinator trick the device into accepting change money sent to a wallet path the user n…

New security check explicitly described as preventing a malicious coordinator from anchoring change to an unmonitored derivation pathNew exception class PSBTUnverifiableMixedInputBasePathsError with Warning-grade refusalUI flow now redirects to a blocking warning screen instead of allowing signing
9130ac75by kdmukai+432−875 files
Vendor flagged security relevance
Moderate 60 AI analysisMessage 73 · Adequate
SS SeedSignerSeedSigner BitcoinHardware wallets

Measure the change window from the smallest input index

This commit fixes a security check in SeedSigner, a small hardware-wallet-like device used to sign Bitcoin transactions. Previously, when deciding whether a change output's address was suspiciously far from the user's known addresses, the …

Fixes a window-widening attack against change-output verificationChange-output address index check now uses smallest input index instead of largestAdds hardened-input edge-case handling (window measured from 0)
512329beby kdmukai+57−102 files
Vendor flagged security relevance
Informational 12 AI analysisMessage 78 · Adequate
SS SeedSignerSeedSigner BitcoinHardware wallets

Test change at an extra level under the base path

This commit only adds a new test case to the project's test suite. It does not change any production code. The new test checks that the existing PSBT parser correctly rejects a specific kind of suspicious change output (one placed at a dee…

Adds defensive test coverage for PSBT change-output derivation-path validationRelates to preventing a coordinator with an account xpub from routing change to an unexpected deeper path
9c19e9d6by kdmukai+17−31 file
No security note in commit
High 81 AI analysisMessage 85 · Strong
SS SeedSignerSeedSigner BitcoinHardware wallets

Check change derivation paths against the inputs

This commit adds a safety check to SeedSigner that refuses to sign a Bitcoin transaction if the change output is being sent to a derivation path the user's wallet is unlikely to scan. Before this change, an attacker could trick a user into…

New attack-level exception PSBTChangeDerivationPathError for change sent to an unscanned derivation pathNew warning WARNING__CHANGE_ADDRESS_INDEX_BEYOND_WINDOW for change address indices far past spent indicesNew UI screen PSBTUnexpectedChangeDerivationPathView with DireWarningScreen and forced discard
862ed41bby kdmukai+1285−507 files
Vendor flagged security relevance
Informational 14 AI analysisMessage 68 · Adequate
SS SeedSignerSeedSigner BitcoinHardware wallets

Show the psbt's warnings through one View

This commit is a code cleanup, not a security fix. It consolidates several warning screens shown before signing a Bitcoin transaction into a single reusable view. The warnings themselves—such as 'high fee' and 'no change'—still behave the …

Refactor only: no change to validation, cryptography, or signing logicUser-facing warning text and flow remain equivalentAdds unit tests covering high-fee, no-change, and combined warning sequences
a8602100by kdmukai+163−784 files
No security note in commit
Informational 15 AI analysisMessage 95 · Strong
SS SeedSignerSeedSigner BitcoinHardware wallets

Add a test helper to set an input's locking script

This commit only reorganizes test code. It adds a helper function that replaces twelve nearly identical blocks of test setup code, with no changes to the actual wallet or signing logic that users rely on.

b297c869by kdmukai+31−553 files
No security note in commit
Informational 15 AI analysisMessage 85 · Strong
SS SeedSignerSeedSigner BitcoinHardware wallets

Document held findings at the steps that hold them

This commit only moves and rewrites documentation comments inside the code. It does not change how the program behaves, what it checks, or how it responds to malicious data. The logic for detecting and holding security findings in PSBT par…

1ba3c6a1by kdmukai+37−232 files
No security note in commit
High 78 AI analysisMessage 88 · Strong
SS SeedSignerSeedSigner BitcoinHardware wallets

Merge pull request #1047 from kdmukai/2026_09_psbt_input_scripts

This commit adds security checks to SeedSigner, a small offline Bitcoin signing device. Before the change, a malicious or buggy wallet coordinator could give the device a transaction where an input's hidden script did not match the public …

New validation logic compares supplied witness/redeem scripts against scriptPubKey hashesNew exception classes explicitly label script mismatch as an attack and missing/extraneous scripts as correctness problemsUI flow terminates signing before rendering transaction details when a script check fails
ada81cdeby Nick Klockenga+598−795 files
Vendor flagged security relevance
Informational 15 AI analysisMessage 18 · Opaque
SS SeedSignerSeedSigner BitcoinHardware wallets

Enable Swahili

This commit simply adds Swahili as a new language option in the SeedSigner settings. It is a routine localization change with no security relevance.

c255bf57by kdmukai+2−01 file
No security note in commit
Moderate 51 AI analysisMessage 73 · Adequate
SS SeedSignerSeedSigner BitcoinHardware wallets

Merge pull request #1042 from Chaitanya-Keyal/op-return-push-opcode

This commit fixes how SeedSigner reads the extra data attached to OP_RETURN Bitcoin transaction outputs. Previously the code always assumed the data was introduced by OP_PUSHDATA1, which meant it would misread or crash on the more common d…

Fixes incorrect parsing of OP_RETURN data due to assumed push opcodeAdds robust handling for direct push, OP_PUSHDATA1/2/4, and OP_0-OP_16Introduces explicit malformed-script rejection instead of silent mis-parsing
d8f7956fby Nick Klockenga+375−156 files
No security note in commit
Moderate 64 AI analysisMessage 73 · Adequate
SS SeedSignerSeedSigner BitcoinHardware wallets

Merge pull request #1041 from Chaitanya-Keyal/psbt-negative-fee

This update makes SeedSigner refuse Bitcoin transaction files (PSBTs) where the outgoing amounts are larger than the incoming amounts. Before the fix, the device would have accepted such impossible transactions and shown the user a negativ…

Input validation: rejects PSBTs with mathematically impossible fee valuesUser-facing safeguard: prevents confusing negative fee from reaching transaction review screensNew exception class with clear semantics (PSBTNegativeFeeError)
ebc1e11fby Nick Klockenga+105−65 files
No security note in commit
Informational 15 AI analysisMessage 73 · Adequate
SS SeedSignerSeedSigner BitcoinHardware wallets

Drop the negative fee comment's claim that both totals are unverified

This commit only updates a code comment to remove an outdated claim. The actual security check for negative fees remains unchanged, and a prior code change already verifies input amounts before outputs are parsed. There is no functional se…

9994a04eby okaybro+3−41 file
No security note in commit
High 81 AI analysisMessage 88 · Strong
SS SeedSignerSeedSigner BitcoinHardware wallets

Merge pull request #995 from newtonick/psbt-verify

This commit fixes a security flaw in SeedSigner, a small offline Bitcoin signing device. Previously, when a user scanned a transaction to sign, the device added up the input amounts exactly as a malicious or compromised computer/coordinato…

Fixes a fee-display manipulation vulnerability where a compromised coordinator could understate input amounts to hide excessive real feesAdds explicit verification of each input's amount against the prior transaction before totaling inputsRaises dedicated security exceptions (PSBTInputAmountVerificationError, PSBTMissingInputUtxoError) and blocks the signing flow
e92c4ea6by Nick Klockenga+508−346 files
Vendor flagged security relevance
Informational 15 AI analysisMessage 60 · Adequate
SS SeedSignerSeedSigner BitcoinHardware wallets

Trim the input-amount verification test docstrings

This commit only rewrites the explanatory text (docstrings) inside test code. No actual program logic, security checks, or test behavior changed. It is a documentation cleanup within tests.

afb7305aby newtonick+17−261 file
No security note in commit
Informational 12 AI analysisMessage 60 · Adequate
SS SeedSignerSeedSigner BitcoinHardware wallets

Tighten the input-amount test asserts and run the no-utxo test over every fixture

This commit only changes test code. It tightens some Python assertions (using 'is False' instead of '== False') and expands one test to run across more test fixtures. There is no change to the actual wallet or PSBT parsing logic that users…

222bf3d5by newtonick+12−91 file
No security note in commit
Informational 15 AI analysisMessage 60 · Adequate
SS SeedSignerSeedSigner BitcoinHardware wallets

Replace the parse() test helper with direct PSBTParser calls

This commit only changes a test file. It removes a small helper method called parse() and replaces its calls with the same one-line PSBTParser constructor call written out directly. There is no change to the actual wallet/security code tha…

a71b7b39by newtonick+11−131 file
No security note in commit
Repository ledger

Explore captured commits

Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.

AI review queuedCorrecting assert mistakeby biel · a1e47eb8 · Dec 19, 2025 · 1 fileMessage 35 · OpaqueInformational 15Details
Commit message · biel

Correcting assert mistake

35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100

This is a one-line correction in a test file. The test was checking that a 'passphrase' setting was NOT included in parsed QR-code settings, but the intended behavior is that it SHOULD be included. The change fixes the test assertion to match the actual expected behavior. It does not change any production code and has no direct security impact on users.

Lower-priorityAdd a recognized setting for test_settingsqr_ignores_unrecognized_settingby biel · d31d819b · Dec 19, 2025 · 1 fileMessage 50 · ThinInformational 12Details
Commit message · biel

Add a recognized setting for test_settingsqr_ignores_unrecognized_setting

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI analysis · Informational 12/100

This commit only changes a test file. It adds one more unrecognized setting ('passphrase=E') to an existing test that checks the SettingsQR parser ignores unknown settings. There is no change to production code, no security fix, and no vulnerability introduced.

Lower-priorityBugfix: `Mock` persisted beyond intended test caseby kdmukai · 4a78c6f0 · Dec 18, 2025 · 1 fileMessage 60 · AdequateInformational 15Details
Commit message · kdmukai

Bugfix: `Mock` persisted beyond intended test case

60/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
AI analysis · Informational 15/100

This is a test-only cleanup. A unit test was replacing the `os.walk` function with a fake version and not restoring it afterward, which could cause unrelated later tests to see the fake directory listing. The fix uses Python's `patch` helper that automatically undoes the change after the test. There is no effect on the actual SeedSigner application or its users.

AI review queuedChanging testsby biel · 02f9b8c9 · Dec 17, 2025 · 5 filesMessage 28 · OpaqueInformational 15Details
Commit message · biel

Changing tests

Change tests

Correcting tests

28/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Mentions testing or verification! Too few words to establish purpose! No meaningful explanatory body
Why it was queued
parser or protocol pathsecond-pass: opaque commit messagesecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit only updates test files to remove references to an obsolete 'xpub_export' setting. It does not change any production code, user-facing behavior, or security controls. There is no security issue in this patch.

Security candidateEliminate Export xpub settingsby biel · 2043918d · Dec 17, 2025 · 2 filesMessage 35 · OpaqueInformational 19Details
Commit message · biel

Eliminate Export xpub settings

35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
seed or entropy pathsigning or wallet path
AI analysis · Informational 19/100

This commit removes a user-facing setting that let advanced users disable the 'Export xpub' button. After the change, the Export xpub option is always shown in the seed options menu. This is a feature simplification, not a fix for a code vulnerability. It slightly reduces user-configurable privacy controls because a user can no longer hide the xpub export entry point, but it does not introduce a new exploit or change how xpub export actually works.

Security candidateRemove last "coord" Settings referencesby kdmukai · c49f644f · Dec 16, 2025 · 4 filesMessage 45 · ThinInformational 15Details
Commit message · kdmukai

Remove last "coord" Settings references

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
seed or entropy pathparser or protocol path
AI analysis · Informational 15/100

This commit only renames internal test variables and settings strings from 'coord' to 'xpub_qr'. It is a cleanup change with no effect on the actual wallet software users run, and no security relevance.

Security candidateReplace the "coordinator" setting with "xpub_qr_type"by kdmukai · b90e3d9e · Dec 16, 2025 · 10 filesMessage 50 · ThinInformational 19Details
Commit message · kdmukai

Replace the "coordinator" setting with "xpub_qr_type"

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
seed or entropy pathsigning or wallet path
AI analysis · Informational 19/100

This commit renames a user-facing setting from picking which Bitcoin wallet app ('coordinator') you use to picking the actual QR code format you want when exporting an extended public key (xpub). It is a settings-label and workflow refactor, not a security fix or vulnerability patch. The code still supports the same three QR formats as before (animated UR, static, and the older Specter format), just selected by format name instead of wallet name.

Security candidateLight loop refactor; improved commentsby kdmukai · 9b855c01 · Dec 16, 2025 · 1 fileMessage 45 · ThinInformational 15Details
Commit message · kdmukai

Light loop refactor; improved comments

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
seed or entropy pathsigning or wallet path
AI analysis · Informational 15/100

This commit is a minor code cleanup in a scrolling text animation loop. It moves a brief sleep statement outside an if/else block and rewords comments. There is no security-relevant change.

Security candidateRefactor scrolling loop for better clarity; more commentsby kdmukai · e88d0e45 · Dec 16, 2025 · 1 fileMessage 50 · ThinInformational 12Details
Commit message · kdmukai

Refactor scrolling loop for better clarity; more comments

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
seed or entropy pathsigning or wallet path
AI analysis · Informational 12/100

This commit is a code cleanup of the on-screen text-scrolling animation. It restructures the scrolling loop to make it easier to read and adds explanatory comments. The only functional tweak visible is lowering the threshold that decides when text should scroll from 2 pixels to 1 pixel. There is no indication this change fixes or introduces a security problem.

Security candidateCleanupby kdmukai · b98faa0a · Dec 16, 2025 · 1 fileMessage 0 · OpaqueInformational 15Details
Commit message · kdmukai

Cleanup

0/100 · OpaqueMessage clarity
! Generic or placeholder subject! Too few words to establish purpose! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
seed or entropy pathsigning or wallet path
AI analysis · Informational 15/100

This commit is a minor code cleanup in the user-interface component that handles horizontally scrolling text. It removes a leftover debug print statement and inlines a small helper function that crops and displays the scrolling text. There is no security-relevant change.

Security candidateRelocate logic for min scroll thresholdby kdmukai · fec9fb43 · Dec 16, 2025 · 1 fileMessage 45 · ThinInformational 15Details
Commit message · kdmukai

Relocate logic for min scroll threshold

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
seed or entropy pathsigning or wallet path
AI analysis · Informational 15/100

This commit is a minor user-interface cleanup. It moves a small piece of logic that decides when text is wide enough to start scrolling from one place in the code to another, and adds a debug print statement. There is no security relevance.

Security candidateEliminate unnecessary scrolling for short textby kdmukai · e3c6b639 · Dec 16, 2025 · 1 fileMessage 45 · ThinInformational 15Details
Commit message · kdmukai

Eliminate unnecessary scrolling for short text

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
seed or entropy pathsigning or wallet path
AI analysis · Informational 15/100

This commit is a minor user-interface polish change. It stops text from twitching left and right when only a tiny amount of scrolling would be needed. There is no security relevance visible in the code or commit message.

Security candidateRemove sleeps that cause delays exiting threadby kdmukai · 68de9fff · Dec 15, 2025 · 1 fileMessage 45 · ThinInformational 12Details
Commit message · kdmukai

Remove sleeps that cause delays exiting thread

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
seed or entropy pathsigning or wallet path
AI analysis · Informational 12/100

This commit refactors how a scrolling text display pauses at the start and end of a line. Previously the code simply slept (paused) the entire thread, which made it slow to respond when the user wanted to stop scrolling. The new code tracks pause timing with variables and checks them in the main loop, so the thread can exit promptly when asked. There is no security issue visible in this change.

Security candidatestyle: fix typos in source code comments and stringsby securesigner · d5729358 · Dec 14, 2025 · 4 filesMessage 50 · ThinInformational 15Details
Commit message · securesigner

style: fix typos in source code comments and strings

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
seed or entropy pathsigning or wallet path
AI analysis · Informational 15/100

This commit only fixes spelling mistakes in comments and log messages. No actual program code, behavior, or security controls were changed.

Security candidateInitial Hindi supportby kdmukai · 1769938c · Dec 14, 2025 · 3 filesMessage 28 · OpaqueInformational 15Details
Commit message · kdmukai

Initial Hindi support

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
seed or entropy pathsigning or wallet path
AI analysis · Informational 15/100

This commit adds Hindi language support to the SeedSigner wallet interface. It registers a new Hindi font, adjusts font sizes for Hindi text, and adds Hindi to the language settings list. There is no security-relevant change.

Security candidateRemove `TextArea.allow_text_overflow`by kdmukai · 1f188754 · Dec 13, 2025 · 7 filesMessage 35 · OpaqueInformational 17Details
Commit message · kdmukai

Remove `TextArea.allow_text_overflow`

35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
memory safetyseed or entropy pathsigning or wallet path
AI analysis · Informational 17/100

This commit removes a UI flag called allow_text_overflow from SeedSigner's on-screen text rendering code. Previously, the flag decided whether text that was too long should be silently allowed to spill past its box (overflow) or trigger an error. After the change, the code always allows overflow and just logs a warning. This is a code-cleanup and UI-layout change; it does not introduce a way for an attacker to steal funds or keys, but it could make some translated screens look clipped or unreadable.

Security candidateRemove now-unused `has_passphrase` attrby kdmukai · 639c2a14 · Dec 10, 2025 · 2 filesMessage 45 · ThinInformational 15Details
Commit message · kdmukai

Remove now-unused `has_passphrase` attr

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
access controlseed or entropy pathsigning or wallet path
AI analysis · Informational 15/100

This commit simply removes an unused attribute called has_passphrase from two screen classes and the two places that passed it in. There is no functional change, no bug fix, and no security relevance visible in the code change.

Security candidateRemove dead codeby kdmukai · 0736e066 · Dec 10, 2025 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · kdmukai

Remove dead code

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
seed or entropy pathsigning or wallet path
AI analysis · Informational 15/100

This commit simply deletes an unused helper function that could generate a seed phrase from an image. There is no security fix or vulnerability here—it's routine cleanup of leftover code.

Security candidateRemove dead codeby kdmukai · dd6277b8 · Dec 10, 2025 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · kdmukai

Remove dead code

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
seed or entropy pathsigning or wallet path
AI analysis · Informational 15/100

This commit removes unused code from a single screen file. One line that set a scroll position variable was never referenced anywhere, and an entire 'Powering Off' screen class was defined but apparently not used. There is no security-relevant change here—just cleanup.

Security candidateRemove dead code and debugging codeby kdmukai · 6fb11166 · Dec 10, 2025 · 1 fileMessage 45 · ThinInformational 15Details
Commit message · kdmukai

Remove dead code and debugging code

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
seed or entropy pathsigning or wallet path
AI analysis · Informational 15/100

This commit removes unused variables and debugging-only code from the QR code scanning screen. There is no security-relevant change; it is purely cleanup of leftover development helpers and a counter that was no longer used.

Security candidateRemove dead codeby kdmukai · aa4b84c9 · Dec 10, 2025 · 4 filesMessage 28 · OpaqueInformational 12Details
Commit message · kdmukai

Remove dead code

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
seed or entropy pathsigning or wallet path
AI analysis · Informational 12/100

This commit removes unused code and fixes a minor variable-name inconsistency in the user interface code. There is no apparent security relevance: it deletes an unused screen class, removes an unused loading-screen flag, drops an unused selection-button setting, and renames a throwaway variable in a font-size calculation so the code is internally consistent. None of these changes affect how private keys, seeds, or transactions are handled.

Security candidateRemove dead codeby kdmukai · 2868b235 · Dec 10, 2025 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · kdmukai

Remove dead code

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
seed or entropy pathsigning or wallet path
AI analysis · Informational 15/100

This commit removes unused variables and commented-out code from a single on-screen keyboard file. It is a routine cleanup with no visible security effect.

Security candidateRemove dead code, unused constantsby kdmukai · 74b57927 · Dec 10, 2025 · 1 fileMessage 45 · ThinInformational 15Details
Commit message · kdmukai

Remove dead code, unused constants

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
seed or entropy pathsigning or wallet path
AI analysis · Informational 15/100

This commit is a routine cleanup: it removes unused color constants, unused icon symbols, an unused helper function for centering text, and an unused empty list. There is no change to how the app behaves or to any security-sensitive logic.

Security candidateRemove dead codeby kdmukai · 060130f9 · Dec 10, 2025 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · kdmukai

Remove dead code

28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body! Opaque security-relevant change
Why it was queued
seed or entropy pathsigning or wallet path
AI analysis · Informational 15/100

This commit simply deletes an unused helper method that could create a class instance without hardware initialization. There is no functional change to the running program because the method was not being called anywhere. It is a routine code cleanup, not a security fix.

Security candidateImprove commenting and solve minor nitsby alvroble · c565b825 · Dec 9, 2025 · 1 fileMessage 45 · ThinInformational 15Details
Commit message · alvroble

Improve commenting and solve minor nits

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
seed or entropy pathsigning or wallet pathparser or protocol path
AI analysis · Informational 15/100

This commit only rewrites comments and removes an unused variable in a single file. It does not change any program logic, security behavior, or functionality. There is no security issue here.