KX
← All projectsKrux

Krux

Open-source signing firmware for Kendryte K210 devices.

BitcoinHardware walletsNormal
Repository coverage

252 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.

61security candidates45second-pass queue223AI analyses
2commits · 30 days
4commits · 60 days
101commits · 180 days
169commits · 365 days
Backfill bands
Aug 5 → Feb 6116 seen6 candidatesComplete
Feb 6 → Jun 639 seen3 candidatesComplete
Jun 6 → Jul 622 seen1 candidatesComplete
Jul 6 → Aug 538 seen5 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.

65/100 average clarity
64Strong · 80–100
76Adequate · 60–79
96Thin · 40–59
16Opaque · 0–39
6security 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.
Odudex291429272
odudex923090159
Tads361036063
qlrd20216083
Jean Do1928067
kdmukai424066
tadeubas414038
Naman0151707059
kkdao12012083
bitcoisas505066
joaozinhom402067
Naman Gupta202079
Analysis record

Published AI watches

Last scanned 43 minutes ago

Informational 15 AI analysisMessage 62 · Adequate
KX KruxKrux BitcoinHardware wallets

chore: updates MaixPy glyphs (adds: 49, removes: 4)

This commit only updates a Git submodule pointer for the MaixPy firmware dependency. The actual code changes are stored in the linked submodule repository, not in this commit. There is no visible security-relevant change here.

f963e035by Jean Do+1−11 file
No security note in commit
Informational 4 AI analysisMessage 57 · Thin
KX KruxKrux BitcoinHardware wallets

fix: use latest MaixPy w/ pr_57

This commit only updates a submodule pointer for MaixPy, a firmware dependency. The actual code changes are not visible in this diff because they live in the separate MaixPy repository. Without seeing what changed in MaixPy, we cannot dete…

31754785by Jean Do+1−11 file
No security note in commit
Informational 15 AI analysisMessage 72 · Adequate
KX KruxKrux BitcoinHardware wallets

test: cover Back and failure paths for SD card and QR loading

This commit only adds and updates automated tests. It does not change any production code, so it cannot introduce a security vulnerability or directly fix one in the shipped firmware. The tests verify that pressing 'Back' or cancelling a c…

7a2fcd9eby notTanveer+297−89 files
No security note in commit
Informational 21 AI analysisMessage 62 · Adequate
KX KruxKrux BitcoinHardware wallets

fix: do not report "Failed to load" when the user backs out

This commit is a user-experience fix: it stops the Krux bitcoin hardware-wallet firmware from showing a scary 'Failed to load' error when the user simply presses Back or leaves the camera/SD-card picker. The change also moves SD-card error…

No memory-safety, cryptographic, or authorization changesError-message UX change onlyNo new attack surface introduced
1e9ea474by notTanveer+54−509 files
No security note in commit
Informational 15 AI analysisMessage 57 · Thin
KX KruxKrux BitcoinHardware wallets

fix(i18n): add scan and manual labels

This commit simply adds two missing translated labels, 'manual' and 'scan', to the project's user-interface language files. It is a routine internationalization (i18n) fix with no security relevance.

00e82270by Naman015+46−023 files
No security note in commit
Low 26 AI analysisMessage 100 · Strong
KX KruxKrux BitcoinHardware wallets

docs: TC-code - warn about privacy when filling flash with entropy from camera

This commit does not fix a software bug. It adds documentation warnings and an on-screen reminder telling users to read the docs before using the TC Code tamper-detection feature. The underlying behavior being warned about is that Krux can…

Privacy warning added for unscrambled camera frames stored in flashOn-device prompt added to read documentation before TC Code setupNo cryptographic or storage-behavior change in the diff
1cb1cc0cby odudex+33−225 files
Vendor flagged security relevance
Informational 15 AI analysisMessage 57 · Thin
KX KruxKrux BitcoinHardware wallets

docs: update mnemonic loading flow

This commit only updates user documentation and simulator test scripts to match a reorganized menu for loading a wallet recovery phrase. No actual wallet or security code was changed, so it does not create or fix a security vulnerability.

e264e2f5by Naman015+139−9522 files
No security note in commit
Moderate 66 AI analysisMessage 45 · Thin
KX KruxKrux BitcoinHardware wallets

Merge branch 'release-26.08.0'

This is a routine release merge for Krux firmware (version 26.08.0). It includes several genuine security fixes: a heap buffer overflow in camera-based entropy generation for a discontinued device, stricter fee calculation when signing Bit…

Heap buffer overflow fix in camera entropy module (discontinued Maix Bit only)PSBT fee calculation stricter checks and unverified-input-amount warningStored mnemonic file corruption now preserved instead of overwritten
be5eda28by odudex+4335−3028123 files
Vendor flagged security relevance
Informational 15 AI analysisMessage 40 · Thin
KX KruxKrux BitcoinHardware wallets

docs: update CHANGELOG

This commit only updates three date lines in the CHANGELOG.md file, changing '2025' to '2026' for three release entries. It does not modify any source code, build scripts, or documentation with security implications. The change is purely c…

ec058d86by odudex+3−31 file
No security note in commit
Moderate 66 AI analysisMessage 85 · Strong
KX KruxKrux BitcoinHardware wallets

fix: bind BBQr parts to the first part of the stream

This commit fixes Krux's QR code scanner so that when it reads a series of animated BBQr codes, every later frame must match the encoding and file type announced by the first frame, must agree on the total number of frames, and cannot over…

Input validation added for multi-part BBQr streamsMemory exhaustion mitigation via accumulated payload capAnti-splicing: parts must agree with first part's encoding and file type
0b3e01b7by odudex+86−13 files
No security note in commit
Informational 15 AI analysisMessage 40 · Thin
KX KruxKrux BitcoinHardware wallets

docs: update CHANGELOG

This commit only updates the project's CHANGELOG.md file. It adds text describing several bug fixes and improvements that were apparently made in prior code changes, but no actual code is changed in this commit. By itself, this documentati…

4c05cefbby odudex+9−11 file
No security note in commit
Informational 0 AI analysisMessage 40 · Thin
KX KruxKrux BitcoinHardware wallets

chore(Maixpy): bump cUR

This commit appears to be a routine version bump of a component called 'cUR' inside the MaixPy firmware build. No actual code changes are visible in the provided diff, and the commit message gives no indication of a security fix or vulnera…

74d6ed40by odudex+1−11 file
No security note in commit
Informational 15 AI analysisMessage 57 · Thin
KX KruxKrux BitcoinHardware wallets

chore: bump version to 26.08.0

This commit is a routine version bump from 26.04.0 to 26.08.0. It only updates version strings in documentation, build files, and source metadata. No code behavior changes. The changelog text mentions a previously fixed heap buffer overflo…

Changelog references a prior heap buffer overflow in Shannon entropy module (camera frame copy into fixed 320x240 RGB565 buffer)No actual code or security fix present in this commit
dea991dfby odudex+5−55 files
Vendor flagged security relevance
Informational 2 AI analysisMessage 57 · Thin
KX KruxKrux BitcoinHardware wallets

chore: bump MaixPy with updated glyphs

This commit appears to update a submodule or dependency called MaixPy to a newer version that includes updated visual glyphs (small icons/symbols). The title and message describe it as a routine maintenance chore, not a security fix. No ac…

a9329228by odudex+1−11 file
No security note in commit
Informational 15 AI analysisMessage 85 · Strong
KX KruxKrux BitcoinHardware wallets

fix: register embed_fire in the bdftokff device list

This commit fixes a build-time font-generation script so that a newly supported device ('embed_fire') is recognized. Before the fix, the script printed an error but still produced the same font files. There is no security issue.

f15308e4by odudex+1−01 file
No security note in commit
Moderate 63 AI analysisMessage 57 · Thin
KX KruxKrux BitcoinHardware wallets

docs: add PSBT input amount fixes to CHANGELOG

This commit only updates the project's CHANGELOG.md to document earlier fixes related to PSBT (Partially Signed Bitcoin Transaction) fee and amount handling. It does not contain any code changes itself. The changelog entries describe secur…

Changelog documents prior PSBT fee/amount validation fixesMentions insufficient coordinator data as a security concernNo actual code or test changes in this commit
48920c31by odudex+4−01 file
Vendor flagged security relevance
High 78 AI analysisMessage 95 · Strong
KX KruxKrux BitcoinHardware wallets

fix: verify PSBT input amounts before showing the fee

This commit fixes a security flaw in Krux, a Bitcoin signing device. Before the fix, an attacker could trick the device into showing a low transaction fee on screen while actually signing a much higher fee. The fix makes the device verify …

Fixes fee-display/sighash amount mismatchAdds prevout txid hash verification for non_witness_utxoMandates non_witness_utxo for legacy inputs
fc808059by odudex+353−122 files
Vendor flagged security relevance
Moderate 66 AI analysisMessage 85 · Strong
KX KruxKrux BitcoinHardware wallets

fix: reject a PSBT whose outputs exceed its inputs

This commit fixes a bug in Krux, a Bitcoin signing device, where a malformed transaction whose outputs spend more than its inputs could be loaded and shown to the user. Normally such a transaction is impossible on the Bitcoin network, but …

Input validation gap in PSBT parsingUI rendering bug masking invalid transaction economicsPotential social-engineering / user-confusion attack
d6813d88by odudex+52−02 files
Vendor flagged security relevance
Informational 15 AI analysisMessage 50 · Thin
KX KruxKrux BitcoinHardware wallets

i18n: translate the unverified input amounts warning

This commit only adds translations for two existing warning messages in the Krux Bitcoin hardware wallet software. It does not change any code logic, security behavior, or fix any vulnerability. The messages warn users that displayed fees …

bdaed1a1by odudex+46−023 files
No security note in commit
Moderate 62 AI analysisMessage 90 · Strong
KX KruxKrux BitcoinHardware wallets

feat: warn when PSBT input amounts cannot be verified

This commit adds a warning screen to Krux, a hardware signing device, when it is asked to sign a multi-input Bitcoin transaction where the amounts of some inputs cannot be independently verified. The risk is that a malicious transaction co…

New user-facing warning for unverified multi-input SegWit amountsDetection logic tied to BIP143 signature semantics and inp.is_verifiedDoes not enforce previous-transaction inclusion; user can still proceed
518b3314by odudex+159−24 files
Vendor flagged security relevance
Repository ledger

Explore captured commits

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

Lower-prioritydocs: add Maix Bit removal and Shannon calc fix to CHANGELOGby odudex · b0a7357e · Jul 31, 2026 · 1 fileMessage 62 · AdequateModerate 53Details
Commit message · odudex

docs: add Maix Bit removal and Shannon calc fix to CHANGELOG

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
documentation-only discount
AI analysis · Moderate 53/100

This commit is a documentation update to the project's changelog. It describes two security-related changes that were apparently made in earlier code: a heap buffer overflow in the camera-based entropy (randomness) module that could only be triggered on a discontinued device called the Maix Bit, and the removal of an unused deterministic random function from the firmware. The commit itself only edits the changelog text; it does not contain the actual code fixes.

Security candidatechore: bump MaixPy with Shannon changes and RNG removalby odudex · 5c4ece9a · Jul 31, 2026 · 1 fileMessage 82 · StrongModerate 55Details
Commit message · odudex

chore: bump MaixPy with Shannon changes and RNG removal

Fixes the shannon heap overflow, removes the unused os.urandom binding,
and drops the Maix Bit build project.

82/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Names security-relevant behavior explicitly
Why it was queued
entropy or randomnessmemory safetyboot or update path
AI analysis · Moderate 55/100

This commit updates a bundled firmware component called MaixPy. The commit message says it fixes a 'Shannon heap overflow,' removes an unused random-number binding, and drops support for one hardware variant (Maix Bit). A heap overflow is a memory corruption bug that can sometimes be exploited to run attacker-controlled code, but the actual code change is just a one-line version bump of a submodule, so we cannot verify the fix from the diff alone.

Security candidatefix: remove Maix Bit and CIF camera supportby odudex · 8090ac73 · Jul 31, 2026 · 9 filesMessage 85 · StrongModerate 52Details
Commit message · odudex

fix: remove Maix Bit and CIF camera support

The device was discontinued in 25.09.0 and has no known users. Its CIF
framesize was the only caller that fed the shannon entropy module a frame
larger than QVGA, overflowing that module's scratch buffer by 49152 bytes.

Also drops the OV5642 sensor handling, which only the Maix Bit used.

85/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Names security-relevant behavior explicitly
Why it was queued
entropy or randomnessmemory safetyboot or update path
AI analysis · Moderate 52/100

This commit removes support for an old, discontinued hardware device called the Maix Bit from the Krux Bitcoin wallet firmware. The commit message says the Maix Bit's camera resolution (CIF) was the only one that fed frames larger than QVGA into a 'shannon entropy' module, overflowing that module's scratch buffer by 49,152 bytes. In plain terms, this is a fix for a buffer overflow bug, but the fix is to delete the only hardware configuration that triggered it rather than enlarge the buffer. Because the device was already discontinued and reportedly has no users, the practical risk is low, but the underlying overflow condition is a real memory-safety issue.

Security candidaterefactor: use native uUR on tests and simulatorby odudex · 2fe2f5f5 · Jul 31, 2026 · 19 filesMessage 90 · StrongInformational 15Details
Commit message · odudex

refactor: use native uUR on tests and simulator

Replace the pure-Python ur/urtypes vendor packages with the uUR CPython
extension built from the bc-ur submodule, so host and device run identical
UR code. Drops the simulator shim that mapped one API onto the other.

Tests now need a C compiler and Python headers.

90/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
signing or wallet pathboot or update path
AI analysis · Informational 15/100

This commit is a routine engineering cleanup: it removes a Python-only compatibility layer (a 'shim') used for testing and simulation, and makes the test environment use the same C-language UR encoder/decoder module that the real hardware device uses. There is no security bug being fixed here; the change is about making tests more realistic and reducing duplicated code.

AI review queuedrefactor: narrow parse_address fallbacks to EmbitError in wallet.pyby kkdao · a5fb4737 · Jul 29, 2026 · 2 filesMessage 62 · AdequateLow 34Details
Commit message · kkdao

refactor: narrow parse_address fallbacks to EmbitError in wallet.py

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 34/100

This change fixes a bug where pressing a device's cancel/back button during address parsing could be ignored or misreported as an 'invalid address' instead of letting the user exit. The code previously caught every possible error (including user interrupts) and treated them all as address validation failures. Now it only catches actual address-format errors from the embit library, allowing legitimate user interrupts to propagate normally.

AI review queuedfix: reject base58 address with unknown version byte in parse_addressby kkdao · 63e8b8e5 · Jul 29, 2026 · 2 filesMessage 93 · StrongModerate 62Details
Commit message · kkdao

fix: reject base58 address with unknown version byte in parse_address

address_to_scriptpubkey returns None (no exception) for a base58 address
with a valid checksum but a version byte matching no network. The final
parse_address block only caught exceptions, so such an address was
returned as valid. Capture the return and require a Script. Per review
on #898.

93/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Moderate 62/100

This fix closes a hole where a Bitcoin address that looks valid (correct checksum) but belongs to no known network could be accepted by Krux's address parser. Before the patch, the parser only caught thrown errors; because the underlying library quietly returns nothing for an unknown address version, such an address slipped through as valid. The patch now checks that a real script output was produced and rejects the address otherwise. This could matter if a user scanned a malformed or wrong-network address and the device treated it as valid.

AI review queuedrefactor: drop change-log notes from parse_wallet except commentsby kkdao · 88adc60a · Jul 29, 2026 · 1 fileMessage 93 · StrongInformational 15Details
Commit message · kkdao

refactor: drop change-log notes from parse_wallet except comments

The comments explained what changed relative to the old bare excepts
(interrupts no longer swallowed), which belongs in the commit message,
not the code. Keep only the forward-looking rationale. Per review on #898.

93/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit only removes historical changelog-style comments from the code and rewrites the remaining comments to describe the current behavior. No code logic was changed, so there is no security impact.

AI review queuedrefactor: catch Exception, not bare except, in parse_wallet fallbacksby kkdao · 6f617710 · Jul 29, 2026 · 2 filesMessage 62 · AdequateLow 34Details
Commit message · kkdao

refactor: catch Exception, not bare except, in parse_wallet fallbacks

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 34/100

This commit tightens error handling in Krux's wallet parsing. Previously, the code used bare 'except:' clauses that would catch everything, including KeyboardInterrupt and SystemExit. Those special exceptions should normally be allowed to propagate so a user can cancel an operation or the program can shut down cleanly. The change replaces the bare catches with 'except Exception:', which still handles ordinary parsing errors but lets KeyboardInterrupt and SystemExit through. A new test confirms KeyboardInterrupt now propagates from all three parsing fallback paths.

Security candidaterefactor: adapt UR decoding to cUR state machine APIby odudex · f90219e3 · Jul 29, 2026 · 4 filesMessage 85 · StrongLow 29Details
Commit message · odudex

refactor: adapt UR decoding to cUR state machine API

receive_part now returns a decoder state instead of raising, and is_complete/is_success were replaced by the state attribute. Transient errors are ignored while scanning; terminal ones abort the capture.

85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
boot or update path
AI analysis · Low 29/100

This commit refactors how Krux handles animated QR codes in the 'UR' format. It swaps an older decoder API for a newer state-machine API. The visible change is that transient decoding errors are now ignored while scanning, and only terminal errors stop capture. The commit itself is described as a refactor, but the change in error handling could affect security if it hides or delays detection of malformed or malicious QR frames.

Security candidatetest: build embit's C libsecp256k1 for testsby odudex · ac3ea482 · Jul 27, 2026 · 3 filesMessage 95 · StrongInformational 15Details
Commit message · odudex

test: build embit's C libsecp256k1 for tests

Without it embit falls back to its pure Python EC implementation, which does
not always behave like the C library the firmware runs: firmware.bin.bad.sig
raises while parsing instead of failing verification, so the Bad signature
branch in firmware.py was never exercised. Adds poe tasks to build and to
check the active backend, wired into CI, which now fails on the fallback.

Full suite goes from 118s to 84s.

95/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Names security-relevant behavior explicitly
Why it was queued
signing boundarydefensive validation
AI analysis · Informational 15/100

This commit only changes how automated tests are run. It builds a C cryptography library during testing so the test environment matches the real firmware more closely. There is no change to the actual Krux firmware or wallet code, and no security vulnerability is being fixed.

Lower-priorityperf(test): stub gc.collect during testsby odudex · 29e4d43b · Jul 27, 2026 · 2 filesMessage 90 · StrongInformational 15Details
Commit message · odudex

perf(test): stub gc.collect during tests

krux calls gc.collect() to manage the device's small heap. On CPython each
call walks the much bigger test heap of mock objects for no benefit: 151s to
118s for the full suite, same coverage.

90/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification
AI analysis · Informational 15/100

This commit only changes test infrastructure. It replaces the garbage collector's collect() function with a no-op during automated tests so the test suite runs faster. It does not change any code that runs on real Krux devices or affect how user funds or data are handled.

Lower-priorityci: allow perf commit typeby odudex · 8e0ac0cb · Jul 27, 2026 · 1 fileMessage 57 · ThinInformational 15Details
Commit message · odudex

ci: allow perf commit type

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
documentation-only discount
AI analysis · Informational 15/100

This change simply adds 'perf' to the list of allowed commit message types in a GitHub Actions workflow that checks whether commit messages follow a conventional format. It has no effect on the Krux software users run, on private keys, wallets, or any security-sensitive behavior.

Security candidatefix(test): fake the clock in test_fill_flash timeout testby qlrd · 9fecf150 · Jul 27, 2026 · 1 fileMessage 95 · StrongInformational 15Details
Commit message · qlrd

fix(test): fake the clock in test_fill_flash timeout test

test_fill_flash_insufficient_entropy_scenario waited 25 real seconds for
MAX_CAPTURE_PERIOD to elapse, spinning ~500k iterations that piled up mock
call records. Patching time.time in fill_flash fires the timeout after 4
frames: 25.1s to 0.09s, same coverage.

95/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
entropy or randomness
AI analysis · Informational 15/100

This commit only changes a test file to make it run faster by faking the system clock. It does not modify any production code, so it has no direct security impact on users of the Krux device or software.

Lower-prioritytest: cover generated mnemonic action flowby Naman015 · 21bd8e4c · Jul 27, 2026 · 1 fileMessage 67 · AdequateInformational 15Details
Commit message · Naman015

test: cover generated mnemonic action flow

67/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Mentions testing or verification! No meaningful explanatory body
AI analysis · Informational 15/100

This commit only adds new automated tests for the wallet login flow. It does not change any production code, so it cannot introduce a security vulnerability or fix one directly. The tests verify that menu navigation works correctly when a user creates a new wallet from a generated mnemonic versus loading an existing one.

AI review queuedchore(i18n): update generated mnemonic action translationsby Naman015 · 022b70d5 · Jul 27, 2026 · 23 filesMessage 62 · AdequateInformational 15Details
Commit message · Naman015

chore(i18n): update generated mnemonic action translations

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
translation-only discountsecond-pass: unusually broad change
AI analysis · Informational 15/100

This commit is a routine translation update. It adds or updates translated text strings for user interface labels such as "Continue", "Wallet Options", "Standard", and "Vertical" across multiple languages. There are no code logic changes, no security fixes, and no behavior changes.

Lower-priorityrefactor: extract wallet info menu helperby odudex · 1b068748 · Jul 27, 2026 · 1 fileMessage 57 · ThinInformational 15Details
Commit message · odudex

refactor: extract wallet info menu helper

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
AI analysis · Informational 15/100

This commit is a simple code cleanup: it pulls duplicated code for drawing a wallet information screen into a single reusable helper function. There is no change to what the program does, no new behavior, and no security issue visible in the diff.

AI review queueddocs: add generated mnemonic flow screenshotsby Naman015 · 61807e7e · Jul 27, 2026 · 8 filesMessage 57 · ThinInformational 15Details
Commit message · Naman015

docs: add generated mnemonic flow screenshots

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit only updates user documentation. It adds new screenshots showing how to create a new wallet mnemonic and updates the script that automatically generates those screenshots. There are no code changes that affect security.

Lower-priorityfeat: simplify generated mnemonic actionsby Naman015 · aed4b007 · Jul 27, 2026 · 1 fileMessage 57 · ThinInformational 15Details
Commit message · Naman015

feat: simplify generated mnemonic actions

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
AI analysis · Informational 15/100

This commit reorganizes the on-screen menu shown after a wallet key is generated or loaded in the Krux firmware. It splits the existing options into a two-level menu for newly generated mnemonics while keeping the old layout for existing ones. There is no security-relevant change visible in the code.

Lower-prioritydocs: document generated mnemonic actionsby Naman015 · c0759d9e · Jul 27, 2026 · 2 filesMessage 57 · ThinInformational 15Details
Commit message · Naman015

docs: document generated mnemonic actions

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
documentation-only discount
AI analysis · Informational 15/100

This commit only updates user documentation and the changelog to describe a recent user-interface change for generated mnemonics. It does not modify any code, cryptographic logic, or security behavior, so it has no direct security relevance.

Lower-prioritychore(Embit): bump to fff7ffaby odudex · 77fc9698 · Jul 27, 2026 · 1 fileMessage 57 · ThinInformational 2Details
Commit message · odudex

chore(Embit): bump to fff7ffa

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
AI analysis · Informational 2/100

This commit is a routine dependency update that bumps the bundled 'embit' library to a newer commit. No actual code changes are shown, and no security relevance is stated in the commit message or title.

Lower-prioritydocs(parts): mark Maix Amigo as discontinued, drop sale linksby joaozinhom · 1b311fad · Jul 10, 2026 · 1 fileMessage 62 · AdequateInformational 15Details
Commit message · joaozinhom

docs(parts): mark Maix Amigo as discontinued, drop sale links

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
documentation-only discount
AI analysis · Informational 15/100

This commit only updates project documentation. It removes shopping links for a discontinued hardware device and adds a note that the device is no longer for sale. There is no code change and no security relevance.

Lower-prioritychore: remove unused color constantsby qlrd · 3c5f395c · Jul 10, 2026 · 1 fileMessage 88 · StrongInformational 15Details
Commit message · qlrd

chore: remove unused color constants

This commit removes two constants on `src/krux/themes.py` once the
`vulture` tool found with a 60% of confidence their possibility to be a
dead code.

Fix #900

Co-authored-by: Naman Gupta <55298452+Naman015@users.noreply.github.com>

88/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
AI analysis · Informational 15/100

This is a routine cleanup commit that deletes two unused color constants (LIGHTGREY and PURPLE) from a theme file. It does not change any behavior, fix any bug, or alter any security-related logic.

Lower-prioritydocs(parts): mark Maix Amigo as discontinued, drop sale linksby joaozinhom · 7ea3f95e · Jul 10, 2026 · 1 fileMessage 62 · AdequateInformational 15Details
Commit message · joaozinhom

docs(parts): mark Maix Amigo as discontinued, drop sale links

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
documentation-only discount
AI analysis · Informational 15/100

This commit only updates project documentation. It marks the Maix Amigo hardware device as discontinued and removes links to stores that used to sell it. There are no code changes and no security implications.

Security candidatechore: update cUR and k_quirkby odudex · f4796afe · Jul 8, 2026 · 1 fileMessage 57 · ThinInformational 0Details
Commit message · odudex

chore: update cUR and k_quirk

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
boot or update path
AI analysis · Informational 0/100

The commit title says it is a routine maintenance update ('chore') for two internal items named cUR and k_quirk in the MaixPy firmware file. No diff content is available, and no verified references were supplied, so there is no visible evidence of any security change.

Security candidatefix: pin gcc base image by digestby odudex · ceefbb19 · Jul 8, 2026 · 1 fileMessage 57 · ThinLow 25Details
Commit message · odudex

fix: pin gcc base image by digest

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
access control
AI analysis · Low 25/100

This change locks the Docker build to one specific, unchangeable version of the GCC compiler image by adding a cryptographic fingerprint (SHA digest). Without this, an attacker who compromises the GCC image registry could silently replace the 'gcc:12-bookworm' image with a malicious one, potentially injecting backdoors into Krux firmware builds. Pinning by digest prevents the build from accepting a substituted image, but it does not fix any already-known vulnerability in the code itself.