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
refactor(core): move haptic driver bindings to io crate
[no 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
boot or update path
AI analysis · Informational 15/100
This commit is a straightforward internal code reorganization: it moves the Rust bindings for the device's vibration motor (haptic feedback) from one internal crate to another. There is no change to security-sensitive logic, no bug fix, and no externally visible behavior change. It is purely a refactor.
AI review queuedchore(core/caesar): prepare stringsby obrusvit · 05ea6072 · Oct 19, 2026 · 14 filesMessage 72 · AdequateInformational 15Details
Commit message · obrusvit
chore(core/caesar): prepare strings
- this commit prepares strings for new menu navigation in Caesar layout (T2B1, T3B1)
[no changelog]
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 or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit only updates text strings and translation files for the on-device tutorial on Trezor's two-button 'Caesar' layout devices (T2B1, T3B1). It adds new tutorial labels, rewords existing instructions, adjusts which layouts may use certain strings, and refreshes the translation signature and UI test snapshots. There is no code that handles secrets, cryptography, memory, network, or user confirmation logic, so it does not introduce a security vulnerability.
Security candidatechore(python): fixup `noqa:` comment following Ruff nitby Roman Zeyde · 72489948 · Oct 19, 2026 · 1 fileMessage 85 · StrongInformational 15Details
Commit message · Roman Zeyde
chore(python): fixup `noqa:` comment following Ruff nit
``` warning: Invalid `# noqa` directive on src/trezorlib/qt/pinmatrix.py:36: expected a comma-separated list of codes (e.g., `# noqa: F401, F841`). warning: Invalid `# noqa` directive on src/trezorlib/qt/pinmatrix.py:37: expected a comma-separated list of codes (e.g., `# noqa: F401, F841`). ```
[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
Why it was queued
authentication path
AI analysis · Informational 15/100
This is a trivial Python linting cleanup. It changes two `# noqa: I` comments to `# noqa: I900` so that the Ruff linter accepts them. No code behavior is altered, and there is no security relevance.
Security candidatefix(core/caesar): show SHIFT label by defaultby obrusvit · 53400258 · Oct 19, 2026 · 2 filesMessage 80 · StrongInformational 15Details
Commit message · obrusvit
fix(core/caesar): show SHIFT label by default
- show the SHIFT label by default in all screens when the shift functionality is activated - previously, this was only in the tutorial
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 is a small user-interface cleanup for the Trezor hardware wallet's 'Caesar' layout. It makes the on-screen 'SHIFT' label appear by default whenever the Shift button feature is active, instead of only showing it in the tutorial. The change removes a special override that the tutorial used and applies the same label everywhere. There is no security issue here.
Security candidatefeat(core/caesar): new tutorialby obrusvit · 6c6bd120 · Oct 19, 2026 · 9 filesMessage 72 · AdequateInformational 15Details
Commit message · obrusvit
feat(core/caesar): new tutorial
- new tutorial implementation teaching the new menu and SHIFT-to-scroll up navigation
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 routine user-interface feature: it adds a new on-device tutorial for the Trezor hardware wallet's 'Caesar' layout. It teaches users how to navigate menus, scroll, use the middle button, and the 'Shift' button combination. There is no security fix or vulnerability present in the change.
AI review queuedfix(core/emulator): fix crash in micropython built with --asanby cepetr · 44c5a701 · Oct 19, 2026 · 4 filesMessage 62 · AdequateInformational 16Details
Commit message · cepetr
fix(core/emulator): fix crash in micropython built with --asan
[no 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
second-pass: broader security terminology
AI analysis · Informational 16/100
This commit fixes a crash that happened only when running the Trezor firmware emulator with AddressSanitizer (ASAN), a debugging tool used during development. The crash occurred because ASAN's stack-use-after-return detection interfered with MicroPython's internal stack check, causing a false RuntimeError on startup. The fix disables that specific ASAN feature for emulator builds and also turns off leak detection because the firmware does not use the heap. This change only affects developer/debug builds and does not change the security behavior of real Trezor devices.
Security candidatefeat(core/caesar): show scrollbar in menuby obrusvit · 90294f2a · Oct 17, 2026 · 5 filesMessage 57 · ThinInformational 15Details
Commit message · obrusvit
feat(core/caesar): show scrollbar in menu
- both FW and BLD menu
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 polish change for the Trezor hardware wallet's 'Caesar' layout. It adds a small page counter (like '1/3') and a scrollbar-style indicator to on-device menus in both the bootloader and firmware. There is no security-relevant change; it only affects what is drawn on screen.
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
Why it was queued
update trustcryptography-sensitive pathboot or update path
AI analysis · Informational 12/100
This commit reorganizes the on-screen button and menu code used by the Trezor bootloader on small-screen devices (T2B1/T3B1). It creates bootloader-specific copies of user-interface components instead of sharing them with the main firmware, and removes unused button layout helpers. The stated goal is to reduce flash memory use and make the bootloader UI independent from firmware UI changes. There is no indication in the commit that this fixes a security bug or changes security-critical behavior.
AI review queuedfix(core/embed): accept zero-length TLV item at the end of optiga metadataby Ondřej Vejpustek · d8ae06db · Oct 16, 2026 · 1 fileMessage 85 · StrongLow 42Details
Commit message · Ondřej Vejpustek
fix(core/embed): accept zero-length TLV item at the end of optiga metadata
`optiga_parse_metadata()` rejected a zero-length item in final position while accepting it anywhere else. Relax the bounds check accordingly.
[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
Why it was queued
second-pass: broader security terminology
AI analysis · Low 42/100
This is a small bug fix in the Trezor hardware wallet firmware. It changes a bounds check so that a zero-length data item at the very end of a metadata block is accepted, just like zero-length items already are elsewhere in the block. Without the fix, a valid but empty trailing item would be rejected as malformed. This could cause communication problems with the Optiga security chip, but the change itself is a straightforward correction of an overly strict check.
get_glyph() narrowed chars with `as u16`, so a code point above U+FFFF was drawn with the glyph of the BMP char sharing its low 16 bits (e.g. U+10041 as 'A'). Two different strings could thus render identically while signing different bytes. Draw such chars with the nonprintable glyph instead.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> (cherry picked from commit f0d78f8fe65b1eac885a048b3173af1deb3a86b8)
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
signing boundary
AI analysis · High 74/100
This commit fixes a display bug in Trezor hardware wallets where special Unicode characters above U+FFFF (so-called supplementary plane characters) were incorrectly drawn as completely different, ordinary characters. For example, a rare character U+10041 could appear on screen as the letter 'A'. Because the device signs the original bytes but the user sees a misleading string, an attacker could craft a transaction or message that looks legitimate to the user while actually signing something different. The fix now shows a non-printable placeholder for such characters instead of the wrong glyph.
Security candidatefeat(core/caesar): new menu nav in bootloaderby obrusvit · 07d2c3d6 · Oct 16, 2026 · 14 filesMessage 57 · ThinInformational 15Details
Commit message · obrusvit
feat(core/caesar): new menu nav in bootloader
[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
update trustcryptography-sensitive pathboot or update path
AI analysis · Informational 15/100
This commit is a routine user-interface redesign for the bootloader on certain Trezor hardware wallets. It changes how buttons are labeled and how users navigate confirmation menus (for example, moving the fingerprint info screen into a context menu and requiring both buttons for factory reset). There is no indication of a security bug being fixed or introduced.
AI review queuedchore(python): remove deprecated `details` argument from `btc.sign_tx()`by Roman Zeyde · 95accc10 · Oct 16, 2026 · 2 filesMessage 77 · AdequateInformational 20Details
Commit message · Roman Zeyde
chore(python): remove deprecated `details` argument from `btc.sign_tx()`
It was deprecated in 3d6d1a56ac595866b0d826445caeb429bac13a26.
77/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 20/100
This is a routine cleanup in Trezor's Python library. It removes an old, already-deprecated way of passing extra transaction signing options (the `details` argument) from the `btc.sign_tx()` helper. Users who still relied on that old argument will now get a normal Python error instead of a deprecation warning, but the change does not fix or introduce any security vulnerability.
Security candidatebuild(core): suppress LOAD segment with RWX permissions warningby Martin Milata · b769435c · Oct 15, 2026 · 1 fileMessage 62 · AdequateInformational 11Details
Commit message · Martin Milata
build(core): suppress LOAD segment with RWX permissions warning
[no 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
credential or privilege state
AI analysis · Informational 11/100
This commit changes the build settings for the Trezor firmware's Rust code to silence a linker warning about memory segments that are marked as readable, writable, and executable (RWX). The commit message states that these segment permissions are not actually used to configure the device's Memory Protection Unit (MPU), so the warning is not a real security concern. It does not fix a vulnerability, but it does hide a warning that could otherwise alert developers to a potentially risky memory layout.
Security candidatefeat(core): add base58 to the crypto crateby Lukas Bielesch · 80b2fc30 · Oct 14, 2026 · 2 filesMessage 57 · ThinInformational 15Details
Commit message · Lukas Bielesch
feat(core): add base58 to the crypto crate
[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
cryptography-sensitive path
AI analysis · Informational 15/100
This commit adds a brand-new Base58 encoding/decoding helper library in Rust for the Trezor firmware. It is purely additive code with no callers yet, and it includes tests. There is no indication it fixes or introduces a security vulnerability.
AI review queuedrefactor(core/embed): extract optiga metadata serialization into optiga_metadata.cby Ondřej Vejpustek · fd2dd466 · Oct 13, 2026 · 3 filesMessage 85 · StrongInformational 15Details
Commit message · Ondřej Vejpustek
refactor(core/embed): extract optiga metadata serialization into optiga_metadata.c
The metadata parsing functions and the `OPTIGA_META_*` constants are pure in-memory TLV serialization with no dependency on the transport or the chip state. Move them into a file of their own.
[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
Why it was queued
second-pass: broader security terminology
AI analysis · Informational 15/100
This commit is a simple code cleanup: it moves existing metadata parsing and serialization functions from one source file to another without changing their behavior. There is no security fix or vulnerability introduced.
AI review queuedfix(xbuild): keep a separate .d file per outputby tychovrahe · c8fc50cf · Oct 12, 2026 · 1 fileMessage 80 · StrongInformational 17Details
Commit message · tychovrahe
fix(xbuild): keep a separate .d file per output
The compiler's dependency file was named by replacing the output's extension, so the object and the preprocessed (qstr collection) output of the same C source shared one .d file. The collection pass runs with NO_QSTR and never includes the generated qstr header, so its .d overwrote the object's and an incremental build no longer saw that header change: after adding a qstr, py/qstr.o was not rebuilt and every later qstr index was off by one. Append .d to the output name instead.
[no changelog]
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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: broader security terminology
AI analysis · Informational 17/100
This is a build-system bug fix, not a security vulnerability. The change fixes how dependency files are named during compilation so that incremental builds correctly detect when generated header files change. Previously, two build stages could overwrite each other's dependency tracking files, causing stale object files and incorrect internal string indexes in the MicroPython runtime. There is no direct exploit path from this commit.
Security candidatefix(core): make the GFXMMU frame buffers writable by the T3W1 applicationby tychovrahe · bcc7f4d5 · Oct 12, 2026 · 13 filesMessage 97 · StrongLow 36Details
Commit message · tychovrahe
fix(core): make the GFXMMU frame buffers writable by the T3W1 application
On T3W1 every pixel the application wrote to the frame buffer with the CPU was silently lost; only DMA2D transfers reached it. The anti-aliased edges of rounded rectangles and circles, and the blur, were missing on hardware, which the dark theme hid.
The GFXMMU stayed privileged-only. Its privilege attribute lives in the GTZC TZSC, and the secure monitor locks the TZSC configuration (LCK, until reset) at the end of its init, so the non-secure kernel's attempt in display_set_unpriv_access() to make it unprivileged was refused. An unprivileged access to a privileged resource is a silent fail (RM0456 5.4.2): reads return zero, writes are ignored, no event is raised, so no fault ever pointed at it.
Configure the frame buffer access in tz_init() instead, on every layout: the secure monitor before it locks the TZSC, the secure kernel of the non-secmon layouts at its start. Unprivilege the physical frame buffers first, so that the GFXMMU's own bus transactions (the LTDC refresh; a securable peripheral that is a bus master issues transactions with its TZSC privilege, RM0456 3.6.3) stay legal, then the GFXMMU. The MPU keeps gating which buffer the application may touch. The regions come from the model's memory layout, so display_set_unpriv_access() and its driver implementations go away. tz_set_sram_unpriv() gets the same secure/ non-secure alias handling as tz_set_sram_unsecure() so the monitor can name the buffers by their non-secure addresses.
Move the TZSC privilege setters (SAES, TAMP, GFXMMU) out of the shared sys/trustzone module into sec/trustzone (sec/tz_periph.h), available to secure builds only, so a non-secure build that calls one fails to compile instead of failing silently at runtime. They now also refuse to run once the TZSC is locked, and the SAES and TAMP ones are not built into the secure monitor, which has no caller for them. Gate the secure AES unprivileged path, their other caller, on secure mode the same way; it is only reachable from secure-only code anyway.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
[no changelog]
97/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Explains rationale or failure mode
Why it was queued
credential or privilege statecryptography-sensitive path
AI analysis · Low 36/100
This commit fixes a display bug on the Trezor T3W1 hardware where the application could not directly write to the screen's frame buffer. Because of a TrustZone security-controller misconfiguration, CPU-drawn pixels were silently ignored, so only graphics copied by the DMA engine showed up. The patch moves the privilege setup to the correct early initialization stage and removes a broken runtime path that could not work once the controller was locked. It also hardens the code so future mistakes cause compile-time or runtime failures instead of silent no-ops.
Security candidatefeat(core/caesar): make more nav consistentby obrusvit · 042523a0 · Oct 10, 2026 · 5 filesMessage 57 · ThinInformational 15Details
Commit message · obrusvit
feat(core/caesar): make more nav consistent
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 cleanup for the Trezor hardware wallet's 'Caesar' layout. It removes unused button styles, unifies how on-screen menus and pagination work, and moves some confirmation screens from Rust into Python so they behave consistently with other models. There is no indication of a security bug or fix.
Security candidatefix(core/caesar): reset button state on attachby obrusvit · e4087c48 · Oct 10, 2026 · 2 filesMessage 57 · ThinLow 49Details
Commit message · obrusvit
fix(core/caesar): reset button state on attach
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 path
AI analysis · Low 49/100
This commit fixes two UI state-reset bugs in the Trezor hardware wallet's 'Caesar' layout. When a screen layout is restarted (an 'Attach' event), the code now forgets any button presses that happened while the layout was inactive and clears a stuck 'Shift' key state. Without the fix, a previously pressed button or held Shift could be incorrectly remembered when returning to a screen, potentially causing an unintended action or confusing the user interface. The commit itself does not describe this as a security fix, and no independent researcher is credited.
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.
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.
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.