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.
Message quality measures whether a commit identifies its scope, purpose, rationale, testing, and supporting references. It does not change the security-severity score.
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.
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…
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…
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
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.
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
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.
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
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…
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
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…
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…
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
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…
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.
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
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
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
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 …
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
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly! No meaningful explanatory body
Why it was queued
documentation-only discount
AI analysis · Informational 15/100
This commit only adds a SECURITY.md file to the repository. It is a documentation-only change that tells people how to report security bugs. It does not change any code, fix any vulnerability, or introduce any security risk.
Lower-prioritydocs: tighten and clarify CONTRIBUTING.mdby odudex · 933e4d0b · May 25, 2026 · 1 fileMessage 72 · AdequateInformational 15Details
Commit message · odudex
docs: tighten and clarify CONTRIBUTING.md
Make the contribution guide more concise, trim topics beyond the document's scope, and fix inaccuracies
72/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
Why it was queued
documentation-only discount
AI analysis · Informational 15/100
This commit is a routine rewrite of the project's CONTRIBUTING.md guide. It shortens instructions for contributors, fixes wording, and updates examples, but does not change any program code, build scripts, tests, or security behavior. There is no security issue here.
`CONTRIBUTING.md` is a important file that guides new developers through the standards built by krux team through years. This isn't a monad and could be changed at time to time.
80/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
documentation-only discount
AI analysis · Informational 15/100
This commit only adds a CONTRIBUTING.md file to the repository. It is a documentation-only change that explains how people can contribute to the Krux firmware project. There are no code changes, no bug fixes, and no security-related modifications.
Lower-prioritydocs: add Embit and k_quirc updates to CHANGELOGby odudex · 9ef58035 · May 14, 2026 · 1 fileMessage 57 · ThinInformational 15Details
Commit message · odudex
docs: add Embit and k_quirc updates to CHANGELOG
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 the project's CHANGELOG.md to document two prior dependency changes (an Embit library update and replacing a custom QR-code decoding library with k_quirc). It contains no code changes, no bug fixes, and no security claims.
✓ Specific, 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 10/100
This commit appears to be a routine maintenance update that bumps the MaixPy firmware submodule to a newer version and updates another component (uUC). The title describes it as a cleanup chore. No actual code changes are visible in the provided diff, and no security-related information is present in the commit message or materials.
Lower-prioritychore: update Embit requires Docker image and toolchain rebuild in order to have compliant python version.by odudex · 5271ebdb · May 14, 2026 · 2 filesMessage 89 · StrongInformational 15Details
Commit message · odudex
chore: update Embit requires Docker image and toolchain rebuild in order to have compliant python version.
89/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Explains rationale or failure mode
AI analysis · Informational 15/100
This commit updates the build environment for the Krux project. It changes the Docker base image from an older Debian version (Bullseye with GCC 9.5.0) to a newer one (Bookworm with GCC 12) and updates the bundled 'embit' library. The commit message frames this as a routine maintenance chore needed to keep Python versions compatible. There is no indication in the commit itself that this fixes a security vulnerability.
docs: add Stackbit 1248 vertical layout 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 · Informational 15/100
This commit only updates the project's CHANGELOG.md file to document a new vertical layout option for the Stackbit 1248 backup display. It adds three lines of text describing a user-facing feature. There are no code changes, no configuration changes, and no security-relevant modifications.
Test grouped/compact layouts + 24-word pagination.
82/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Mentions testing or verification
AI analysis · Informational 15/100
This commit only adds and updates automated tests for a backup-screen layout feature called Stackbit. It does not change any production code, so it cannot introduce a security vulnerability or fix one.
docs: add Stackbit 1248 vertical layout screenshots and documentation
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 adds documentation screenshots and text describing a vertical layout for the Stackbit 1248 metal backup format. It also updates a simulator script used to capture those screenshots. There is no code change that affects security.
feat: add vertical export methods to Stackbit 1248
Add grouped and compact export methods.
62/100 · AdequateMessage clarity
✓ Specific, 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 adds new on-screen backup layout options for a Bitcoin hardware wallet feature called Stackbit 1248. It only changes how the wallet's seed phrase is drawn on the device display so users can physically punch it into a metal backup card. There is no security vulnerability visible in the change.
Lower-priorityfeat(i18n): add Standard and Vertical strings for stackbit menuby bitcoisas · effba1bb · May 14, 2026 · 11 filesMessage 62 · AdequateInformational 15Details
Commit message · bitcoisas
feat(i18n): add Standard and Vertical strings for stackbit menu
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 discount
AI analysis · Informational 15/100
This commit only adds translated text strings for two menu labels, 'Standard' and 'Vertical', used in the stackbit feature. It does not change any program logic, security checks, or data handling. There is no security relevance.
This commit add some common AI configuration files, such as `CLAUDE.md`, `AGENT.md`, `.cursorrules` and `.claude/`, since it should be a per-maintainer policy on local development machine.
80/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
AI analysis · Informational 15/100
This commit only updates the project's .gitignore file to exclude common AI assistant configuration files (like CLAUDE.md, AGENT.md, .cursorrules, and folders such as .claude/). It does not change any executable code, build scripts, cryptographic logic, or user-facing behavior. There is no security relevance.
AI review queuedfeat: add flash_success method to Page class (#853)by Naman Gupta · 2191ddde · May 7, 2026 · 14 filesMessage 93 · StrongInformational 15Details
Commit message · Naman Gupta
feat: add flash_success method to Page class (#853)
added flash_success that uses theme.go_color, giving success confirmations a distinct green color vs default foreground. Fix #852
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 is a user-interface polish change: it adds a new green-colored success message method and switches existing success messages from the default text color to green. There is no security-relevant behavior change.
Security candidatefeat: migrate UR encoding to uUR MicroPython C moduleby odudex · 401c70c4 · May 6, 2026 · 12 filesMessage 95 · StrongLow 32Details
Commit message · odudex
feat: migrate UR encoding to uUR MicroPython C module
Switch src/krux from the pure-Python urtypes and foundation-ur-py packages to the new uUR C module (built into MaixPy). The simulator and tests reach the same API surface through a sys.modules shim that re-exports the Python packages.
chore: update to latest Maixpy develop commit
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
signing or wallet pathboot or update path
AI analysis · Low 32/100
This commit swaps out the pure-Python QR code encoding/decoding libraries used by the Krux hardware wallet for a new C module called uUR. The stated goal is faster scanning and lower memory use. The change touches code that handles Bitcoin wallet descriptors, seed phrases, and signed transactions (PSBTs). There is no direct evidence in the commit of a security vulnerability, but any rewrite of code that parses cryptographic data deserves careful review because a bug could in theory cause the wallet to misread a transaction or seed. The commit does not describe itself as a security fix.
✓ Subject identifies a change✓ Uses a recognizable type or scope! No meaningful explanatory body
AI analysis · Low 29/100
This commit updates the Pillow image-processing library from version 12.1.1 to 12.2.0 in Krux's optional simulator dependencies. The change itself only bumps version numbers and lock-file hashes; it does not modify Krux application code. Pillow 12.2.0 is a routine maintenance release that fixes several bugs and security issues in image handling, so the update is generally beneficial. However, the commit message does not say which vulnerabilities are being addressed, and the diff provides no direct evidence of a specific security problem in Krux.
Lower-prioritychore: drop translate dev dep to remove lxml exposureby odudex · 701f8efd · May 6, 2026 · 4 filesMessage 85 · StrongLow 25Details
Commit message · odudex
chore: drop translate dev dep to remove lxml exposure
Removes the translate package and its i18n auto-fill helper (print_missing/post_process_translation and the fill* CLI actions).
85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
AI analysis · Low 25/100
This commit removes a developer-only translation helper that relied on the 'translate' package, which in turn pulled in the 'lxml' XML-processing library. The stated goal is to reduce exposure to lxml, a large native-code dependency that has a history of security vulnerabilities. The change only affects development tooling and does not alter the actual Krux firmware or wallet code that end users run.
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
seed or entropy path
AI analysis · Informational 15/100
This commit removes the visual grid lines drawn on camera scans of TinySeed metal backup plates. It is a user-interface improvement to make the punched holes easier to see; it does not change security logic, cryptography, or data handling.
Lower-prioritychore: bump version to 26.04.0by odudex · 00bf26d3 · Apr 22, 2026 · 4 filesMessage 57 · ThinInformational 15Details
Commit message · odudex
chore: bump version to 26.04.0
and add .claude .gitignore
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 routine version bump from 26.03.1 to 26.04.0 across three configuration/source files, plus adding '.claude' to the .gitignore file. There are no code changes that affect security, functionality, or user behavior.
* fix: enforce minimum PBKDF2 iterations in kef.unwrap
A malicious envelope could declare iterations=0 and bypass key stretching. Reject any envelope below 10000 iterations.
* fix: reject multiple origin-less xpubs in multi-key descriptors
Previously a second origin-less key would silently overwrite the first, losing cosigner identity. Only the single taproot internal-key exception remains allowed.
* fix: filter traversal entries from SD listings in file manager
A malicious or corrupted SD card could return names like ".", ".." or entries containing path separators which, concatenated into a path, would allow escaping the current directory. Drop those entries from os.listdir results. The intended ".." up-navigation is unaffected because it is added explicitly by the page.
* fix: add in-session backoff on KEF decryption failures
Track failed KEF decrypt attempts in a RAM-only class counter and sleep with exponentially growing delay (1s, 2s, 4s, capped at 30s) before each new attempt. Reset on success. A power cycle clears the counter, an accepted trade-off to slow interactive brute forcing without writing lockout state to flash.
83/100 · StrongMessage clarity
✓ Descriptive subject✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly
Why it was queued
access controldefensive validationsigning or wallet path
AI analysis · High 74/100
This commit fixes four security weaknesses in Krux, a Bitcoin hardware-wallet project. The changes prevent: (1) encrypted backups from declaring zero or very low password-stretching effort, which would make them easy to brute-force; (2) multi-signature wallet descriptors from silently accepting multiple cosigners whose identity cannot be verified; (3) a malicious or corrupted SD card from tricking the file manager into leaving its intended folder; and (4) repeated wrong password attempts on encrypted backups by adding growing delays between attempts. All four are hardening fixes rather than a single critical vulnerability.
Lower-priorityfix: validate settings.json on load to prevent OOM and type confusion (#850)by Odudex · e2a8bf7b · Apr 7, 2026 · 3 filesMessage 97 · StrongModerate 68Details
Commit message · Odudex
fix: validate settings.json on load to prevent OOM and type confusion (#850)
Enforces a maximum file size and rejects non-object payloads when loading settings.json from SD/flash.
97/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Explains rationale or failure mode✓ Links an issue, advisory, or supporting reference
Why it was queued
defensive validation
AI analysis · Moderate 68/100
This update fixes a security hole in how Krux reads its settings file from an SD card or flash storage. Before, an attacker with physical access could put an abnormally large or oddly shaped settings.json file on the card and crash or confuse the device. Now the device refuses to load any settings.json larger than 8 KB and rejects files whose contents are not a JSON object, falling back to safe default settings instead.
Security candidatefix: add zip bomb protection and QR part limit enforcement (#843) (#848)by Odudex · bd95e828 · Apr 7, 2026 · 10 filesMessage 93 · StrongModerate 66Details
Commit message · Odudex
fix: add zip bomb protection and QR part limit enforcement (#843) (#848)
DeflateIO now enforces a 100KB max decompressed size at the C level, protecting all callers (BBQR and KEF) from zip bomb OOM on K210. pMofN parser validates part_total (1-99) and part_index range. BBQR parser validates part_total >= 1.
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
defensive validationboot or update path
AI analysis · Moderate 66/100
This commit fixes two denial-of-service weaknesses in Krux, a Bitcoin hardware-wallet firmware. First, it caps how much data can come out of compressed (deflated) QR codes and encrypted backups, preventing a maliciously crafted 'zip bomb' from exhausting the device's memory. Second, it rejects QR-code part counts that are zero or absurdly high, preventing an attacker from tricking the wallet into reserving unbounded memory while scanning multi-part QR codes.
Security candidatefix: warn user before signing raw hashes in message signing (#846)by Odudex · 23bc73b3 · Apr 6, 2026 · 26 filesMessage 93 · StrongModerate 60Details
Commit message · Odudex
fix: warn user before signing raw hashes in message signing (#846)
Add a warning screen when the input is a raw 32-byte hash or 64-char hex string, alerting the user before signing. This mitigates the risk of an attacker submitting a transaction sighash disguised as a message. Fixes C3 of #843
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
explicit security languagesigning boundarysigning or wallet path
AI analysis · Moderate 60/100
This commit adds a warning screen to Krux's message-signing feature when the user is about to sign a raw 32-byte hash or a 64-character hex string. Previously, the device would silently treat such inputs as already-hashed values and sign them directly. Because a Bitcoin transaction's signature hash (sighash) is also a 32-byte value, an attacker could trick a user into signing what looks like a harmless message but is actually a transaction hash, effectively authorizing a transaction. The fix asks the user to confirm before proceeding.
AI review queuedFix: Reject multisig policies with m=0 or m>n and guard against ZeroDivisionError in fee calculation and (#845)by Odudex · 33982945 · Apr 6, 2026 · 8 filesMessage 93 · StrongModerate 60Details
Commit message · Odudex
Fix: Reject multisig policies with m=0 or m>n and guard against ZeroDivisionError in fee calculation and (#845)
* fix: guard against ZeroDivisionError in fee calculation for zero-value outputs
* fix: validate multisig quorum m>0 and m<=n in key-value wallet files
* chore: bump version to 26.03.01
* fix: Be more specific about invalid multisig quorum errors
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
defensive validationsigning or wallet pathsecond-pass: near security thresholdsecond-pass: security-sensitive path
AI analysis · Moderate 60/100
This update fixes two security issues in Krux, a Bitcoin signing device. First, it prevents the device from crashing when calculating fees for transactions that send no regular bitcoin (only data outputs like OP_RETURN). Second, it now rejects invalid multisig wallet setups where zero signatures are required or where more signatures are required than keys exist, which could otherwise allow unauthorized or impossible spending rules.
refactor: remove unreachable code after while true (#842)
70/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
AI analysis · Informational 15/100
This commit removes a single line of Python code that could never run. The removed line sat immediately after a `while True:` loop that only exits by returning from the function, so execution could never reach it. It is a harmless cleanup with no security effect.
refactor: remove duplicated HEX and OCT digit constants (#841)
70/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
AI analysis · Informational 15/100
This commit removes two unused duplicate text strings that listed hexadecimal and octal digits from a login-related source file. There is no functional code change, no bug fix, and no security relevance visible in the diff.