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 commit removes the SHA-1 hashing function from the regular Trezor firmware. SHA-1 is an old, weak hash algorithm that is no longer considered secure for sensitive uses. The change deletes the code that exposes SHA-1 to apps running on…
Removal of a deprecated cryptographic primitive (SHA-1) from the firmware API surfaceReduction of attack surface and prevention of future misuse of a collision-vulnerable hashNo direct vulnerability patch or memory-safety bug is present in the diff
This commit changes how a cryptographic library sets up secure connections. Previously, the code automatically calculated the public key from the private key. Now, the caller must provide the public key directly. This is a code-quality ref…
Cryptographic key handling changed: public key is now supplied rather than derivedPotential reduction of key-mismatch risk if caller provides correct public keyNew null-pointer check added for static_public_key
This commit simply reorders the arguments of an internal function called dh() and updates every place that calls it. The actual math and security behavior are unchanged; it is a code cleanup with no security effect.
This commit simply renames two groups of internal status labels (called enums) in the Trezor firmware's cryptographic code. The old names like WAITING_FOR_REQUEST1 were shared between two different parts of the code, so the developer gave …
This commit fixes three places in the Trezor firmware's cryptographic code where a memory-clearing function could be called with a NULL pointer. In practice, passing NULL to memzero is harmless on Trezor's platform (it does nothing), but i…
NULL pointer passed to memory-zeroing helper in cryptographic codeUndefined behavior in C standard library contractDefensive hardening in Noise protocol implementation
This commit is a code cleanup (refactor) for the cryptographic handshake code used in Trezor devices. It changes how the other party's long-term public key is returned to the caller: instead of storing it inside an internal state structure…
Removal of long-term public key storage from internal handshake stateCaller-supplied output buffer for remote static public key reduces internal secret retentionError-path memzero of returned key material on failure
This commit is a build-system refactoring for Trezor firmware. It moves the mapping of command-line build options to Rust/cargo features out of hard-coded Rust logic and into per-project TOML files. It also adds a small change so debug bui…
Build-option mapping now lives in project.toml files, increasing the attack surface for supply-chain/build-configuration tamperingMakefile change automatically enables debug-link for PYOPT=0 debug buildsValidation added to reject storage_insecure_testing_mode in production builds
This commit only updates test data. It corrects the capitalization (checksum) of Ethereum addresses used in automated tests and refreshes the expected screen-shot hashes those tests compare against. There are no changes to the actual Trezo…
This commit changes the Trezor Python library so that, when setting up a Trezor Model One (the original Trezor 1 device), it now performs an entropy check by default if the device runs firmware 1.13.1 or newer. Previously, the library only…
Enables a previously disabled security/validation feature (entropy check) for a specific device modelAdds version-gated behavior to avoid errors on older firmwareDefensive hardening of wallet setup randomness verification
This commit is a routine cleanup that removes the old SCons build system files from the Trezor Core firmware repository. It deletes Makefiles, SConscripts, and related Python helper scripts, but does not change any firmware source code, cr…
This commit updates Trezor's embedded MicroPython interpreter from an older version to 1.28.0. It pulls in several upstream MicroPython bug fixes, including stricter buffer-size checks for converting integers to bytes, a new stack-safety A…
Synchronizes upstream MicroPython fixes that include buffer-size and stack-safety hardeningPrevents Ctrl+C interruption of frozen boot code, reducing denial-of-service/control-flow risk during bootFixes sys.stdout.buffer.write() return value, which could affect code relying on correct I/O semantics
This commit is a simple code cleanup that replaces a common MicroPython string-creation pattern with a new helper function. It does not change what the code does, only how it is written. There is no security issue visible in the change.
This is a large but straightforward internal cleanup: the project switched from using the MicroPython `ubinascii` module's `hexlify`/`unhexlify` functions to the standard Python `bytes.hex()` and `bytes.fromhex()` methods. The change remov…
This commit is a routine code cleanup in the Trezor firmware's embedded MicroPython modules. It replaces an older, two-step object allocation pattern with a newer helper that allocates memory and sets the object type in one step. The chang…
No security-relevant logic changes observedNo input validation changesNo memory safety bug fixes (e.g., no overflow, use-after-free, or uninitialized memory fixes)
This commit is a routine maintenance refactor. MicroPython removed its built-in 'utimeq' module, so Trezor copied the same code into its own firmware tree and renamed it to 'timeq'. There is no security bug being fixed and no new vulnerabi…
This is a code cleanup change in Trezor's firmware that swaps one MicroPython internal helper for another. It replaces calls that create byte or string objects from a vstr buffer with newer, purpose-built helpers. The commit message says t…
Refactor only: helper function renames with equivalent semanticsNew str helper adds UTF-8 validation; bytes helper does not validateNo input validation, length, or error-handling changes observed
This commit is a routine internal cleanup that switches how Trezor's firmware defines built-in MicroPython object types. It replaces older, manually-written type structures with a newer macro provided by the upstream MicroPython project. T…
This commit is a straightforward internal code refactor. It adds a small C wrapper file so that Rust code can call two specific internal MicroPython functions that are declared as static/inline in headers. There is no user-facing change, n…
This commit is a routine build-system update for the Trezor firmware. It changes where the build process looks for the MicroPython cross-compiler binary (mpy-cross) and synchronizes a configuration header with newer MicroPython code. There…
This commit updates the Trezor firmware build system to use a newer MicroPython mechanism for tracking special memory pointers called 'root pointers.' It removes hard-coded lists of these pointers from configuration files and instead colle…
GC root pointer handling changedBuild system now auto-collects root pointers instead of hard-coding themRemoves manual MICROPY_PORT_ROOT_POINTERS lists
Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.
Lower-prioritytest(core): check Optiga presence once per sessionby Roman Zeyde · e72f9596 · Jul 14, 2026 · 2 filesMessage 72 · AdequateTriage 0Details
Commit message · Roman Zeyde
test(core): check Optiga presence once per session
[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
AI review queuedtest(core): wait for `Cancel` response before sending `Ping`by Roman Zeyde · a6bffbca · Jul 14, 2026 · 1 fileMessage 100 · StrongInformational 15Details
Commit message · Roman Zeyde
test(core): wait for `Cancel` response before sending `Ping`
Otherwise, we may get stuck when using USB transport: if the device is stuck sending, and not reading new messages from the host, the first write may get stuck - and the test will deadlock.
[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
Why it was queued
parser or protocol pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This is a test-only change to the Python Trezor client library. It fixes a potential deadlock in test synchronization code by waiting for a response to a Cancel message before sending a Ping message. There is no change to device firmware or any security-sensitive behavior, and no security vulnerability is present in the commit.
Security candidatefix(core): don't drop layout objects after `draw_simple()`by Roman Zeyde · 155fa8d2 · Jul 14, 2026 · 7 filesMessage 85 · StrongLow 44Details
Commit message · Roman Zeyde
fix(core): don't drop layout objects after `draw_simple()`
After `draw_simple()` is called, `layout` is still referenced by `trezor.ui.CURRENT_LAYOUT` and its event-handling tasks are still running.
Therefore, it MUST NOT be dropped, until a new layout is started.
[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 pathboot or update path
AI analysis · Low 44/100
This commit fixes a bug in the Trezor hardware wallet's user-interface code. Previously, certain simple on-screen messages were wrapped in a Python `with` block, which caused the underlying layout object to be cleaned up (dropped) as soon as the message was drawn. However, the system still held a reference to that layout and its background event-handling tasks were still running. Dropping it early could lead to a crash, a frozen screen, or undefined behavior while the device is showing important prompts such as asking the user to enter their passphrase on a host computer or displaying a 'please wait' message. The fix removes the `with` wrapper so the layout object stays alive until a new screen replaces it.
Security candidatechore(core/ethereum): drop EIP-7702 delegation support for nowby PrisionMike · 347c3c4d · Jul 14, 2026 · 6 filesMessage 98 · StrongInformational 15Details
Commit message · PrisionMike
chore(core/ethereum): drop EIP-7702 delegation support for now
Splitting #6983 into smaller PRs.
Reverts 307d601abe4ad0d3cd80b3fffab9ab3f7f80f085 functionality. Will be re-added after EIP-7702 authorization is implemented.
[no changelog]
Co-authored-by: Roman Zeyde <roman.zeyde@satoshilabs.com>
98/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✓ Names security-relevant behavior explicitly
Why it was queued
access controlsigning or wallet path
AI analysis · Informational 15/100
This commit removes support for a new Ethereum transaction type (EIP-7702) from Trezor hardware wallets. It is described by the developers as a temporary revert of a feature that will be re-added later. There is no indication this is a security fix; it is a feature removal for code organization.
✓ Descriptive subject✓ 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. It changes no program logic, fixes no bugs, and introduces no security-relevant behavior. There is nothing here that could be exploited or that changes how the device protects data.
fix(core/caesar): remove count limit in confirm_properties
Properties were eagerly parsed into a fixed-capacity ParagraphVecLong (36 paragraphs, i.e. 18 key-value pairs), which panicked in debug builds and silently truncated the list in production when exceeded. Use the lazy PropsList paragraph source instead, as in the other layouts. PROP_INNER_SPACING is set to 2 px to match the key-value spacing hardcoded in the add_paragraphs helper, so rendering is unchanged.
[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 pathboot or update path
AI analysis · Moderate 51/100
This commit fixes a bug in the Trezor hardware wallet's Caesar UI layout where long lists of key-value properties (for example, transaction details shown on the device screen) could either crash debug builds or be silently cut off in production builds. The fix replaces a fixed-size container with a lazy, unbounded one, so all properties are rendered and none are dropped. There is no direct evidence in the commit that this was exploited or treated as a security vulnerability by the vendor.
✓ 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 path
AI analysis · Informational 18/100
This is a code cleanup and type-safety refactor for the Monero parts of the Trezor firmware. It adds stricter type hints, asserts that certain values are not missing, and fixes a minor return-value bug in a helper that encrypts data. There is no direct evidence this commit fixes an active security vulnerability, but it reduces the chance of future bugs by making assumptions explicit.
tests: replace repeated xfail/suppresion by decorators
- Replaced repeated "optiga xfail" in `evolu/test_sign_registration` by a decorator. - Replaced repeated ephemeral key warning suppression in `thp/test-pairing` by marker alias.
[no changelog]
83/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit is a test-code cleanup only. It replaces repeated snippets in automated tests with reusable decorators and marker aliases. No firmware behavior, cryptography, or user-facing functionality is changed, so it has no security impact on Trezor devices.
AI review queuedtest(core): try to avoid old emulators' crashing during upgrade testsby Roman Zeyde · 468b7d75 · Jul 10, 2026 · 1 fileMessage 100 · StrongInformational 17Details
Commit message · Roman Zeyde
test(core): try to avoid old emulators' crashing during upgrade tests
Should help with https://github.com/trezor/trezor-firmware/issues/7052.
IIUC, #1725 was introduced to save memory, but it may crash the emulator if debuglink and wirelink are used at the same time.
[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✓ Links an issue, advisory, or supporting reference
Why it was queued
second-pass: broader security terminology
AI analysis · Informational 17/100
This commit is a test-only workaround that adds a one-second sleep in an upgrade test script for older Trezor emulator versions. It avoids a known emulator crash during automated recovery tests when debug and wire communication are used simultaneously. It does not change the firmware itself or fix a security vulnerability in shipped devices.
Security candidatebuild(core): enable and start Tropic emulator by defaultby Martin Milata · afb0fdd4 · Jul 9, 2026 · 16 filesMessage 62 · AdequateInformational 18Details
Commit message · Martin Milata
build(core): enable and start Tropic emulator by default
[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 pathauthentication path
AI analysis · Informational 18/100
This commit changes how the Trezor firmware build and test tooling handles the Tropic secure-element emulator. Previously, Tropic support was disabled by default in Unix emulator builds and had to be explicitly enabled; now it is enabled by default and the test harness starts the Tropic model automatically. It also refactors port allocation so each emulator worker reserves a wider block of ports. The changes are confined to build scripts, CI workflows, and test/development tooling. There is no direct fix for a runtime vulnerability in shipped firmware, but enabling a hardware-security emulator by default could theoretically expose test-only code paths or secrets if the emulator is misused outside of testing.
Security candidatechore: enable pyright for emu.py and scripts in test/by Martin Milata · 16a7a0b8 · Jul 9, 2026 · 9 filesMessage 72 · AdequateInformational 15Details
Commit message · Martin Milata
chore: enable pyright for emu.py and scripts in test/
[no changelog]
72/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
cryptography-sensitive pathboot or update path
AI analysis · Informational 15/100
This commit is a routine developer tooling change. It turns on stricter Python type checking (Pyright) for the emulator script and some test helper scripts, and makes small code adjustments so those files pass the new checks. There is no change to the security-critical Trezor firmware itself, wallet operations, or cryptographic handling.
Lower-prioritytest(core): enable logging from tests and fixturesby Martin Milata · a22031d5 · Jul 9, 2026 · 1 fileMessage 72 · AdequateTriage 0Details
Commit message · Martin Milata
test(core): enable logging from tests and fixtures
[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
Lower-prioritychore: make python 3.12 the pyright baselineby Martin Milata · 9c1a3a7c · Jul 9, 2026 · 3 filesMessage 90 · StrongTriage 0Details
Commit message · Martin Milata
chore: make python 3.12 the pyright baseline
Keep 3.10 in pyproject.toml for now since the project should still be buildable on older systems. The incompatibility only affects tests.
[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
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Lower-priorityrefactor(core): add option that prints basic emulator propertiesby Martin Milata · 35c98847 · Jul 9, 2026 · 3 filesMessage 62 · AdequateTriage 0Details
Commit message · Martin Milata
refactor(core): add option that prints basic emulator properties
[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
Lower-prioritytest(core): only start Tropic model if the Trezor emulator needs itby Martin Milata · eadb8c1a · Jul 9, 2026 · 3 filesMessage 72 · AdequateTriage 0Details
Commit message · Martin Milata
test(core): only start Tropic model if the Trezor emulator needs it
[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
feat(core/python): create testing module in trezorlib
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
cryptography-sensitive pathsigning or wallet pathboot or update pathauthentication path
AI analysis · Informational 15/100
This commit is a routine code reorganization: it moves existing test-only helper code from the project's internal test directory into the public `trezorlib` Python package as a new `testing` module. The moved code includes utilities for handling emulated devices during tests, translation blob helpers, and Bitcoin compact-size encoding. There is no change to the firmware that runs on Trezor devices, no change to production cryptography, and no security fix or vulnerability introduced.
Lower-priorityci(core): increase individual test timeout for upgrade testsby Martin Milata · 5e4aec49 · Jul 9, 2026 · 1 fileMessage 72 · AdequateTriage 0Details
Commit message · Martin Milata
ci(core): increase individual test timeout for upgrade tests
[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
documentation-only discount
Lower-priorityfix(core): embed the bitcoin-only vendor header in bitcoin-only buildsby Andrew Kozlik · b517e0a0 · Jul 9, 2026 · 1 fileMessage 62 · AdequateTriage 0Details
Commit message · Andrew Kozlik
fix(core): embed the bitcoin-only vendor header in bitcoin-only builds
[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
AI review queuedchore(python): remove remaining TrezorClientDebugLink references [no changelog]by Arnold K · 64601614 · Jul 8, 2026 · 3 filesMessage 93 · StrongInformational 15Details
- Remove stale docstring reference in debuglink.py - Drop obsolete snippet scripts sign_tx.py and unify_test_files.py - No changelog entry per trezor-firmware changelog guidelines
93/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit is a routine cleanup: it updates one comment in a debug helper file and deletes two old developer-only snippet scripts that referenced an outdated class name. There is no change to the firmware, wallet logic, cryptography, or any code that runs on user devices. It does not fix or introduce any security issue.
ci(core): avoid restarting MicroPython event loop for faster tests
[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
Lower-priorityci(core): avoid rehashing the screenshotsby Roman Zeyde · 17640ca1 · Jul 8, 2026 · 1 fileMessage 57 · ThinTriage 0Details
Commit message · Roman Zeyde
ci(core): avoid rehashing the screenshots
[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
signing or wallet pathboot or update path
AI analysis · Informational 15/100
This commit adds support for a new Trezor hardware model, the T3T2. It is a product enablement change that introduces board definitions, memory layouts, bootloader hashes, vendor headers, and Python tooling entries for the new device. There is no indication of a security vulnerability or a fix for one.