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.
Security candidatefeat: sanity-check seed entropyby Andrew Kozlik · 14aa0b6d · Aug 1, 2026 · 6 filesMessage 77 · AdequateModerate 61Details
Commit message · Andrew Kozlik
feat: sanity-check seed entropy
[no changelog]
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
77/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Names security-relevant behavior explicitly
Why it was queued
entropy or randomnesscryptography-sensitive pathboot or update path
AI analysis · Moderate 61/100
This commit adds safety checks during wallet creation to make sure the randomness used to generate the recovery seed is long enough and not obviously broken. It also aborts the setup process cleanly if something arrives at the wrong time. These are defensive hardening changes rather than a fix for a known active attack.
Security candidatefeat(common,core,python): improve UX for SEP-41 token invocations of Stellar Asset Contracts.by Jun Luo · 78f7c19e · Aug 1, 2026 · 30 filesMessage 62 · AdequateInformational 23Details
Commit message · Jun Luo
feat(common,core,python): improve UX for SEP-41 token invocations of Stellar Asset Contracts.
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 pathsigning or wallet pathauthentication path
AI analysis · Informational 23/100
This commit improves the on-screen display for certain Stellar smart-contract token operations. It lets a connected wallet tell the Trezor device that a contract call is actually a well-known token transfer or approval, so the user sees a friendlier 'Send' or 'Approve' screen instead of raw technical data. The device independently recalculates the token contract address from the hint and only uses the friendly screen if the address matches; a wrong hint falls back to the raw display. The change is a user-experience enhancement, not a fix for a known security flaw.
Security candidatefix(core/ui): stop dropping the subtitle of the Stellar amount screen on caesar.by Jun Luo · b864ed99 · Aug 1, 2026 · 1 fileMessage 62 · AdequateInformational 18Details
Commit message · Jun Luo
fix(core/ui): stop dropping the subtitle of the Stellar amount screen on caesar.
[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 · Informational 18/100
This commit fixes a user-interface bug in Trezor hardware wallets where the subtitle line on the Stellar cryptocurrency transaction confirmation screen was accidentally dropped. The fix joins the title and subtitle into a single line so users see both pieces of context before signing. It is a UI clarity issue, not a cryptographic or code-execution vulnerability.
Security candidatechore: guard against insecure PRNG in production buildby Andrew Kozlik · 16e23d34 · Jul 31, 2026 · 3 filesMessage 77 · AdequateLow 42Details
Commit message · Andrew Kozlik
chore: guard against insecure PRNG in production build
[no changelog]
Co-Authored-By: Claude Fable 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
entropy or randomnesscryptography-sensitive path
AI analysis · Low 42/100
This commit adds safety guards to prevent a deliberately weak random-number generator from being included in production firmware builds, and stops emulator builds from being labeled as production builds. It does not by itself fix a vulnerability in shipped code; it is a build-time hardening measure against accidental misconfiguration.
refactor(core/rust/crypto): prepare crypto crate for API bindings
Introduces the concept of a "copy hazard" separate from unsafety, replacing pinning. A "copy hazard" is the possibility of Rust auto-copying owned structs containing sensitive data.
Replaces the "memory" module with "secret", introducing well documented helper types specifically for copy hazard: * SecretContext is a zeroizing wrapper over the raw memory. By itself, not super useful, except that it implements Default for types tagged with the unsafe marker type ZeroableMemory (ffi contexts). * SecretContextLock holds a generic DerefMut "lock" over a SecretContext, forcing the borrow checker to prevent copy hazards: the compiler is not free to move around memory while a live DerefMut pointer to it exists. Zeroizes on drop.
Introduces implementation separation on hasher-like structs (that is the various SHAs plus HMAC): * "hazardous" base methods are implemented on a SecretContext<ffi_type>, delegating hazard responsibility to caller, * non-hazardous methods are implemented on a wrapper struct (Sha256, Sha3_256 in the followup PR) that takes a SecretContextLock, which zeroizes on drop, so whenever the computation is either (a) finished or (b) abandoned, the memory is zeroed before unlocking.
Trezor THP already takes advantage of this split by using hazard methods directly (with the appropriate comment), without needing a separate NoPinSha implementations.
This is also preparation for the SDK API bindings, which will introduce their own secure wrapper for the hasher structs.
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 safetycryptography-sensitive path
AI analysis · Informational 20/100
This is a large internal refactor of how Trezor's Rust crypto code handles sensitive memory. It replaces an older pinning-based mechanism with a new 'copy hazard' framework designed to prevent Rust from accidentally duplicating secret data in memory. The change itself is defensive and does not appear to introduce a new vulnerability; rather, it is a hardening measure. However, because it touches low-level cryptographic state handling across many files, any mistake in the new abstraction could theoretically affect how secrets are cleared from memory.
✓ 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 pathauthentication path
AI analysis · Informational 15/100
This commit adds Bluetooth Low Energy (BLE) support for the Trezor T3T2 hardware model. It introduces new board configuration files, pin mappings, build scripts, and firmware binaries for the Nordic nRF54LS05A BLE radio used in T3T2. There is no indication in the commit that this fixes a security bug; it appears to be a feature addition enabling BLE functionality on a new device variant.
✓ 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 housekeeping change that reorganizes the feature sections inside 14 Cargo.toml build configuration files. It reorders, renames, and groups feature flags (such as MCU selection, privilege mode, build options, and selectable components) without changing the actual feature names, their meanings, or the underlying source code. There is no indication this affects device behavior or security.
in rtl: * provide headers for error_shutdown and __fatal_error (and variants) * implement all except error_shutdown_ex_n and __fatal_error_n * if feature error_shims is activated (dependency of test), also error_shutdown_ex_n and __fatal_error_n are implemented via unix calls
in crypto: * implement tc_fault_handler by delegating to error_shutdown
in sys: * add error_handling.c, which provides global implementations of error_shutdown_ex_n and __fatal_error_n by delegating to system_exit_error/fatal
in conclusion: the error failure functions are forward-declared in rtl, and waiting for _someone_ to provide an implementation at link time
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
Why it was queued
cryptography-sensitive pathboot or update path
AI analysis · Informational 17/100
This commit is a code cleanup that moves how Trezor firmware handles fatal errors and shutdowns between its internal software layers. It does not add new user-facing features or change security protections. The main risk is that reorganizing low-level error paths could accidentally introduce a bug, but the diff itself does not show a vulnerability being fixed or introduced.
Security candidatefeat(core/rust): separate trezor-crypto to its own Rust crateby matejcik · 836142c7 · Jul 31, 2026 · 39 filesMessage 62 · AdequateInformational 15Details
Commit message · matejcik
feat(core/rust): separate trezor-crypto to its own Rust crate
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 15/100
This commit is a large but straightforward internal refactoring: the cryptographic code is moved from one Rust crate (`rtl`) into a new dedicated crate (`crypto`), and all project dependencies are updated to point to the new crate. The actual cryptographic algorithms, build flags, and source files remain the same. There is no indication of a security bug fix or a vulnerability being introduced.
Security candidaterefactor(python): extract model definition into single fileby tychovrahe · e16fbb27 · Jul 31, 2026 · 19 filesMessage 62 · AdequateInformational 15Details
Commit message · tychovrahe
refactor(python): extract model definition into single file
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 is a code cleanup (refactor) in the Python trezorlib library. It moves Trezor hardware model definitions (names, USB IDs, firmware verification keys, hash settings, UI layout, BLE capability) from several scattered files into one shared module. The actual data values appear unchanged; only the organization of the code changed. There is no indication this fixes a security bug or introduces a vulnerability.
Security candidatechore(core): add trailing colon for Bolt/Caesar EIP-7702 info itemsby Roman Zeyde · 243a9d21 · Jul 30, 2026 · 3 filesMessage 62 · AdequateInformational 15Details
Commit message · Roman Zeyde
chore(core): add trailing colon for Bolt/Caesar EIP-7702 info items
[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 · Informational 15/100
This is a cosmetic user-interface change for the Trezor hardware wallet. It adds a trailing colon to labels shown when a user is reviewing Ethereum EIP-7702 authorization or revoke actions. There is no security impact: no code logic, cryptography, transaction parsing, or signing behavior is changed. The only side effect is that on-screen text labels now end with a colon, and the corresponding UI test snapshots (fixtures.json) were updated to match the new appearance.
✓ 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 pathauthentication path
AI analysis · Informational 19/100
This commit is a large internal refactoring that moves time-related code (Duration, Instant, sleep, tick counters) from one Rust module to another shared system module so it can be reused more cleanly. It does not change what the code does; it only reorganizes where the definitions live. There is no obvious security bug introduced, but any big refactor carries a small risk of accidental behavior changes.
fix(core/bootloader): correct "Change FW vendor" title
[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
update trustboot or update path
AI analysis · Informational 15/100
This commit changes a single on-screen label in the Trezor bootloader from lowercase 'Change fw vendor' to uppercase 'Change FW vendor'. It is purely a cosmetic wording fix with no security relevance.
✓ 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 · Low 30/100
This commit adds support in Trezor's Ethereum clear-signing feature for transactions that contain multiple embedded subcalls (like a multicall). Previously, only a single embedded call could be clearly displayed. The change lets the device show each subcall separately with labels like "(Subcall #1)" and handles both a single shared recipient address or a parallel list of recipients. It is a feature addition, not a fix for a known vulnerability.
✓ 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 only adds new automated tests for Trezor's Ethereum 'clear signing' feature. It includes a test case for an Aave multi-call transaction, a matching test data blob, and expected screen snapshots for different device models and languages. There are no changes to the actual firmware code that runs on the device, so this commit does not introduce or fix a security vulnerability.
✓ 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 pathtranslation-only discount
AI analysis · Informational 15/100
This commit simply updates a metadata file that records a digital signature (a 'merkle_root') for translation data in a Trezor hardware wallet. There is no code change, no bug fix, and no security issue visible in the diff. It appears to be a routine administrative update to keep the signature record in sync with the latest translation content.
✓ 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 adds a new display formatter for Ethereum clear signing. It lets a transaction descriptor map numeric enum values (like 1 or 2) to human-readable labels (like 'stable' or 'variable') on the Trezor screen. The change is purely additive and includes tests. There is no indication it fixes a security bug or introduces a vulnerability; it is a feature implementation.
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
signing boundary
AI analysis · Informational 15/100
This commit only adds new data structures and an enum value for a future 'enum formatter' feature in Trezor's Ethereum clear-signing support. It does not change any existing behavior, add parsing logic, or fix a bug. There is no security issue visible in this change.
- compare rendered strings now. - small typo in a test fixture name.
[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 boundarysigning or wallet path
AI analysis · Informational 19/100
This commit fixes a user-interface bug in Trezor's Ethereum 'clear signing' flow where the transaction's native ETH amount could be shown twice on the device screen. The old code tried to avoid duplication by checking whether an 'AmountFormatter' field was present, but that check missed cases where the same amount was rendered by other field types. The new code compares the actual rendered strings and suppresses the summary amount only when it exactly matches a field already displayed. There is no security vulnerability here; it is purely a display-quality fix.
feat(clear_signing): support for calldata formatter. - scaffolding
[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 boundary
AI analysis · Informational 15/100
This commit is purely scaffolding for a new Ethereum clear-signing feature. It adds a new data type (FORMATTER_CALLDATA), two new optional fields (callee_path and selector) to message definitions, and two new user-facing text labels ('Subcall' and 'Subcall to'). There is no actual implementation of parsing, validation, or display logic here, and no security vulnerability is visible in the diff.
test(clear_signing): add device test for calldata formatter.
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 only adds a new automated test case for an existing Ethereum transaction display feature. It does not change any production firmware code, so it cannot introduce a security vulnerability or fix one. It is purely a test-data addition.
✓ 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 23/100
This commit is a test-only addition for Trezor's Ethereum 'clear signing' feature. It adds new test cases and makes a small production-code tweak so that enum display-formatters can accept byte values (converted to integers). The change is not described as a security fix, and the production change is minor and defensive: it broadens accepted input types rather than fixing a crash or bypass. There is no evidence of a disclosed vulnerability or exploit.
feat(clear_signing): support for calldata formatter. - core changes
[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 · Low 39/100
This commit adds a new Trezor firmware feature called 'clear signing' for nested Ethereum calls. It lets the device understand when a transaction wraps another contract call (like a router or multicall) and tries to show the user readable details about the inner call instead of just a blob of hex. The change is a feature addition with built-in safeguards: nested parsing is limited to one level, ambiguous fields like sender and value are blocked inside nested calls, and failures fall back to showing raw hex rather than aborting the whole transaction. There is no indication in the commit that this fixes a known security bug; it reads as a defensive new capability.
✓ 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 user-interface layout tweak for the Trezor hardware wallet's Bolt design. It widens the 'Continue' button and replaces some text buttons with icons in certain confirmation dialogs. There is no security-relevant change visible in the code diff.
- do not persist conflicting token from actions/checkout - remove failing git command that is no longer needed - explicitly specify required permissions
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
credential or privilege statedocumentation-only discount
AI analysis · Informational 16/100
This commit adjusts a GitHub Actions workflow that synchronizes code between two Trezor repositories. The changes remove a leftover default authentication token, explicitly request only the write permission needed for contents, and drop an unnecessary git command. These are hardening improvements rather than a fix for an active vulnerability.