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 queuedfix(tests): removed unused is_dynamicby PrisionMike · 2ada2691 · Nov 18, 2026 · 3 filesMessage 67 · AdequateInformational 15Details
Commit message · PrisionMike
fix(tests): removed unused is_dynamic
[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 · Informational 15/100
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 test suite with no user-facing or security impact.
Security candidatefeat(clear_signing): update proto defs for features to be supported.by PrisionMike · 84cb6a4b · Nov 18, 2026 · 9 filesMessage 62 · AdequateInformational 21Details
Commit message · PrisionMike
feat(clear_signing): update proto defs for features to be supported.
[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 21/100
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 extra formatting options, while making some older fields optional. The code changes are mostly additions to generated protocol files and a small update to the Python parser. There is no direct evidence in the commit of a security vulnerability being fixed or introduced.
✓ Descriptive subject✓ Uses a recognizable type or scope! No meaningful explanatory body
AI review queuedchore(python): fix protocol_v1 probe for bridge transportby M1nd3r · 46492ba4 · Nov 18, 2026 · 4 filesMessage 62 · AdequateInformational 19Details
Commit message · M1nd3r
chore(python): fix protocol_v1 probe for bridge transport
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
parser or protocol pathsecond-pass: security-sensitive path
AI analysis · Informational 19/100
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 accidentally disconnect the device when using Trezor Bridge (a browser-to-device communication path). The fix moves the cleanup into the transport layer and skips it entirely for Bridge transports, so connections no longer get dropped during detection.
Lower-prioritytest(python): test bridge transport survives protocol_v1 probeby M1nd3r · 0115c93d · Nov 18, 2026 · 1 fileMessage 72 · AdequateTriage 0Details
Commit message · M1nd3r
test(python): test bridge transport survives protocol_v1 probe
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
Lower-prioritychore(core): update fixturesby Michal Kazda · 037db60a · Nov 18, 2026 · 1 fileMessage 47 · ThinTriage 0Details
Commit message · Michal Kazda
chore(core): update fixtures
[no changelog]
47/100 · ThinMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope! No meaningful explanatory body
Lower-prioritychore(core): add generated filesby Michal Kazda · e3de805e · Nov 18, 2026 · 2 filesMessage 57 · ThinTriage 0Details
Commit message · Michal Kazda
chore(core): add generated files
[no changelog]
57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Lower-priorityfix(core): moved period from code to stringby Michal Kazda · 367c1ef2 · Nov 18, 2026 · 2 filesMessage 57 · ThinTriage 0Details
Commit message · Michal Kazda
fix(core): moved period from code to string
[no changelog]
57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Lower-priorityfix(core): with_colon instead of hardcoded string concatenationby Michal Kazda · 1764151f · Nov 18, 2026 · 1 fileMessage 62 · AdequateTriage 0Details
Commit message · Michal Kazda
fix(core): with_colon instead of hardcoded string concatenation
[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
Lower-priorityfix(core): add periods to share templatesby Michal Kazda · 08c7aade · Nov 18, 2026 · 1 fileMessage 57 · ThinTriage 0Details
Commit message · Michal Kazda
fix(core): add periods to share templates
[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
translation-only discount
Lower-prioritychore(core): update fixturesby Michal Kazda · 6f4d3ec5 · Nov 18, 2026 · 1 fileMessage 47 · ThinTriage 0Details
Commit message · Michal Kazda
chore(core): update fixtures
[no changelog]
47/100 · ThinMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope! No meaningful explanatory body
AI review queuedfeat(core): show language name in change confirmby Michal Kazda · 5ff5cba0 · Nov 18, 2026 · 7 filesMessage 80 · StrongInformational 15Details
Commit message · Michal Kazda
feat(core): show language name in change confirm
- Replace the language code (e.g. "cs-CZ") in the "Change language to ...?" prompt with a translatable language name. - Add language__<name> strings for all supported languages; unknown languages fall back to the raw code.
[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
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
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'. It also adds the corresponding translated names for all supported languages. There is no security-relevant change.
AI review queuedfix(translations): fix failing tests in ES and FRby Michal Kazda · 9a12ab12 · Nov 18, 2026 · 3 filesMessage 67 · AdequateInformational 15Details
Commit message · Michal Kazda
fix(translations): fix failing tests in ES and FR [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 pathtranslation-only discountsecond-pass: security-sensitive path
AI analysis · Informational 15/100
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' and shortening some backup-related phrases). There is no indication of any security-relevant code change.
Lower-priorityrefactor(core): relocate model crate sourcesby cepetr · b46182e2 · Nov 18, 2026 · 7 filesMessage 57 · ThinTriage 0Details
Commit message · cepetr
refactor(core): relocate model crate sources
[no changelog]
57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
chore(crypto): hardening against potential side-channel leakage
Two issues - Using `volatile cond` twice in a single `assert`, i.e. `assert(cond == 0 | cond == 1)` results in two conditional branches (potentially distinguishable). - Memory access is (potentially) dependent on the secret exponent. This is not an expoitable issue, as Trezor does not utilize a memory cache.
Solution - Using `cond` only once in the `assert` (`assert(cond <= 1)`), which is compiled into a single branch. - Using `point_select` makes the memory access independent of the secret exponent.
Note that all `assert`s in the C code are compiled into production core firmware, so the first issue DOES affect the production code.
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
defensive validationcryptography-sensitive path
AI analysis · Low 47/100
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 two, reducing the chance that timing or power analysis could reveal whether the value was 0 or 1. Second, it replaces direct table lookups that depended on a secret scalar with a constant-time selection helper that always reads every table entry. The commit message explicitly says the memory-access issue is not exploitable on Trezor because the device has no cache, but the assert issue does affect production firmware because asserts are compiled in.
Lower-priorityfix(storage): fix burst scheduling in flash area writesby tychovrahe · 3cbf2ce2 · Nov 16, 2026 · 1 fileMessage 85 · StrongTriage 0Details
Commit message · tychovrahe
fix(storage): fix burst scheduling in flash area writes
- the burst condition compared the area offset with the bytes left to write, so bursts stopped halfway and never ran past the first region
[no changelog]
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Security candidatefeat(ci, clear_signing): add clear signing device tests as a nightly run.by PrisionMike · fea125ba · Nov 15, 2026 · 17 filesMessage 72 · AdequateInformational 15Details
Commit message · PrisionMike
feat(ci, clear_signing): add clear signing device tests as a nightly run.
[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 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 reporting improvements. There is no indication this commit fixes or introduces a security vulnerability.
Lower-prioritydocs(core): document all prodtest variant valuesby tychovrahe · d71c14dd · Nov 13, 2026 · 1 fileMessage 80 · StrongTriage 0Details
Commit message · tychovrahe
docs(core): document all prodtest variant values
- list battery_type and manufacturing_lock_present in otp-variant-write
[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
documentation-only discount
Lower-prioritychore(core): don't show progress bar when unsetting translationsby Roman Zeyde · 0d7ea84e · Nov 13, 2026 · 2 filesMessage 77 · AdequateTriage 0Details
Commit message · Roman Zeyde
chore(core): don't show progress bar when unsetting translations
The animation happen after the erasure is over, so it doesn't improve the UX.
[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
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Security candidatechore(core): move `keccak_32` to unittestsby Roman Zeyde · f3225451 · Nov 12, 2026 · 2 filesMessage 57 · ThinInformational 15Details
Commit message · Roman Zeyde
chore(core): move `keccak_32` to unittests
[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 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 the device handles user data, no bug fix, and no security-related behavior change.
Security candidatechore: remove SmartCashby Roman Zeyde · b6d65c00 · Nov 12, 2026 · 16 filesMessage 63 · AdequateInformational 15Details
Commit message · Roman Zeyde
chore: remove SmartCash
- drop SmartCash (SMART, tSMART) coin definitions and support entries - remove secp256k1-smart curve from crypto, core coininfo and cointool
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
63/100 · AdequateMessage clarity
✓ Subject identifies a change✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
cryptography-sensitive pathboot or update path
AI analysis · Informational 15/100
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 fixed here; it is simply cleanup of an unused or unsupported coin.
Security candidatechore(common,core,legacy,crypto): remove Groestlcoinby Roman Zeyde · e22d597d · Nov 12, 2026 · 45 filesMessage 77 · AdequateInformational 15Details
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
cryptography-sensitive pathsigning or wallet pathboot or update path
AI analysis · Informational 15/100
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 vulnerability here—this is a feature-removal cleanup.
✓ Descriptive subject✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
signing or wallet pathboot or update path
AI analysis · Informational 15/100
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 it addresses any security issue.