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
✓ 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✓ Names security-relevant behavior explicitly
Why it was queued
access control
AI analysis · Informational 23/100
This commit improves error messages in the Trezor Python command-line library when a user tries to run device authentication on hardware models that do not support it, or when the installed library version lacks the needed root certificates for a model. It does not change cryptographic behavior; it only fails earlier with clearer messages instead of potentially confusing downstream failures.
Security candidateci(core): tweak MemBrowse workflowsby Martin Milata · f62fe43e · Nov 6, 2026 · 4 filesMessage 72 · AdequateInformational 21Details
Commit message · Martin Milata
ci(core): tweak MemBrowse workflows
- Pin actions to commit hashes. - Don't run on forks.
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
access controldocumentation-only discount
AI analysis · Informational 21/100
This commit hardens Trezor's GitHub CI workflows that run a third-party memory-analysis tool called MemBrowse. It pins the MemBrowse action to a specific commit hash instead of a moving version tag, prevents the workflows from running on forked repositories, adds a job timeout, and fixes a minor condition placement. These are defensive supply-chain and hardening improvements, not a fix for an active vulnerability in the firmware itself.
- this commit introduces a configuration TOML for font generator - the new config allows incorporating manual modifications to font data
[no changelog]
70/100 · AdequateMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Security candidateci(core): tighten permissionsby Martin Milata · df815315 · Nov 6, 2026 · 1 fileMessage 47 · ThinLow 39Details
Commit message · Martin Milata
ci(core): tighten permissions
47/100 · ThinMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
credential or privilege statedocumentation-only discount
AI analysis · Low 39/100
This commit tightens the GitHub Actions workflow permissions for the Trezor firmware repository. Previously, the entire workflow had broad permissions: it could write OIDC tokens, read repository contents, and write pull-request comments. Now those permissions are removed from the top level and granted only to the specific jobs that actually need them. This is a defensive hardening change that reduces the damage if a malicious or compromised step were abused, but it does not by itself fix an active vulnerability.
Lower-prioritydocs(tools): add secmon to bump-version.py helpby obrusvit · 9d4f7db2 · Nov 6, 2026 · 1 fileMessage 57 · ThinTriage 0Details
Commit message · obrusvit
docs(tools): add secmon to bump-version.py help
[no changelog]
57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
✓ Subject identifies a change✓ Uses a recognizable type or scope✓ Provides an explanatory body
Why it was queued
signing or wallet pathboot or update path
AI analysis · Informational 15/100
This commit only updates version numbers and translation metadata across Trezor firmware files. There are no code changes, no bug fixes, and no security-related modifications visible in the diff.
Security candidatefix(core): lower maximum auto-lock delay to 149 hoursby Ondřej Vejpustek · 7cc12064 · Nov 6, 2026 · 7 filesMessage 97 · StrongLow 41Details
Commit message · Ondřej Vejpustek
fix(core): lower maximum auto-lock delay to 149 hours
Setting the auto-lock delay to the maximum crashed the firmware on every boot. The old maximum of `0x2000_0000` ms is exactly half the MicroPython tick period on 32-bit MCUs, which is the smallest delta that `utime.ticks_add()` rejects with `OverflowError`.
A device that already stores the old maximum recovers after the update, because `get_autolock_delay_ms()` clamps the stored value. The stored value itself is not rewritten.
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
memory safety
AI analysis · Low 41/100
This update fixes a bug in Trezor hardware wallets where setting the screen auto-lock delay to its maximum value caused the device to crash every time it restarted. The old maximum was chosen so that it hit a limit inside the device's timekeeping code, triggering an overflow error. The fix lowers the maximum allowed auto-lock delay to 149 hours and adds a safety check so the device cannot accept a value that would cause the crash. A device already stuck with the old maximum will recover after updating because the firmware clamps the stored value down to a safe range.
AI review queuedchore(core): sign translationsby obrusvit · b5c724df · Nov 6, 2026 · 1 fileMessage 62 · AdequateInformational 11Details
Commit message · obrusvit
chore(core): sign translations
[no changelog]
(cherry picked from commit d60a0e0e0686b3bc2d543a0135527af574b3ff8a)
62/100 · AdequateMessage clarity
✓ Descriptive subject✓ 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 11/100
This commit simply adds a new cryptographic signature entry to a JSON file that records approved translation bundles for the Trezor hardware wallet. There is no code change, no bug fix, and no apparent security issue. It looks like a routine administrative step to authorize a new set of translated strings.
Lower-priorityrefactor(core): simplify `DataCache`-related type annotationby Roman Zeyde · 3f79d53d · Nov 6, 2026 · 2 filesMessage 85 · StrongTriage 0Details
Commit message · Roman Zeyde
refactor(core): simplify `DataCache`-related type annotation
- make the return value type more specific (not need for `T`). - remove unneeded `noqa: F811` annotations.
[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
cryptography-sensitive pathboot or update path
AI analysis · Informational 15/100
This commit is a code cleanup that standardizes the names used for page-number debugging output across different parts of the Trezor user interface. It does not change any user-visible behavior, security logic, or device functionality. There is no security issue here.
Lower-priorityci: wait for Tropic model to startby Martin Milata · 8ef55098 · Nov 5, 2026 · 1 fileMessage 57 · ThinTriage 0Details
Commit message · Martin Milata
ci: wait for Tropic model to start
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
documentation-only discount
Lower-priorityci: disregard submodules in flake.nixby Martin Milata · 6dad5f4f · Nov 5, 2026 · 1 fileMessage 80 · StrongTriage 0Details
Commit message · Martin Milata
ci: disregard submodules in flake.nix
Improves `nix develop` startup speed and disk usage. Breaks uv2nix and building firmware inside nix sandbox, neither of which we currently do. If we ever roll this back we need to figure out how to make the submodules shallow.
80/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Lower-priorityRevert "fix(ci): avoid cloning submodules when starting nix shell"by Martin Milata · 3055f082 · Nov 5, 2026 · 1 fileMessage 65 · AdequateTriage 0Details
Commit message · Martin Milata
Revert "fix(ci): avoid cloning submodules when starting nix shell"
This reverts commit 557889b65b65061c4a11e1af03ab9d71d4843ab2.
65/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Why it was queued
documentation-only discount
Security candidatetest(core): use more time-efficient passphrase pattern on touch layoutsby Roman Zeyde · 09b86896 · Nov 5, 2026 · 4 filesMessage 100 · StrongInformational 15Details
Commit message · Roman Zeyde
test(core): use more time-efficient passphrase pattern on touch layouts
Otherwise, some click tests takes >2 minutes (because they need to wait for ~1 second between consecutive clicks on the same button).
[no changelog]
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
This commit only changes automated test code for the Trezor hardware wallet. It swaps the long passphrase test string from repeated 'W' characters to an alternating 'AD' pattern so the automated click tests run faster on touch-screen layouts. There is no change to the actual firmware, wallet behavior, or security logic.
AI review queuedchore(translations): sync Crowdin translationsby Thalarion · b5d65e9d · Nov 5, 2026 · 7 filesMessage 57 · ThinInformational 15Details
Commit message · Thalarion
chore(translations): sync Crowdin translations
[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 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. It updates wording, adds missing translations, removes obsolete translation keys, and refreshes the cryptographic signature file that protects those translations from tampering. There is no code change and no security vulnerability is introduced or fixed.
Lower-priorityci: bump cachix/install-nix-action to 31.11.3by Martin Milata · f0cfd633 · Nov 5, 2026 · 1 fileMessage 72 · AdequateTriage 0Details
Commit message · Martin Milata
ci: bump cachix/install-nix-action to 31.11.3
Includes nix 2.35.3 which improves flake disk usage.
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
documentation-only discount
Lower-priorityci(core): show runners' disk usage before `action/environment`by Roman Zeyde · 3d2b5c15 · Nov 5, 2026 · 1 fileMessage 62 · AdequateTriage 0Details
Commit message · Roman Zeyde
ci(core): show runners' disk usage before `action/environment`
[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
documentation-only discount
Lower-priorityfix(core): zero ipc message header paddingby cepetr · dd85234b · Nov 5, 2026 · 1 fileMessage 80 · StrongTriage 0Details
Commit message · cepetr
fix(core): zero ipc message header padding
- Clear the entire header before populating its fields. - Avoid copying uninitialized padding bytes into the queue.
[no changelog]
80/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Security candidatefix(core): show RSOD after a fault in an IRQ handlerby cepetr · 46f736e6 · Nov 5, 2026 · 6 filesMessage 62 · AdequateLow 34Details
Commit message · cepetr
fix(core): show RSOD after a fault in an IRQ handler
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 · Low 34/100
This update changes how Trezor hardware wallets recover when something goes wrong inside an interrupt handler. Previously, the device could freeze silently instead of showing the red error screen (RSOD). Now it unwinds nested interrupt handlers and shows the error screen. The change is a robustness improvement, not a direct fix for an exploitable vulnerability, but the freeze behavior could have been used to make a device hang or confuse a user.
Lower-prioritychore(rust): update trezor-client Cargo.lockby Martin Milata · fbc5d800 · Nov 5, 2026 · 1 fileMessage 57 · ThinTriage 0Details
Commit message · Martin Milata
chore(rust): update trezor-client Cargo.lock
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): issue RASET before CASET in set_windowby bleska · acf0d278 · Nov 5, 2026 · 1 fileMessage 80 · StrongTriage 0Details
Commit message · bleska
fix(core): issue RASET before CASET in set_window - Swap the CASET/RASET order in display_panel_set_window(); the panel doesn't care, but it breaks bus sniffers syncing on 2A/2B/2C.
[no changelog]
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> (cherry picked from commit 4289e23b317e98ab6a5e8237723e0cd57f44934c)
80/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Lower-priorityci: list failed param job in HW test Slack messageby Michal Kazda · e480655e · Nov 5, 2026 · 1 fileMessage 87 · StrongTriage 0Details
Commit message · Michal Kazda
ci: list failed param job in HW test Slack message
- keep param out of the job count, but list it if it fails
[no changelog]
87/100 · StrongMessage clarity
✓ Specific, 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
documentation-only discount
Lower-priorityci: hw: fail early if uhubctl detects no hubby Martin Milata · eb9313c6 · Nov 4, 2026 · 2 filesMessage 57 · ThinTriage 0Details
Commit message · Martin Milata
ci: hw: fail early if uhubctl detects no hub
57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Lower-priorityci: send HW test Slack message only on failureby Michal Kazda · 4fff7aed · Nov 4, 2026 · 1 fileMessage 82 · StrongTriage 0Details
Commit message · Michal Kazda
ci: send HW test Slack message only on failure
- restore the nightly-only failure condition after testing
[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
documentation-only discount
Lower-priorityci: list failed jobs in HW test Slack messageby Michal Kazda · 33736f41 · Nov 4, 2026 · 1 fileMessage 90 · StrongTriage 0Details
Commit message · Michal Kazda
ci: list failed jobs in HW test Slack message
- list failed and cancelled jobs, each linked to its log - add an "N of M jobs failed" count to the header - give the notify job actions: read to query the run's jobs
[no changelog]
90/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification