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
feat(core): defs MIN_DATA_VERSION based on version
[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 19/100
This change updates how Trezor devices decide whether downloaded Ethereum token/chain definition files are too old to trust. Previously there was one global cutoff date; now each definition format version has its own cutoff. This is a maintenance and correctness improvement, not a fix for an active security bug. It reduces the chance that a future format version could accidentally accept stale or incompatible definition data.
✓ 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 · Low 31/100
This commit updates the Trezor One (legacy firmware) to use version 2 of the external Ethereum token/network definition format. The key change is that legacy firmware now requires only one valid signature instead of two, and explicitly rejects the older version 1 format. This is a feature update to align legacy devices with the newer definition format, not a fix for an active security bug. The change is documented and includes tests verifying that version 1 definitions are rejected on legacy firmware.
Security candidaterefactor(core/sec): make the boot header portable and lift it out of stm32by tychovrahe · edf70f4b · Sep 8, 2026 · 4 filesMessage 100 · StrongInformational 13Details
Commit message · tychovrahe
refactor(core/sec): make the boot header portable and lift it out of stm32
`boot_header.c` is parsing, hashing and signature verification over a caller-supplied buffer. No flash, no MPU, nothing per-MCU -- yet it sat under `image/stm32/`, so it was compiled only for the device and any host build of code that touches a boot header failed to link on the whole layer. That blocks two things: a bootloader emulator (it IS the boot chain, so it cannot emulate anything without this) and host-side test harnesses over the same structures.
Only three lines were actually non-portable, all casting a `uint32_t` flash address to a pointer. So the API takes pointers:
The callers are unaffected in substance: each already had the address of something it was about to read, and on the device a pointer into flash IS that address. `boot_ucb_read` still hands out `uint32_t` fields, because the UCB is a flash structure the boardloader parses -- an address there is data, not a pointer, and it stays that way.
`boot_ucb.c` and `boot_image.c` stay under stm32/: they touch flash.
Also in `boot_header_auth_get`, one early return was `return secfalse` in a function returning a pointer. `secfalse` is 0x00000000U so this was correct by accident; it now returns NULL. No behaviour change.
Pure refactor -- no functional change on any device. Built T3W1 boardloader/bootloader/firmware/prodtest, T3T1 boardloader and bootloader --production (spare unchanged), T2T1 to cover an MCU without the scheme, and the T3W1 firmware / T3T1 bootloader emulators.
[no changelog]
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
100/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✓ Mentions testing or verification✓ Names security-relevant behavior explicitly
Why it was queued
signing boundaryupdate trustdefensive validation
AI analysis · Informational 13/100
This commit is a code cleanup that moves a small piece of boot-header parsing code out of an STM32-specific folder so it can also be used in emulator and test builds. It changes function arguments from raw flash addresses (uint32_t numbers) to generic pointers, and fixes one accidental use of a security-boolean value where a null pointer was intended. The commit message and diff show no intended behavior change on real devices.
build(core): fix NFC feature propagation at emulator
Otherwise, <io/nfc.h> fails to be included - and emulator build breaks.
Also, remove top-level `nfc` feature, and keep it only in `upymod` crate.
[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
boot or update path
AI analysis · Informational 15/100
This is a build-system-only change that moves where the NFC feature flag is defined so the emulator compiles correctly. It does not change any runtime behavior, user-facing functionality, or security logic.
Security candidatechore(core): fix a small comment typoby Roman Zeyde · 578e011b · Sep 8, 2026 · 2 filesMessage 57 · ThinInformational 15Details
Commit message · Roman Zeyde
chore(core): fix a small comment typo
[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
boot or update path
AI analysis · Informational 15/100
This commit fixes a grammar typo in two code comments/docstrings, changing 'Receive a BLE events' to 'Receive a BLE event'. It does not change any executable code, behavior, or security properties.
✓ 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 only changes how a command-line tool prints information about secure-monitor firmware headers. In non-verbose mode it now shows the device model and version instead of dumping every header field. There is no change to security checks, cryptography, or firmware behavior.
test(clear_signing): native currency address in token formatter
[no changelog]
72/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
signing boundarysigning or wallet path
AI analysis · Informational 15/100
This commit only adds a new test case for the Trezor hardware wallet's Ethereum transaction-signing feature. It records a sample Aave 'withdraw ETH' transaction and its expected on-screen snapshots across many languages. There is no change to the actual firmware code that runs on the device, so it cannot introduce a security vulnerability or fix one.
feat(clear_signing): support native currency address in token formatter
[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
signing boundarysigning or wallet path
AI analysis · Informational 18/100
This commit adds support for passing a 'native currency address' into an Ethereum token amount formatter used for Trezor's clear-signing feature. It is a small feature addition with no obvious security bug. There is no evidence in the commit of a vulnerability, exploit, or security fix.
chore(clear_signing): support native currency addresses
[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
signing boundary
AI analysis · Informational 20/100
This commit adds a new optional data field called native_currency_address to the message format used for Trezor's Ethereum clear-signing feature. It only changes protocol definitions and generated serialization code across Python, Rust, and the core firmware. There is no actual logic that uses the new field yet, and the commit is marked as a routine chore with no changelog entry. It does not appear to fix or introduce a security vulnerability on its own.
test(clear_signing): add test fixture for external threshold message
.dat file not added so it would blind sign at the time of merge. We need to update the definitions repo for it. Will be added in a separate PR. [no changelog]
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 boundarysigning or wallet path
AI analysis · Informational 15/100
This commit only adds a new test case for the Trezor Ethereum clear-signing feature. It records an expected transaction signature and screen snapshots for an Aave 'repayWithPermit' operation. The actual human-readable definition file needed for clear-signing is intentionally not included, so the test will blind-sign until a separate update is made. There is no change to firmware code, no vulnerability, and no security fix.
feat(clear_signing): add threshold message support
[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
signing boundarysigning or wallet path
AI analysis · Informational 18/100
This commit adds a small feature to Trezor's Ethereum 'clear signing' code that lets a data format specify a custom message to show when a token amount exceeds a configured threshold. Previously the device always displayed the word 'unlimited'. There is no obvious security bug in the change itself; it is a user-interface wording feature. The commit does not fix a vulnerability.
chore(clear_signing): add threshold message support
[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
signing boundary
AI analysis · Informational 15/100
This commit adds a new optional text field called 'threshold_message' to the data structure used for Ethereum clear-signing. It only updates protocol definitions and generated code in Python, Rust, and the core firmware. There is no change to how data is validated, displayed, or processed. By itself, this commit does not introduce a security vulnerability.
Security candidatefeat(ui): assert property list is never empty.by PrisionMike · fc09afce · Sep 7, 2026 · 6 filesMessage 72 · AdequateInformational 17Details
Commit message · PrisionMike
feat(ui): assert property list is never empty.
Will not affect the production builds. [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
cryptography-sensitive path
AI analysis · Informational 17/100
This commit adds a runtime check (assert) that ensures a UI function for confirming on-screen properties is never called with an empty list. It also changes the expected input type from a generic iterable to a sequence and converts a couple of generator expressions into lists. The commit message explicitly says it will not affect production builds, because assertions are typically stripped from production firmware. There is no direct evidence this fixes an active security bug; it appears to be a defensive hardening measure for development/debug builds.
Security candidatefix(core/xtask): pad a combined image's erased regions as erasedby tychovrahe · 7d423838 · Sep 7, 2026 · 2 filesMessage 95 · StrongLow 25Details
Commit message · tychovrahe
fix(core/xtask): pad a combined image's erased regions as erased
A combined image pads the gaps between its sections with 0x00. That is wrong for any region the boot chain ERASES on first boot: the bootloader erases the UCB (`boot_ucb_erase`), so the device stops matching the image it was flashed from the moment it boots, and a factory line that verifies by reading flash back would fail.
Pad that region with 0xFF, the erased state, and the erase becomes a no-op -- it checks `flash_area_is_erased` and skips -- leaving the image byte-identical to what is on the device. The rule generalises: a region the boot chain erases has to be combined in its erased state.
The region is located from the model's memory.ld, so a model without one is untouched; both cases are covered by tests.
[no changelog]
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
update trust
AI analysis · Low 25/100
This commit fixes a build-time tooling bug in Trezor's firmware build helper. When creating a combined firmware image, the tool was filling unused gaps between sections with 0x00 bytes. One specific gap (the UCB region) is erased by the bootloader on first boot. Because erased flash reads as 0xFF, the device would no longer match the original image after its first boot, causing factory verification to fail. The fix makes the tool fill that gap with 0xFF instead, so the image stays identical after the device boots. This is a manufacturing/verification bug, not a security vulnerability that can be exploited by an attacker.
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
secret or key materialcryptography-sensitive path
AI analysis · Low 46/100
This commit turns off an internal performance cache for BIP39, the system that converts a recovery seed phrase into cryptographic keys on Trezor hardware wallets. Disabling a cache is usually a defensive change: it can prevent sensitive seed-derived data from lingering in device memory longer than necessary. However, the commit gives no explanation, changelog entry, or linked security report, so we cannot tell whether this fixes a known vulnerability or is just a precautionary hardening measure.
Security candidatefix(core/bootloader): report the actual error from a failed wipe stepby tychovrahe · 0a0d00aa · Sep 7, 2026 · 1 fileMessage 85 · StrongInformational 20Details
Commit message · tychovrahe
fix(core/bootloader): report the actual error from a failed wipe step
`send_error_conditionally` ignored its `msg` argument and always sent "Could not read BLE status", so a host watching a WipeDevice was told the wrong thing whenever anything but the BLE status read failed -- an inability to issue a BLE command, to erase bonds, or to erase flash.
[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
update trustboot or update path
AI analysis · Informational 20/100
This is a minor bug fix in the Trezor bootloader. When wiping the device, if a step failed, the bootloader always reported the same generic error message ('Could not read BLE status') even when the actual failure was something else, such as failing to erase stored data or issue a Bluetooth command. The fix makes the bootloader report the correct, specific error message. It does not change whether errors happen or how they are handled; it only corrects the message sent to the host computer.
✓ Specific, 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 12/100
This is a small internal code cleanup in the Trezor firmware's Rust UI layer. It moves some MicroPython-specific code into its own submodule and removes an unused import. There is no visible change to user-facing behavior or security-sensitive logic.
Security candidatefeat(clear signing): show signing context on all flowsby PrisionMike · da463970 · Sep 7, 2026 · 7 filesMessage 62 · AdequateInformational 17Details
Commit message · PrisionMike
feat(clear signing): show signing context on all flows
[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
signing boundarycryptography-sensitive pathsigning or wallet path
AI analysis · Informational 17/100
This commit changes how Trezor hardware wallets display Ethereum transaction details on screen during 'clear signing' flows. It adds more context—such as the contract address, account name, and derivation path—to the confirmation screens across all supported device models (Bolt, Caesar, Delizia, Eckhart). The change is purely user-interface related and does not alter transaction validation, cryptography, or how funds are moved.
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit is a minor code cleanup in a test file. It reorganizes Python import statements to follow style guidelines by importing Callable and Sequence from collections.abc instead of typing. There is no functional change and no security relevance.
test(clear_signing): benqi claim empty property list
[no changelog]
72/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
signing boundarysigning or wallet path
AI analysis · Informational 15/100
This commit only adds a new test case for the Benqi sAVAX redeem function. It includes test data, a small external definition file, and expected screen hashes for automated UI tests. There is no change to production firmware code, no bug fix, and no security patch.
test(clear_signing): benqi claim empty property list
[no changelog]
72/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
signing boundary
AI analysis · Informational 15/100
This commit only updates a single test data file used for Ethereum clear-signing tests. The title says it is adjusting a Benqi claim test case to use an empty property list. There is no code change, no firmware change, and no indication of a security fix or vulnerability.
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
signing boundarycryptography-sensitive path
AI analysis · Informational 19/100
This commit is a minor user-interface fix for Ethereum 'clear signing' flows on Trezor hardware wallets. It simply skips showing a contract-details screen when there are no details to display. There is no indication this is a security fix, and the change does not alter what users must approve before signing a transaction.
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
boot or update pathauthentication path
AI analysis · Informational 15/100
This commit removes an unused import of a string type from a Rust source file. It is a routine code cleanup with no functional change and no security relevance.
It better describes the reality as not only st-7789 controller is used inside the Trezor devices display panels.
[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 15/100
This commit is a simple rename of the display driver from 'st-7789' to 'i8080' because the code supports more than just the ST7789 display controller. It only changes file paths, feature names, and include guards. There is no change to how the code works, and no security issue is present.
✓ 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 minor user-interface improvement for a developer/debugging tool. It adds a 'verbose' mode to the text output shown when inspecting a Trezor firmware file header. In non-verbose mode it now prints a shorter summary (device model, version, fingerprint, signature/hash status) instead of dumping every header field. There is no change to security checks, cryptography, firmware loading, or device behavior.