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.
AI review queuedrefactor(ethereum): use DisplayFormat to parse yieldingby Ioan Bizău · 6daa3bd6 · May 7, 2026 · 2 filesMessage 62 · AdequateInformational 12Details
Commit message · Ioan Bizău
refactor(ethereum): use DisplayFormat to parse yielding
[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 or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 12/100
This commit is a code cleanup in Trezor's Ethereum transaction handling. It replaces a hand-rolled method of reading Ethereum vault transaction data with a shared, more structured parsing system called DisplayFormat. There is no indication this fixes a security bug; it appears to be a refactoring change with no functional security relevance stated by the vendor.
AI review queuedrefactor(nordic): migrate away from pm_static towards DTS fixed-partitionsby tychovrahe · 7e3eb453 · May 6, 2026 · 8 filesMessage 62 · AdequateInformational 17Details
Commit message · tychovrahe
refactor(nordic): migrate away from pm_static towards DTS fixed-partitions
[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 or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 17/100
This is a build-system refactor for Trezor's Nordic Bluetooth chip firmware. It removes manually maintained flash partition files and switches to Zephyr's standard device-tree partition definitions. The change also fixes a build-time signing script bug where a duplicate image header could be inserted, which would cause the device to crash immediately on boot. There is no direct evidence this is a security vulnerability patch, but it prevents a real boot failure in the manufacturing/development workflow.
AI review queuedrefactor(nordic): dts cleanup and DK gpio driver removalby tychovrahe · a9470c60 · May 6, 2026 · 8 filesMessage 62 · AdequateInformational 15Details
Commit message · tychovrahe
refactor(nordic): dts cleanup and DK gpio driver removal
[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 or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit is a routine cleanup of the Nordic board configuration and Bluetooth Low Energy firmware for a Trezor hardware wallet. It removes the generic Nordic 'DK buttons and LEDs' driver and replaces it with direct GPIO (general-purpose input/output) definitions tied to the actual Trezor board pins. It also fixes a typo in the board name and renames some device-tree labels for clarity. There is no security-relevant change visible in the diff.
AI review queuedrefactor(nordic): make build_sign_flash.sh script take constants from DTS and config filesby tychovrahe · fa2dc6b7 · May 6, 2026 · 1 fileMessage 62 · AdequateInformational 15Details
Commit message · tychovrahe
refactor(nordic): make build_sign_flash.sh script take constants from DTS and config files
[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 or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit refactors a build script for Nordic hardware so that several hard-coded numbers (memory addresses, slot size, device model tag) are instead read from the project's generated device tree and configuration files. There is no change to runtime code, no new user-facing behavior, and no indication of a security fix or vulnerability.
AI review queuedfix(core): prevent NFC driver crash on repeated deinitializationby tychovrahe · c856ba57 · May 5, 2026 · 1 fileMessage 62 · AdequateLow 32Details
Commit message · tychovrahe
fix(core): prevent NFC driver crash on repeated deinitialization
[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 · Low 32/100
This commit fixes a bug in the Trezor hardware wallet's NFC driver where calling the NFC shutdown function more than once could crash the device. The fix adds a simple check to skip re-deinitializing the SPI hardware if it has already been shut down. It is a defensive hardening fix rather than a clear exploitable vulnerability.
AI review queuedchore(ethereum): check array data lengthby Ioan Bizău · bbb17455 · May 5, 2026 · 1 fileMessage 57 · ThinLow 49Details
Commit message · Ioan Bizău
chore(ethereum): check array data length
[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
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 49/100
This commit adds a length check to a function that parses arrays of 256-bit unsigned integers in Ethereum transaction data. Previously, if the raw data was not a multiple of 32 bytes, the function would silently ignore leftover bytes at the end. The fix now raises an error instead. This could matter for 'clear signing' displays on a Trezor hardware wallet, where malformed data might otherwise be shown or processed in a misleading way. The commit message does not describe this as a security fix, and no exploit is demonstrated.
AI review queuedchore(ethereum): precomputed approve/transfer sigby Ioan Bizău · 424bc94e · May 5, 2026 · 1 fileMessage 57 · ThinInformational 19Details
Commit message · Ioan Bizău
chore(ethereum): precomputed approve/transfer sig
[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
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 19/100
This commit replaces runtime computation of two Ethereum function signatures with hard-coded byte values, then adds debug-only assertions to verify those values still match the original computation. It is a minor code cleanup with no apparent security impact. The change does not alter what the device signs, displays, or accepts.
AI review queuedchore(ethereum): check data lengthby Ioan Bizău · e64bfd98 · May 5, 2026 · 1 fileMessage 57 · ThinLow 47Details
Commit message · Ioan Bizău
chore(ethereum): check data length
[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
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 47/100
This commit adds a safety check to a function that verifies unused data is zeroed. Before the change, if a caller passed an invalid 'used_bytes' value (for example, a negative number or one larger than 32), the function could read memory outside the intended 32-byte window or behave unexpectedly. The patch now rejects such invalid values immediately. The commit message calls it a routine cleanup ('chore') and does not claim it fixes a security vulnerability.
AI review queuedchore(ethereum): enforce context-based parser typeby Ioan Bizău · 39ce7ae7 · May 5, 2026 · 1 fileMessage 77 · AdequateLow 46Details
Commit message · Ioan Bizău
chore(ethereum): enforce context-based parser type
Only allow dynamic types to be parsed in a Dynamic context and non-Dynamic in an Atomic context.
[no changelog]
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 · Low 46/100
This commit tightens validation in Trezor's Ethereum 'clear signing' feature. It now rejects cases where a host computer tells the device to parse a variable-length type (like a string or byte blob) as if it were a fixed 32-byte value, or vice versa. This reduces the chance that a malicious or buggy host could trick the device into misreading transaction data, but the commit itself does not claim to fix a specific known attack.
AI review queuedchore(ethereum): replace load-bearing assertsby Ioan Bizău · aabaf3f5 · May 5, 2026 · 1 fileMessage 57 · ThinLow 46Details
Commit message · Ioan Bizău
chore(ethereum): replace load-bearing asserts
[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
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 46/100
This commit replaces several 'assert' checks in the Ethereum 'clear signing' code with proper error handling. In production firmware, asserts can be stripped out or behave differently than expected, so replacing them with explicit error raises makes the code more robust against malformed or malicious transaction data. The change is defensive hardening rather than a clear fix for an active exploit.
AI review queuedrefactor(ethereum): extract functionby Ioan Bizău · f5aa9d87 · May 5, 2026 · 1 fileMessage 47 · ThinInformational 15Details
Commit message · Ioan Bizău
refactor(ethereum): extract function
[no changelog]
47/100 · ThinMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit is a simple code cleanup in the Ethereum clear-signing module. It pulls out a repeated snippet of code that reads variable-length data into a new helper function, then replaces two copies of that snippet with calls to the helper. No behavior changes are visible in the diff.
AI review queuedfeat(ethereum): support ContainerPath.Toby Ioan Bizău · 98badcea · May 5, 2026 · 7 filesMessage 57 · ThinLow 27Details
Commit message · Ioan Bizău
feat(ethereum): support ContainerPath.To
[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
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 27/100
This commit adds support for a new 'To' container path in Trezor's Ethereum clear-signing feature. It lets the device reference the transaction recipient when formatting token amounts, which is useful for displaying ERC-20 transfers and approvals correctly. The change is a feature addition, not a clear security fix, and there is no evidence of a disclosed vulnerability.
AI review queuedfeat(tests,ethereum): definition requestby Ioan Bizău · 20e95c6b · May 5, 2026 · 6 filesMessage 67 · AdequateLow 28Details
Commit message · Ioan Bizău
feat(tests,ethereum): definition request
[no changelog]
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
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 28/100
This commit adds a new feature to Trezor's Ethereum signing flow: the device can now ask the host computer mid-transaction for extra token or display-format definitions. The main production code change is small and appears to fix a token-resolution bug in clear signing by preferring a token returned from the parsed field data over the one looked up from the static definitions. Most of the diff is new and updated test code exercising the new request/response mechanism and renaming helpers from 'erc7730' to the more generic 'display format'.
AI review queuedchore(ethereum): payment request just for transfersby Ioan Bizău · d8d009e9 · May 5, 2026 · 1 fileMessage 77 · AdequateModerate 58Details
Commit message · Ioan Bizău
chore(ethereum): payment request just for transfers
The only ERC-20 call allowed in payment requests should be `transfer`.
[no changelog]
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 · Moderate 58/100
This commit tightens a security rule in Trezor's Ethereum signing code: payment requests can now only be used with plain ERC-20 token transfers. Previously, the code may have allowed payment requests with other smart-contract calls, which could let a malicious app or service trick a user into approving a different transaction than expected while still showing a familiar payment-request screen.
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 14/100
This commit only adds three new user-facing text strings for an existing hardware feature called N4W1 (likely a near-field communication tag workflow). It adds error messages for empty, non-empty, and damaged tags, plus updates translation indexes and a signature file. There is no code logic change, no bug fix, and no security-relevant behavior.
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit only adds new user-facing text strings for a wallet backup feature called 'N4W1' (for example, prompts asking the user what kind of backup they want and a 'Reading tag...' message). It updates translation files, generated Rust translation code, and a mock file used for testing. There is no executable logic change, no bug fix, and no security-related change.
AI review queuedchore(ethereum): add more parsersby Ioan Bizău · c63bb2c1 · Apr 28, 2026 · 1 fileMessage 57 · ThinInformational 12Details
Commit message · Ioan Bizău
chore(ethereum): add more parsers
[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
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 12/100
This commit is a routine code cleanup for the Ethereum app in Trezor firmware. It replaces several hand-written number-parsing functions with a single factory that generates them automatically, and moves the address parser earlier in the file. There is no indication this fixes a security bug or introduces a vulnerability.
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit is a simple code cleanup in Trezor's Ethereum transaction signing. It extracts a repeated chunk of code that confirms transaction data and shows a summary into a shared helper function, then uses that helper in both legacy and EIP-1559 transaction signing paths. There is no security bug being fixed here.
AI review queuedchore(ethereum): rename Struct to Tupleby Ioan Bizău · dee0663a · Apr 28, 2026 · 3 filesMessage 72 · AdequateInformational 15Details
Commit message · Ioan Bizău
chore(ethereum): rename Struct to Tuple
They are the same thing, but we are actually referring the fields by index.
[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 is a simple rename from 'Struct' to 'Tuple' in the Ethereum clear-signing code. It changes only variable, class, and type alias names to better reflect that the code accesses fields by index. No behavior, logic, or security properties are changed.
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit removes two unused symbolic labels, TO and CHAIN_ID, from an internal Ethereum clear-signing data-format definition. It is a cleanup change with no functional code logic altered and no security relevance.
AI review queuedrefactor(core): move `ButtonRequest`-related code into `ButtonRequestHandler`by Roman Zeyde · 9d49d901 · Apr 28, 2026 · 2 filesMessage 77 · AdequateInformational 11Details
Commit message · Roman Zeyde
refactor(core): move `ButtonRequest`-related code into `ButtonRequestHandler`
Also, minimize context-related access in `ui.Layout`.
[no changelog]
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
parser or protocol pathsecond-pass: security-sensitive path
AI analysis · Informational 11/100
This commit is a code cleanup (refactor) that moves ButtonRequest handling logic out of the UI layout class and into a dedicated ButtonRequestHandler class. It does not appear to change security behavior; it reorganizes existing logic to make the code easier to maintain. There is no indication this fixes or introduces a security vulnerability.
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit is a routine translation update for the French language. It changes the capitalization of one word ('fragment' to 'Fragment') and removes the word 'n°' (number) from two French text strings shown on the device during SLIP39 backup/recovery flows. The accompanying files are just updated translation signatures and UI test fixture hashes. There is no code logic change and no security relevance.
✓ 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 pathtranslation-only discountsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit is a routine synchronization of translated user-interface text strings for the Trezor hardware wallet firmware. It updates wording in Czech, German, Spanish, French, Portuguese, and the translation signature file. There are no code, logic, cryptographic, or security behavior changes.
AI review queuedchore(translations): sync second batch of Crowdin translations [no changelog]by Michal Kazda · 1f6513c7 · Apr 28, 2026 · 7 filesMessage 77 · AdequateInformational 15Details
Commit message · Michal Kazda
chore(translations): sync second batch of Crowdin translations [no changelog]
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 15/100
This commit is a routine synchronization of translated user-interface text for the Trezor hardware wallet. It updates Czech, German, Spanish, French, and Portuguese translation files, refreshes the cryptographic signature that protects those translations, and updates the expected screen hashes used by automated UI tests. There is no change to security logic, cryptography, or how the device handles private keys or transactions.
AI review queuedfix(l10n): various en strings improvements [no changelog]by Michal Kazda · 7c014e24 · Apr 27, 2026 · 12 filesMessage 77 · AdequateInformational 15Details
Commit message · Michal Kazda
fix(l10n): various en strings improvements [no changelog]
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 15/100
This commit is a routine language and translation update for the Trezor hardware wallet firmware. It changes English wording (for example, 'Input data' becomes 'Data', 'Access passphrase wallet' becomes 'Access Passphrase wallet'), removes some trailing colons from prompts, and updates the generated translation tables and test fixtures accordingly. There is no code behavior change, no security fix, and no vulnerability.