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
- Allow the bot to run in other trezor-firmware repositories within the `Trezor` org.
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
Security candidatechore: bump version to 2.13.0by Jakub Janků · cf19aec3 · Oct 1, 2026 · 9 filesMessage 57 · ThinInformational 15Details
Commit message · Jakub Janků
chore: bump version to 2.13.0
[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 pathboot or update path
AI analysis · Informational 15/100
This commit is a routine version bump from 2.12.6 to 2.13.0. It only changes version numbers in a header file and translation metadata, plus updates the signed translation bundle timestamp and hash. There are no code behavior changes, no bug fixes, and no security-related modifications.
Lower-prioritychore: update releases.jsonby Jakub Janků · 3edb4e44 · Oct 1, 2026 · 1 fileMessage 62 · AdequateTriage 0Details
Commit message · Jakub Janků
chore: update releases.json
[no changelog]
(cherry picked from commit 19a20096e902a0f405a368b78785e31218344f92)
62/100 · AdequateMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope✓ Provides an explanatory body
Security candidateci: hw: add script for debugging USB permissionsby Martin Milata · efcd53c9 · Oct 1, 2026 · 3 filesMessage 57 · ThinInformational 15Details
Commit message · Martin Milata
ci: hw: add script for debugging USB permissions
[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
credential or privilege state
AI analysis · Informational 15/100
This commit adds a diagnostic script to help debug USB permission problems during automated hardware testing. It does not change any firmware code that runs on Trezor devices, nor does it alter how user funds or secrets are handled. It only collects system information (like USB device listings and library dependencies) and saves it as a log file for CI troubleshooting.
Security candidatedocs(legacy): add changelog for 1.14.2by Jakub Janků · 74f98873 · Oct 1, 2026 · 9 filesMessage 72 · AdequateInformational 15Details
Commit message · Jakub Janků
docs(legacy): add changelog for 1.14.2
[no changelog]
(cherry picked from commit a0386b23e6de54d2131602b7bd6743bb2724c6dd)
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 pathauthentication path
AI analysis · Informational 15/100
This commit is purely a documentation update: it adds the release notes for Trezor legacy firmware version 1.14.2. The actual code changes being described were made in earlier commits. Because no source code is modified here, this commit itself does not introduce, fix, or change any security behavior in the firmware.
AI review queueddocs(core): add changelog for 2.13.0by Jakub Janků · 7489d4ea · Oct 1, 2026 · 30 filesMessage 72 · AdequateModerate 61Details
Commit message · Jakub Janků
docs(core): add changelog for 2.13.0
[no changelog]
(cherry picked from commit 5ecc834612f8482aaa0e9caa2a130124be0fe753)
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: unusually broad changesecond-pass: security-sensitive path
AI analysis · Moderate 61/100
This commit is a documentation-only changelog update for the Trezor firmware 2.13.0 release. It does not change any code. The changelog describes several previously committed security fixes for Monero, Cardano, Solana, and Stellar transaction handling, plus some feature and bug fixes. Because the actual code changes happened in earlier commits, this commit itself is not a security patch, but it publicly discloses that multiple security-relevant fixes are included in the release.
Following [Tropic FW update](https://github.com/trezor/trezor-firmware/pull/7929) (to be released in 2.13.0 FW).
[no changelog]
(cherry picked from commit a6e345126ad969011876ecb3cb686b4e3dc8d5f6)
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
Lower-prioritychore: update definitions timestampby Jakub Janků · 5cfa7acc · Oct 1, 2026 · 2 filesMessage 62 · AdequateTriage 0Details
Commit message · Jakub Janků
chore: update definitions timestamp
[no changelog]
(cherry picked from commit 9fd4c3d2dc8774286f0ba9bf92767346adb61cdc)
62/100 · AdequateMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope✓ Provides an explanatory body
Lower-prioritychore(deps): bump urllib3 from 2.7.0 to 2.8.0by M1nd3r · 0c2cb6c8 · Oct 1, 2026 · 2 filesMessage 93 · StrongTriage 0Details
✓ 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
automated dependency-update discount
Lower-priorityci: increase `Dependencies uv` timeoutby Roman Zeyde · a532006f · Oct 1, 2026 · 1 fileMessage 57 · ThinTriage 0Details
Commit message · Roman Zeyde
ci: increase `Dependencies uv` timeout
[no changelog]
57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
✓ 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 17/100
This commit is a code cleanup that adds Rust-language bindings for an existing internal error/status type used inside the Trezor firmware. It does not change how user funds or secrets are handled. The main observable effect is that Rust code can now check and report low-level device errors more cleanly, and one screen callback now handles errors more carefully instead of crashing. There is no direct security fix here, but it improves future error-handling hygiene.
✓ Subject identifies a change✓ Uses a recognizable type or scope! No meaningful explanatory body
Lower-priorityci(core): run Python unit tests with WARD enabledby Jakub Janků · 76bfa7f1 · Sep 30, 2026 · 1 fileMessage 90 · StrongTriage 0Details
Commit message · Jakub Janků
ci(core): run Python unit tests with WARD enabled
WARD is only built together with Miniscript, which is not supported for universal builds, so add a T3T1 btc-only Miniscript entry to the Python unit test matrix.
[no changelog]
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
feat(ethereum): Unknown vaults fetch relevant token defintion from host
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 · Low 36/100
This commit changes how Trezor handles Ethereum 'vault' transactions (like deposits and withdrawals from yield-bearing token vaults). Previously, the device only supported a fixed list of known vaults and rejected or blindly signed unknown ones. Now, for unknown vaults, it asks the connected computer (host) for token and display definitions so it can show clearer signing information. The change also removes a hard safety check that rejected transactions where the receiver or owner did not match the signer for known vaults, and instead lets the UI display the receiver/owner explicitly. This is a feature addition, but it introduces new trust in host-provided data and relaxes a previously strict safety rule.
refactor(core): add Rust bindings for noise_xxpsk3
[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 pathboot or update path
AI analysis · Informational 11/100
This commit adds Rust programming-language wrappers around an existing C library for a secure communication protocol called Noise XXpsk3. It does not change the underlying cryptographic logic or fix any bug; it is a code organization (refactoring) change that lets other parts of the Trezor firmware call the Noise XXpsk3 routines from Rust. There is no direct security problem visible in the change itself.
✓ 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 pathtranslation-only discountsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit only updates translated text strings in German, French, and Portuguese, plus the translation signature metadata. There are no code or security changes.
Lower-priorityfeat(core): implement WARD record storeby Jakub Janků · d61d53fc · Sep 30, 2026 · 5 filesMessage 80 · StrongTriage 0Details
Commit message · Jakub Janků
feat(core): implement WARD record store
- store each record in its own slot of the `APP_WARD` storage namespace, with a header (version, wallet id prefix, length-prefixed app identifier) and a version 0 body (key length, key, value) - bound the number of records, the record length and the total length; nothing is ever evicted - records this version cannot parse (same-scope unknown-version or malformed) are skipped and can't be listed or deleted; handling them is out of scope for now, the header lets a later change surface them and delete them with user approval
[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
Lower-priorityfeat(core): add WARD service scaffoldby Jakub Janků · a0dbdd45 · Sep 30, 2026 · 11 filesMessage 80 · StrongTriage 0Details
Commit message · Jakub Janků
feat(core): add WARD service scaffold
Declare the `trezorward` store API and `WardError`, add the `apps.ward` package (`with_ward`, `WardStore`), and reserve the `APP_WARD` storage namespace. The bodies raise `NotImplementedError` for now.
[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
AI review queuedfix(ethereum): Remove hardcoded names for registry known addressesby PrisionMike · 5f1c1003 · Sep 30, 2026 · 4 filesMessage 62 · AdequateInformational 24Details
Commit message · PrisionMike
fix(ethereum): Remove hardcoded names for registry known addresses
[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 24/100
This commit removes a long list of hardcoded friendly names (like 'Lido', 'Morpho', 'WalletConnect') that Trezor devices previously showed when signing Ethereum transactions to certain smart contracts. After the change, only a few built-in names remain (mainly 'WETH' and a test address), and most contracts will be shown to the user as raw addresses instead of recognizable labels. The change is framed as a cleanup to rely on an external registry rather than hardcoded names. It is not a direct security fix for a vulnerability, but it reduces the risk that a wrong or misleading hardcoded label could trick a user into trusting a malicious contract.
Lower-priorityfix(translations): do not blank `instructions__hold_to_confirm` with Caesar layoutby M1nd3r · a1c30e91 · Sep 30, 2026 · 1 fileMessage 62 · AdequateTriage 0Details
Commit message · M1nd3r
fix(translations): do not blank `instructions__hold_to_confirm` with Caesar layout
[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
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
access controlauthentication path
AI analysis · Informational 15/100
This commit is a user-interface polish fix for the Trezor hardware wallet's passphrase entry screen. It replaces a static text label with a scrolling 'marquee' so that longer prompts fit on the small device screen. There is no security-relevant change here.
Security candidatefeat(clear_signing,test): added script to update the latest definitions from prodby PrisionMike · fab3bea4 · Sep 30, 2026 · 3 filesMessage 72 · AdequateInformational 15Details
Commit message · PrisionMike
feat(clear_signing,test): added script to update the latest definitions from prod
[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 boundary
AI analysis · Informational 15/100
This commit adds two helper scripts for Trezor's internal testing workflow. They download or convert signed Ethereum/Solana definition files and verify their digital signatures before converting them into JSON test fixtures. There is no change to the firmware that runs on customer devices, no change to how signatures are verified in production code, and no disclosed security issue.