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
(cherry picked from commit 2f9edf3e118fe09f551184cb2d2a782a77b5c16f)
82/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Mentions testing or verification
✓ Descriptive subject✓ Uses a recognizable type or scope✓ Mentions testing or verification! No meaningful explanatory body
AI review queuedfix(cardano): ask detail level for script data hashby Jakub Janků · e3554c4a · Sep 23, 2026 · 3 filesMessage 85 · StrongModerate 60Details
Commit message · Jakub Janků
fix(cardano): ask detail level for script data hash
The script data hash is signed but was hidden in simple transactions, which skip the level of details prompt.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> (cherry picked from commit 5d70dc3b7358706f3125fb469457c2a4864bf36f)
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
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Moderate 60/100
This update fixes a display issue in Trezor's Cardano signing flow. When a user signs a simple-looking Cardano transaction that secretly includes a 'script data hash,' the device now asks the user to confirm details instead of hiding that hash. The script data hash is still signed, but previously it could be shown without the user being prompted at the right detail level, which could make it easier for a malicious app or website to trick the user into approving something they did not fully understand.
Lower-prioritychore(core): drop unused `bitcoin__unknown_transaction` stringby Roman Zeyde · 0e4f3191 · Sep 23, 2026 · 4 filesMessage 77 · AdequateTriage 0Details
Commit message · Roman Zeyde
chore(core): drop unused `bitcoin__unknown_transaction` string
It was previously used by Omni parser.
[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
Security candidatechore: drop Omni support from Core and Legacy firmwareby Roman Zeyde · 47dc2058 · Sep 23, 2026 · 14 filesMessage 93 · StrongInformational 19Details
Commit message · Roman Zeyde
chore: drop Omni support from Core and Legacy firmware
OP_RETURN data will be confirmed using `confirm_blob()` flow.
USDT is no longer supported on Omni: https://tether.io/news/tether-provides-update-on-transition-plan-for-legacy-blockchains/
93/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathboot or update path
AI analysis · Informational 19/100
This commit removes support for the old Omni Layer protocol from Trezor hardware wallets. Omni was used for assets like USDT (Tether) on Bitcoin before those tokens moved to other blockchains. After this change, any transaction that previously showed a friendly 'Simple send of X USDT' message will instead be shown as raw 'OP_RETURN' data. This is a deliberate feature removal, not a security fix, and it does not introduce a vulnerability.
- added a production and staging Swapkit key to debug FW
[no changelog]
72/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
AI review queuedfix(cardano): ask detail level for datum outputsby Jakub Janků · ddd608cf · Sep 23, 2026 · 10 filesMessage 80 · StrongModerate 60Details
Commit message · Jakub Janků
fix(cardano): ask detail level for datum outputs
Simple transactions skip the level of details prompt, which also hid output datums and reference scripts although they are signed.
- ask for the level of details when the first output carrying Plutus data is encountered - add show-details fixtures for such simple transactions
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> (cherry picked from commit 801cf7033f96951eb17ab4c72ebfe94eac8ec6ee)
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 · Moderate 60/100
This update fixes a user-interface bug in Trezor's Cardano transaction signing. For simple-looking Cardano transactions, the device was skipping the 'show details' prompt. Because of that, the user never saw important output data—specifically inline datums and reference scripts—even though those data are part of what the device signs. A malicious or buggy wallet app could have hidden those details from the user while still getting the device to sign them. The fix makes the device ask whether to show details as soon as it encounters an output containing Plutus data, so the user can review and decide.
Lower-priorityfix(translations): split English strings at byte offsetsby Jakub Janků · 888eb81d · Sep 23, 2026 · 1 fileMessage 77 · AdequateTriage 0Details
Commit message · Jakub Janků
fix(translations): split English strings at byte offsets
Slice the UTF-8 bytes before decoding, so strings with multi-byte chars (e.g. NBSP) stay one per line.
[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
- SELL payment requests are now supported in production.
[no changelog]
82/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Mentions testing or verification
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Lower-priorityfix(core): allow NBSP in English strings ASCII testby Michal Kazda · 4778a4e7 · Sep 22, 2026 · 1 fileMessage 72 · AdequateTriage 0Details
Commit message · Michal Kazda
fix(core): allow NBSP in English strings ASCII test [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
translation-only discount
Security candidatechore(core): improvements to English copyby Michal Kazda · 1dbc2c3c · Sep 22, 2026 · 2 filesMessage 57 · ThinInformational 15Details
Commit message · Michal Kazda
chore(core): improvements to English copy [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 pathboot or update path
AI analysis · Informational 15/100
This commit is a routine text cleanup for the Trezor hardware wallet's on-screen English messages. It fixes punctuation, removes unnecessary line breaks, and makes small wording tweaks (for example, changing 'PIN will be required' to 'A PIN will be required'). There is no change to security logic, cryptography, or how the device protects funds.
Lower-priorityfix(core/prodtest): fix signed comparison errorby Martin Milata · bd2a538e · Sep 22, 2026 · 1 fileMessage 57 · ThinTriage 0Details
Commit message · Martin Milata
fix(core/prodtest): fix signed comparison error
[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(core/embed): add missing memzero to modtrezorcrypto
[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
cryptography-sensitive path
AI analysis · Low 44/100
This commit adds secure cleanup (memzero) and fixes memory allocation ordering in Trezor's cryptocurrency module. It ensures that sensitive key material, such as BIP-32 and Cardano secrets, is wiped from memory even when an error occurs during key derivation. Without these changes, secret data could remain in memory longer than intended after a failure, increasing the risk of exposure if an attacker could read device memory. The commit is a defensive hardening fix and does not appear to be a complete exploit by itself.
Lower-prioritybuild(core): deny `unused_imports` in trezor_libby Roman Zeyde · 61f7a5f0 · Sep 22, 2026 · 1 fileMessage 57 · ThinTriage 0Details
Commit message · Roman Zeyde
build(core): deny `unused_imports` in trezor_lib
[no changelog]
57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
refactor(clear_signing): improve types - add FormattedValue type
improved naming and readability [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 boundarysigning or wallet path
AI analysis · Informational 15/100
This is a pure code cleanup (refactoring) change in the Ethereum 'clear signing' feature of the Trezor firmware. It renames a type alias, introduces a new helper type alias to make function signatures shorter, removes an unused list initialization, and makes a private helper function public. No behavior of the device or how transactions are shown to the user is changed.
Security candidatefix(clear_signing): threshold value should use non-strict inequalityby PrisionMike · 1875af5e · Sep 21, 2026 · 1 fileMessage 93 · StrongLow 38Details
Commit message · PrisionMike
fix(clear_signing): threshold value should use non-strict inequality
- Long discussed fix in the spec wordings. - To be fixed formally here: https://github.com/ethereum/ERCs/pull/2017 - Practically this was always the case but was fixed with data instead of logic.
[no changelog]
93/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
signing boundarysigning or wallet path
AI analysis · Low 38/100
This commit fixes a tiny but meaningful off-by-one error in how Trezor displays Ethereum transaction amounts. Previously, an amount exactly equal to a 'threshold' value was shown as a normal number; now it is shown as a special 'above threshold' or 'unlimited' warning. The change makes the device behavior match the intended specification, reducing the chance that a user approves a transaction they mistake for small when it is actually at the danger threshold.
Lower-prioritychore(core): added rules for strings already used by subset of layoutsby Michal Kazda · 4178d500 · Sep 21, 2026 · 1 fileMessage 62 · AdequateTriage 0Details
Commit message · Michal Kazda
chore(core): added rules for strings already used by subset of layouts [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
translation-only discount
Lower-prioritychore(core): added and applied new blanking rulesby Michal Kazda · f8db4e90 · Sep 21, 2026 · 3 filesMessage 57 · ThinTriage 0Details
Commit message · Michal Kazda
chore(core): added and applied new blanking rules [no changelog]
57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body