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
- Assign hid both the assigned account and the new owner when they equal the signer, so a self-assignment showed no instruction screen at all and could be appended to an otherwise visible transfer.
- The owner is a program ID, not an authority. Assigning a wallet to its own non-executable address permanently locks its lamports: only the current owner program can debit lamports or change the owner. - https://solana.com/docs/core/accounts#key-facts - https://github.com/anza-xyz/agave/blob/8acf2b352b9768b2b96f283400d8b9393c6c6e40/transaction-context/src/instruction_accounts.rs#L91-L103
- Always show both fields for consistency with "Assign With Seed".
(cherry picked from commit 2894b1ec7a20e51614eaa79881a39f37a0b33c75)
100/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Links an issue, advisory, or supporting reference
Why it was queued
signing boundarysigning or wallet path
AI analysis · High 75/100
This fix prevents a Trezor hardware wallet from silently approving a specific Solana 'Assign' instruction. Previously, when a user assigned their own account as the new owner program, both key details were hidden from the device screen, so the instruction produced no visible prompt at all. An attacker could tack this silent self-assignment onto an otherwise normal-looking transfer, tricking the user into signing a transaction that permanently locks their Solana account's funds. The patch now always displays both the account being assigned and the new owner program.
- use Layout rendering machinery to split text into two lines instead of using split_two_lines function - the reason is that a very long (german) word cannot be split by a space so we need to break using a hyphen
[no changelog]
80/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
refactor(clear_signing): renamed variables for code comprehension
[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 15/100
This commit is a simple code cleanup: it renames the variable `address_bytes` to `contract_address` and `f` to `display_format` in one Ethereum clear-signing file to make the code easier to read. No behavior changes, no security fixes, and no bug fixes are visible in the diff.
✓ Descriptive subject✓ Uses a recognizable type or scope! No meaningful explanatory body
Security candidatefix(core): add new line on Eckhart address mismatch screenby Michal Kazda · 99cb0ffd · Sep 25, 2026 · 1 fileMessage 77 · AdequateInformational 15Details
Commit message · Michal Kazda
fix(core): add new line on Eckhart address mismatch screen - ensures addr_mismatch__support_url starts on a new 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
Why it was queued
boot or update path
AI analysis · Informational 15/100
This commit is a cosmetic UI fix for the Trezor hardware wallet's Eckhart layout. It adds a line break so that a support URL appears on its own line when the device shows an address mismatch warning. There is no security-relevant change to how addresses are validated, compared, or displayed to the user.
Security candidatefix(core): use buttons__cancel in Delizia menu to cancel PIN setupby Michal Kazda · 7a1b8121 · Sep 25, 2026 · 1 fileMessage 85 · StrongInformational 18Details
Commit message · Michal Kazda
fix(core): use buttons__cancel in Delizia menu to cancel PIN setup - copies cancelling wipe code setup - fixes trouble with some long translations of pin__cancel_setup which cannot fit into the menu item [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
access control
AI analysis · Informational 18/100
This is a tiny user-interface wording fix in the Trezor hardware wallet firmware. It changes the label on one menu button from a long translated phrase ('cancel setup') to a shorter generic word ('Cancel') so that translations fit on screen. There is no direct evidence this is a security vulnerability; it is a UI polish fix that may slightly reduce user confusion when setting up a PIN.
Will be used for testing multisig/Miniscript end-to-end test vectors.
[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
Why it was queued
signing boundaryfuzzing or regression evidence
AI analysis · Informational 15/100
This commit only adds a new Python test dependency called 'embit' version 0.8.0 to the project's dependency files. It is explicitly marked as being for testing PSBT (Partially Signed Bitcoin Transaction) parsing and end-to-end test vectors. There is no code change, no vulnerability fix, and no indication of a security issue.
Security candidatebuild(crypto): update `crypto/Makefile` to use `-std=gnu11`by Roman Zeyde · fafc7d72 · Sep 25, 2026 · 1 fileMessage 85 · StrongInformational 15Details
Commit message · Roman Zeyde
build(crypto): update `crypto/Makefile` to use `-std=gnu11`
`std=gnu99` is no longer used elsewhere in our codebase.
It will allow us to use `max_align_t` in the next commit.
[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
cryptography-sensitive path
AI analysis · Informational 15/100
This commit simply changes the C language standard version used to compile the crypto library from GNU C99 to GNU C11. It is a routine build-system update with no security-relevant code change and no functional impact on its own.
From `secp256k1_context_preallocated_create()` documentation: ``` * The caller must provide a pointer to a rewritable contiguous block of memory * of size at least secp256k1_context_preallocated_size(flags) bytes, suitably * aligned to hold an object of any type. ```
✓ 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
cryptography-sensitive path
AI analysis · Low 46/100
This commit fixes how a memory buffer used by the secp256k1 cryptographic library is aligned in memory. The library requires the buffer to be aligned for any data type, but the previous code used a plain byte array, which could be misaligned on some platforms or compilers. Misalignment can cause crashes or, in rare cases, subtle cryptographic failures. The fix explicitly aligns the buffer to the strictest alignment the C compiler supports.
- chnages in Eckhart mainly and a little bit in Delizia
[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
boot or update path
AI analysis · Informational 16/100
This commit changes how Trezor hardware wallets display the sign/verify message flow on two newer user-interface designs (Eckhart and Delizia). It mostly reorganizes on-screen menus so that extra details (account, derivation path, message size) are grouped under a single 'More info' item, and it makes the cancel/mismatch warning screen consistent with other flows. There is no direct evidence in the commit that this fixes a security vulnerability; it reads as a UI consistency and usability cleanup.
✓ 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 routine internal refactoring of how debug logging is implemented in the Trezor firmware's Rust code. It introduces a new lightweight logging system based on the ufmt library and adds build options to control the maximum log level. There is no indication this change fixes a security vulnerability or introduces a new security risk.
refactor(core/rust): move log crate connector to sys
[no changelog]
62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
boot or update path
AI analysis · Informational 15/100
This commit is a straightforward internal code reorganization (refactor) for how debug logging is wired up in the Trezor firmware's Rust code. It moves a logging connector from one internal module to another and adds a build-time feature flag to enable it. There is no indication this fixes or introduces a security vulnerability.
Lower-priorityfix(translations): update help text for source-only option in mergeby Michal Kazda · 6c38a6ab · Sep 24, 2026 · 1 fileMessage 77 · AdequateTriage 0Details
Commit message · Michal Kazda
fix(translations): update help text for source-only option in merge
[no changelog]
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
77/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
(cherry picked from commit 674f2304b4c7838de465f474436e8f7b23e449d4)
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
Lower-prioritychore(core): adjusted how crowdin.py merge option deals with Englishby Michal Kazda · fd2d831b · Sep 24, 2026 · 1 fileMessage 85 · StrongTriage 0Details
Commit message · Michal Kazda
chore(core): adjusted how crowdin.py merge option deals with English - by default merge now skips English layout files and does not touch en.json - new --source-only flag merges only English layout files (used after blanking rules are applied) [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
✓ 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 pathtranslation-only discountsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit is a routine synchronization of translated user-interface text strings from the Crowdin translation platform into the Trezor firmware. It only changes wording, grammar, and layout labels in multiple language files (Czech, German, Spanish, French, Indonesian, Portuguese) and updates their cryptographic signatures. There is no change to firmware logic, cryptography, transaction handling, or security behavior.
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
boot or update path
AI analysis · Informational 15/100
This commit is a straightforward internal code cleanup in the Trezor firmware's user-interface layer. It replaces a small helper struct called ShowInfoParams with a direct function call (show_info_screen) that builds the same on-screen information pages. There is no change to security behavior, no bug fix, and no externally visible feature change.
Lower-prioritytest(core/delizia): visit more info screen pagesby obrusvit · 7c85d27f · Sep 24, 2026 · 1 fileMessage 67 · AdequateTriage 0Details
Commit message · obrusvit
test(core/delizia): visit more info screen pages
[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
- shrink `ShowInfoParams` struct to a bare minimum - the main `confirm_summary` screen now uses bare `Frame` constructed with paragraphs
[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
boot or update path
AI analysis · Informational 12/100
This commit is a routine internal code cleanup (refactor) for the Trezor firmware's user interface. It replaces a custom-built information screen with a shared 'MoreInfoScreen' component and simplifies a settings structure. There is no indication in the commit that it fixes a security bug or changes security behavior.
Lower-priorityfix(core/delizia): use monospace for fee rateby obrusvit · a9fc93c8 · Sep 24, 2026 · 1 fileMessage 80 · StrongTriage 0Details
Commit message · obrusvit
fix(core/delizia): use monospace for fee rate
- not setting this `is_data` flag would cause incorrect fee rate format (not monospaced) after implementing the new MoreInfoScreen
[no changelog]
80/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context