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 is a routine GitHub Actions workflow fix. It changes which Slack webhook secret is used for nightly test failure notifications and removes a now-unnecessary safety check. There is no security vulnerability in the change itself.
This commit only improves a test report for Trezor's clear-signing feature. It changes how skipped test cases are listed in a nightly summary, showing each skipped case's source file and calldata size instead of just counting them by reaso…
This commit only changes test scripts and documentation for the Trezor firmware clear-signing test suite. It makes the tests run more registry cases—specifically those where the developer definitions do not yet have a display format—so the…
This commit updates French and Portuguese translation strings in the Trezor firmware and refreshes the translation signature metadata. The changes are purely wording adjustments (for example, replacing abbreviations like 'nº' with the full…
This commit changes a code-coverage tracking map inside the Trezor firmware from a claimed capacity of 1,048,576 entries down to 65,536 entries. The commit message says the old capacity was never truly that large because the heapless libra…
No cryptographic or secret-handling code changedNo input parsing, deserialization, or memory allocator changesChange is in a debug/test instrumentation module (coverage)
This commit is a routine update of translated user-interface text strings for the Trezor hardware wallet. It adds new translations (for example, warnings about exporting public keys and Solana blind-signing prompts), updates existing wordi…
This commit only adds new test cases for Ethereum clear-signing array parsing. It does not change any production code, so it cannot introduce a new security vulnerability on its own. The tests verify that malformed arrays (out-of-bounds of…
test-only changeno production code modifiedadds defensive test coverage for ABI decoding edge cases
This commit hardens the Trezor firmware's task scheduler against fault-injection attacks. These attacks use physical techniques like voltage glitches or laser pulses to trick the device into executing code with higher privileges than inten…
Fault-injection hardening (FIH) explicitly mentioned in commit title and code commentsPrivilege-level transition split into multiple guarded stepsAdded runtime invariant check that only the kernel task may run privileged
This commit only removes an unused parameter called `is_dynamic` from test helper functions and from test data in three test files. It does not change any production firmware code, wallet behavior, or security logic. It is a cleanup of the…
This commit updates the data-format definitions used by Trezor devices for Ethereum 'clear signing' (showing human-readable details of smart-contract interactions). It adds support for more numeric types, new path-step structures, and extr…
Schema expansion increases attack surface for future clear-signing parser logic, but no new parser logic is present in this commit.Replacement of NotImplementedError with InvalidFormatDefinition is a defensive change that turns unimplemented paths into a handled error rather than a crash/DoS vector.New optional fields and deprecated old fields (is_dynamic, lookup_address) are backward-compatible changes.
This is a bug-fix patch in the Python Trezor client library. It changes how the software probes whether a connected device uses the older protocol v1. Previously, the probe tried to read and throw away leftover data, but that read could ac…
No security-relevant signal in commit message or diffFix is described as a connectivity/functional bug, not a vulnerabilityNo mention of CVE, researcher credit, or security advisory
This commit is a user-interface improvement, not a security fix. It changes the language-change confirmation prompt on Trezor devices so that it shows a human-readable language name (for example, 'French') instead of a raw code like 'fr-FR…
This commit updates Spanish and French translation strings in the Trezor firmware and refreshes the translation signature file. The changes are purely textual wording adjustments (for example, changing 'Mostrar palab.' to 'Mostrar palabras…
This commit hardens cryptographic code in Trezor firmware against two potential side-channel leaks. First, it simplifies how a secret condition value is checked inside an assert statement so the compiler produces only one branch instead of…
Side-channel hardening in constant-time cryptographic primitivesReplacement of double-evaluation volatile assert with single-branch assertElimination of secret-dependent memory access in elliptic-curve scalar multiplication
This commit adds a new nightly automated testing workflow for Ethereum 'clear signing' on Trezor hardware wallets. It does not change any wallet firmware code that users run; it only adds test scripts, CI configuration, documentation, and …
This commit is a routine code cleanup. It removes a small helper function called keccak_32 from a shared crypto utility file and places an equivalent helper directly inside the only test file that still uses it. There is no change to how t…
This commit removes support for a cryptocurrency called SmartCash from Trezor hardware wallets. It deletes coin definitions, support entries, and a custom cryptographic curve used only by SmartCash. There is no security vulnerability being…
No security-relevant signals detectedPure feature removal / code cleanup
This commit removes all support for the Groestlcoin cryptocurrency from Trezor firmware. It deletes coin definitions, the custom Groestl hash algorithm code, related address/transaction handling, and tests. There is no security vulnerabili…
No security-relevant change: pure feature removalNo new attack surface introducedNo vulnerability patched or created
This commit removes all support for the Tezos cryptocurrency from Trezor firmware, software libraries, and documentation. It is a feature-removal change, not a security fix or vulnerability patch. There is no indication in the commit that …
This update reduces the longest allowed screen-lock timeout on older Trezor devices from about 6 days down to 149 hours (just over 6 days). It makes the legacy firmware behave the same as newer Trezor firmware and prevents users from setti…
Bounds enforcement added for a configurable security-relevant timeoutAlignment of security policy between legacy and core firmware variantsTest coverage added for boundary values above and below new maximum
Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.
Security candidatefix(core/caesar): ctx menu with extra infoby obrusvit · fbb130b2 · Oct 10, 2026 · 6 filesMessage 72 · AdequateLow 28Details
Commit message · obrusvit
fix(core/caesar): ctx menu with extra info
- use menu in various flows, especially ETH
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
cryptography-sensitive pathsigning or wallet pathboot or update path
AI analysis · Low 28/100
This commit fixes UI navigation behavior on Trezor Safe 3 and related Caesar-layout devices when confirming cryptocurrency transactions. Previously, pressing the shifted-right button on certain confirmation screens could cancel the signing flow instead of going back to the previous screen, and some screens lacked a proper cancel option in the menu. The patch makes navigation consistent so users can move back and forth between recipient/amount/summary screens and cancel safely from the menu, reducing the chance of accidental transaction confirmation or cancellation.
Security candidaterefactor(solana): fold write_tx into build_txby Jakub Janků · 02662d75 · Oct 10, 2026 · 1 fileMessage 95 · StrongInformational 15Details
Commit message · Jakub Janků
refactor(solana): fold write_tx into build_tx
The unit test helper write_tx had no other caller than build_tx, which repeated its whole signature just to forward the arguments.
[no changelog]
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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 boundarysigning or wallet path
AI analysis · Informational 15/100
This is a minor code cleanup in a test file. A helper function used only by one test function was folded into that function. There is no change to production firmware or to what the test actually checks.
Lower-priorityfix(core): re-send an nRF update chunk whose response does not arriveby tychovrahe · fa736f4b · Oct 9, 2026 · 1 fileMessage 85 · StrongTriage 0Details
Commit message · tychovrahe
fix(core): re-send an nRF update chunk whose response does not arrive
An SMP image upload chunk occasionally gets no response from MCUboot (nothing received, no UART errors, no nRF reset), and the whole upload then fails. Re-send the chunk up to three times before giving up; this is safe whether the request or the response was lost, as MCUboot answers a repeated chunk with its current offset.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
[no changelog]
85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Lower-priorityfix(core): compare task pointers in PendSVby cepetr · 703b2424 · Oct 9, 2026 · 1 fileMessage 57 · ThinTriage 0Details
Commit message · cepetr
fix(core): compare task pointers in PendSV
[no changelog]
57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Security candidatefix(core/caesar): ctx menu in sign msgby obrusvit · 9651bc9a · Oct 9, 2026 · 4 filesMessage 57 · ThinInformational 15Details
Commit message · obrusvit
fix(core/caesar): ctx menu in sign msg
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
cryptography-sensitive pathsigning or wallet path
AI analysis · Informational 15/100
This commit is a user-interface improvement for Trezor hardware wallets with Caesar-style screens. It adds an information menu (account, derivation path, message size) during message signing/verification and refactors the navigation flow. There is no security vulnerability being fixed; it is a usability enhancement.
Lower-priorityfix(tests): fix a Caesar click testby obrusvit · a58bcfa9 · Oct 8, 2026 · 1 fileMessage 67 · AdequateTriage 0Details
Commit message · obrusvit
fix(tests): fix a Caesar click test
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
Security candidatefeat(core/caesar): rm scrollbar in ShareWordsby obrusvit · 9674815b · Oct 8, 2026 · 1 fileMessage 80 · StrongInformational 15Details
Commit message · obrusvit
feat(core/caesar): rm scrollbar in ShareWords
- from now on, we will only use numeric scrollbar, the "bubbly" one was removed - numeric scrollbar is confusing in ShareWords Component
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
cryptography-sensitive path
AI analysis · Informational 15/100
This commit removes a visual scrollbar from the screen that displays recovery/share words on Trezor devices with the Caesar layout. It is purely a user-interface cleanup: the bubbly scrollbar was dropped in favor of a numeric page indicator, and the numeric indicator was deemed confusing in this particular screen, so it was removed entirely. There is no security-relevant change.
- this commit removes "bubbly" scrollbar and replaces it with numeric one
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
cryptography-sensitive pathboot or update path
AI analysis · Informational 15/100
This commit is a user-interface cleanup: it removes the old dotted 'bubble' scrollbar and makes the numeric 'page X of Y' counter the only style used on Trezor Safe 5 (Caesar layout). It does not change security logic, cryptography, or how user data is handled.
Security candidatefeat(core/caesar): use new menu in prompt_backupby obrusvit · 2a5772e3 · Oct 8, 2026 · 4 filesMessage 57 · ThinInformational 15Details
Commit message · obrusvit
feat(core/caesar): use new menu in prompt_backup
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
cryptography-sensitive pathboot or update path
AI analysis · Informational 15/100
This commit is a user-interface refactor for the Trezor hardware wallet's backup prompt. It replaces a two-page flow with a scrollable frame and moves the 'skip backup' action into a context menu. There is no security vulnerability visible in the diff; it is a normal feature/UX change.
Security candidatefeat(core/caesar): use new menu navigationby obrusvit · daf0c327 · Oct 8, 2026 · 19 filesMessage 57 · ThinInformational 15Details
Commit message · obrusvit
feat(core/caesar): use new menu navigation
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
cryptography-sensitive pathsigning or wallet pathboot or update path
AI analysis · Informational 15/100
This commit is a user-interface refactor for Trezor's Caesar layout (used on certain hardware models). It replaces an older 'info button' navigation pattern with a new context-menu system: the left button opens a menu, holding it enables a 'Shift' mode to scroll back, and the right button scrolls down or confirms when held. The change is purely about how screens are navigated and how extra information is shown; it does not introduce or fix any cryptographic, firmware-flashing, or memory-safety vulnerability.
Security candidatedocs: document fix_version usageby Andrew Kozlik · b34ecf34 · Oct 8, 2026 · 1 fileMessage 47 · ThinInformational 15Details
Commit message · Andrew Kozlik
docs: document fix_version usage
[no changelog]
47/100 · ThinMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
boot or update pathdocumentation-only discount
AI analysis · Informational 15/100
This commit only updates a documentation file (docs/misc/update-wipes.md). It explains when the firmware's 'fix_version' value should be increased, including one scenario involving security vulnerabilities. There are no code changes, no bug fixes, and no new functionality. It is purely a documentation clarification.
Security candidatefeat(core/caesar): implement new menu navigationby obrusvit · 2a222034 · Oct 8, 2026 · 15 filesMessage 72 · AdequateInformational 19Details
Commit message · obrusvit
feat(core/caesar): implement new menu navigation
- use the new system in BTC GetAddress flow
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
cryptography-sensitive pathboot or update path
AI analysis · Informational 19/100
This commit refactors the on-screen menu and button navigation for the Trezor hardware wallet's 'Caesar' layout. It introduces a new 'Shift' gesture (hold left button, then press right) and moves address details into a context menu. There is no direct evidence in the commit of a security vulnerability; it appears to be a user-interface redesign with corresponding test updates. However, any change to button-handling state machines on a security device warrants careful review because mistakes could, in theory, allow unintended confirmations or menu bypasses.
Lower-priorityfeat(core): check for heap allocation leaksby Roman Zeyde · 8c0afec1 · Oct 8, 2026 · 1 fileMessage 80 · StrongTriage 0Details
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
AI review queuedchore(core): sign translationsby Jakub Janků · c2167166 · Oct 8, 2026 · 1 fileMessage 62 · AdequateInformational 15Details
Commit message · Jakub Janků
chore(core): sign translations
[no changelog]
(cherry picked from commit e72a9283f723ef58f3b8644a97d76b961fd14fa4)
62/100 · AdequateMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope✓ Provides an explanatory body
Why it was queued
signing or wallet pathtranslation-only discountsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit simply adds a new cryptographic signature entry to a JSON file that records approved translation bundles for the Trezor hardware wallet. There is no code change, no bug fix, and no indication of a security issue. It appears to be routine release housekeeping.
AI review queuedfeat(core/rust): improve panic UX in case Rust heap allocation failsby Roman Zeyde · 1c3e0305 · Oct 8, 2026 · 1 fileMessage 89 · StrongInformational 23Details
Commit message · Roman Zeyde
feat(core/rust): improve panic UX in case Rust heap allocation fails
Otherwise, we'll get an internal panic from Rust stdlib.
[no changelog]
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
Why it was queued
second-pass: broader security terminology
AI analysis · Informational 23/100
This commit changes how a Trezor hardware wallet's Rust code reacts when it runs out of memory. Previously, a failed memory allocation returned a null pointer, which could later trigger a confusing internal panic from the Rust standard library. Now, the device immediately reports a clear 'Allocation failed' fatal error instead. The change is framed as a user-experience improvement, not as fixing a security vulnerability, and it does not make attacks easier.
Security candidatefix(core): support change outputs ADA payment_reqby obrusvit · 8d6394dc · Oct 8, 2026 · 7 filesMessage 72 · AdequateLow 37Details
Commit message · obrusvit
fix(core): support change outputs ADA payment_req
- only ORDINARY_SIGNER is supported for payment requests
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
signing boundarysigning or wallet path
AI analysis · Low 37/100
This update changes how Trezor handles Cardano (ADA) payment requests when a transaction includes both a recipient payment and a change output returning funds to the user's own wallet. Previously, any transaction with more than one output was rejected when a payment request was used, which prevented normal 'send payment and get change back' transactions. The fix allows one change output plus one recipient output, while still blocking risky cases such as multiple recipients, tokens on the recipient output, Plutus scripts, or payment requests in non-ordinary signing modes. It is a feature expansion with added safety checks, not a clear-cut security bug fix, but it touches code that protects users from signing unintended payments.
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
cryptography-sensitive pathsigning or wallet path
AI analysis · Informational 15/100
This commit is a routine cleanup and update of on-device icon images for the Trezor hardware wallet's user interface. It removes a couple of unused icons and adds new ones for menu graphics. There is no code behavior change, no fix for a flaw, and no security-relevant content visible in the diff.
Switch the T3T2 devkit to the LX200B4501CTP03A/B module (GC9307C controller, 240x320, FT6x36 touch) on the i8080 FMC bus.
Display panel: - Add the lx200b4501ctp03 panel (init sequence, rotation via MADCTL) and the display_panel_lx200b4501ctp03 feature (240x320). - The module has no TE output, so framebuffer copies start immediately.
Runtime pixel byte order: - The GC9307 cannot switch the RGB565 byte order and always expects the high byte first. Replace the compile-time assumption with display_pixel_endian_t stored in the driver; set_little_endian() and set_big_endian() now return the byte order actually in effect. - ISSUE_PIXEL_DATA() takes the byte order; it only matters on the 8-bit bus, as the 16-bit bus writes a whole pixel per cycle. - Pixel loops keep a local copy of the byte order, since the display write pointer could alias the driver struct and force a reload after every pixel write.
Framebuffer copy: - Add bg_copy_start_const_out_16() (GPDMA, halfword writes, optional byte exchange). - 16-bit bus: copy the framebuffer with 16-bit DMA writes. - 8-bit bus, big-endian panel: 16-bit DMA writes with byte exchange; the FMC splits each halfword into two byte cycles (lower address first), so the high byte goes out first. Little-endian panels keep the 8-bit copy.
Board (T3T2 devkit): - Drive the IM0-IM2 interface-mode pins from optional DISPLAY_IMx_* board defines; IM0 selects the 8-bit or 16-bit bus. - Display power enable (DISPL_PWR_EN) is active low on this board. - Add the touch reset pin. - Default to the 16-bit bus; the 8-bit bus is selectable in devkit.h.
Touch: - Add the touch_panel_lx200b4501ctp03 feature with a coordinate correction. Its constants are placeholders copied from LX154A2422CPT23 and still need to be verified on hardware.
[no changelog]
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
second-pass: unusually broad change
AI analysis · Informational 18/100
This commit adds support for a new LCD touchscreen module used on the T3T2 hardware development kit. It is a routine hardware-enablement change: new display initialization commands, a new DMA copy path for 16-bit or byte-swapped pixel transfers, runtime tracking of pixel byte order, and placeholder touch calibration. There is no indication in the commit that this fixes a security vulnerability or introduces a known dangerous pattern. The most notable code-quality observation is that the new touch-panel correction function currently uses unverified placeholder constants copied from another panel, which could make touch coordinates inaccurate on the devkit until hardware calibration is performed.
AI review queuedbuild(core): rename build-xtask/ to build/by Martin Milata · c1dacf2f · Oct 7, 2026 · 20 filesMessage 57 · ThinInformational 15Details
Commit message · Martin Milata
build(core): rename build-xtask/ to build/
[no 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
second-pass: unusually broad change
AI analysis · Informational 15/100
This commit is a simple rename of the build output directory from `core/build-xtask/` to `core/build/` across build scripts, CI workflows, documentation, and test helpers. It does not change any firmware code, cryptographic logic, or security behavior. It is purely a build-system maintenance change.