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.
Lower-priorityfeat(python): store the prodtest emulator flash as `trezor_prodtest.flash`by Ondřej Vejpustek · 122076ec · Oct 15, 2026 · 1 fileMessage 85 · StrongTriage 0Details
Commit message · Ondřej Vejpustek
feat(python): store the prodtest emulator flash as `trezor_prodtest.flash`
The name is distinct from the firmware emulator's `trezor.flash`, so both emulators can share a profile directory without overwriting each other's flash.
[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
Lower-priorityrefactor(core): use xtask ---log-level for C loggingby cepetr · 5fdc180b · Oct 15, 2026 · 2 filesMessage 62 · AdequateTriage 0Details
Commit message · cepetr
refactor(core): use xtask ---log-level for C logging
[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-priorityfix(python): wrap BLE transport errors in TransportExceptionby tychovrahe · 81e36dc8 · Oct 15, 2026 · 1 fileMessage 85 · StrongTriage 0Details
Commit message · tychovrahe
fix(python): wrap BLE transport errors in TransportException
Errors from the BLE process (RuntimeError, KeyError, BleakError) reached callers raw; open, read and write now raise TransportException like the WebUSB transport does, so callers can catch the transport's own exceptions. Timeout passes through unchanged.
[no changelog]
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Lower-priorityfix(core/xtask): collect build artifacts with --asanby cepetr · f6278e2e · Oct 15, 2026 · 4 filesMessage 62 · AdequateTriage 0Details
Commit message · cepetr
fix(core/xtask): collect build artifacts with --asan
[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-priorityfeat(core): start a TROPIC01 model from `prodtest_emu.py`by Ondřej Vejpustek · 830f0f81 · Oct 14, 2026 · 1 fileMessage 85 · StrongTriage 0Details
Commit message · Ondřej Vejpustek
feat(core): start a TROPIC01 model from `prodtest_emu.py`
The launcher now manages a model of its own on a free port, like `emu.py` does for the firmware emulator, so the Tropic prodtest commands work out of the box. The semantics match `emu.py`. `--no-tropic-emulator` switches to an externally managed model on the default port and `--tropic-model-port` overrides the port. A failed model start is reported and the emulator continues without the model, like `emu.py` does.
The model port is printed on startup and exported for a command run via `-c`.
[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
feat(core): add profile options to `prodtest_emu.py`
`-p`, `-t` and `-e` mirror `emu.py`. Unlike `emu.py`, the temporary profile stays the default. The launcher mostly wraps tests, which expect a clean state, and a persistent default in `/var/tmp` would collide with the firmware emulator storage. Use `-p` to keep the device state across restarts.
[no changelog]
95/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification
Lower-priorityfeat(core): port `prodtest_emu.py` to clickby Ondřej Vejpustek · 9a666c49 · Oct 14, 2026 · 1 fileMessage 57 · ThinTriage 0Details
Commit message · Ondřej Vejpustek
feat(core): port `prodtest_emu.py` to click
[no changelog]
57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Lower-priorityfeat(core): default `prodtest_emu.py` to the latest buildby Ondřej Vejpustek · d5569d08 · Oct 14, 2026 · 1 fileMessage 77 · AdequateTriage 0Details
Commit message · Ondřej Vejpustek
feat(core): default `prodtest_emu.py` to the latest build
The model is now optional and defaults to the `latest` build, like `emu.py`.
[no changelog]
77/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
Lower-priorityfeat(core): support running `prodtest_emu.py` without a commandby Ondřej Vejpustek · 9b9402db · Oct 14, 2026 · 2 filesMessage 85 · StrongTriage 0Details
Commit message · Ondřej Vejpustek
feat(core): support running `prodtest_emu.py` without a command
Without a command, the emulator now runs until interrupted, serving clients started separately (pytest, a console). The launcher waits on the emulator process like `emu.py` does. Ctrl+C stops the emulator itself (SDL turns `SIGINT` into a quit event) and the launcher propagates its exit code.
A command now requires `-c`, mirroring `emu.py`. A mistyped option is reported instead of silently becoming the command.
[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
Lower-prioritychore: update nixpkgsby Martin Milata · 555e7def · Oct 14, 2026 · 3 filesMessage 55 · ThinTriage 0Details
Commit message · Martin Milata
chore: update nixpkgs
Updated to nixpkgs-unstable 7fd4004d0511991fff3a0524856a9be09e28c5f0
55/100 · ThinMessage clarity
✓ Subject identifies a change✓ Uses a recognizable type or scope✓ Provides an explanatory body
Lower-priorityfeat(core): run `emu.py`'s TROPIC01 model on a free portby Ondřej Vejpustek · 2408c815 · Oct 14, 2026 · 1 fileMessage 95 · StrongTriage 0Details
Commit message · Ondřej Vejpustek
feat(core): run `emu.py`'s TROPIC01 model on a free port
The auto-started model is private to its emulator, so it has no reason to use a fixed port, which may already be taken by a leftover model or by the upgrade tests on 28992. `--no-tropic-emulator` keeps pointing the emulator at 28992 and the new `--tropic-model-port` option overrides either. The launcher prints `TROPIC_MODEL_PORT` and exports it for the `-c` command, unless the binary has no Tropic.
[no changelog]
95/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification
Lower-priorityfeat(python): run `TropicModel` on a free portby Ondřej Vejpustek · 8eaa3502 · Oct 14, 2026 · 3 filesMessage 80 · StrongTriage 0Details
Commit message · Ondřej Vejpustek
feat(python): run `TropicModel` on a free port
`TropicModel` now binds a free port when none is given. An auto-started model is private to its emulator, so it has no reason to use a fixed port, which may already be taken by another or a leftover model. `TropicModel.DEFAULT_PORT` remains the port where the emulators look for a manually started `model_server`.
The port is reserved by a socket held for the model's lifetime. Both the reservation and `model_server` bind with `SO_REUSEPORT`, so no other process can take the port in the meantime and parallel runs never pick the same port.
The `tropic_prodtest` fixture now relies on this instead of picking the port itself.
[no changelog]
80/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Lower-prioritybuild(core): don't silence linker warningsby Martin Milata · dfdb75dc · Oct 14, 2026 · 1 fileMessage 57 · ThinTriage 0Details
Commit message · Martin Milata
build(core): don't silence linker warnings
[no changelog]
57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Security candidatefeat(core): add base58 to the crypto crateby Lukas Bielesch · 80b2fc30 · Oct 14, 2026 · 2 filesMessage 57 · ThinInformational 15Details
Commit message · Lukas Bielesch
feat(core): add base58 to the crypto crate
[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
cryptography-sensitive path
AI analysis · Informational 15/100
This commit adds a brand-new Base58 encoding/decoding helper library in Rust for the Trezor firmware. It is purely additive code with no callers yet, and it includes tests. There is no indication it fixes or introduces a security vulnerability.
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
AI review queuedrefactor(core/embed): extract optiga metadata serialization into optiga_metadata.cby Ondřej Vejpustek · fd2dd466 · Oct 13, 2026 · 3 filesMessage 85 · StrongInformational 15Details
Commit message · Ondřej Vejpustek
refactor(core/embed): extract optiga metadata serialization into optiga_metadata.c
The metadata parsing functions and the `OPTIGA_META_*` constants are pure in-memory TLV serialization with no dependency on the transport or the chip state. Move them into a file of their own.
[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
second-pass: broader security terminology
AI analysis · Informational 15/100
This commit is a simple code cleanup: it moves existing metadata parsing and serialization functions from one source file to another without changing their behavior. There is no security fix or vulnerability introduced.
AI review queuedfix(xbuild): keep a separate .d file per outputby tychovrahe · c8fc50cf · Oct 12, 2026 · 1 fileMessage 80 · StrongInformational 17Details
Commit message · tychovrahe
fix(xbuild): keep a separate .d file per output
The compiler's dependency file was named by replacing the output's extension, so the object and the preprocessed (qstr collection) output of the same C source shared one .d file. The collection pass runs with NO_QSTR and never includes the generated qstr header, so its .d overwrote the object's and an incremental build no longer saw that header change: after adding a qstr, py/qstr.o was not rebuilt and every later qstr index was off by one. Append .d to the output name instead.
[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
Why it was queued
second-pass: broader security terminology
AI analysis · Informational 17/100
This is a build-system bug fix, not a security vulnerability. The change fixes how dependency files are named during compilation so that incremental builds correctly detect when generated header files change. Previously, two build stages could overwrite each other's dependency tracking files, causing stale object files and incorrect internal string indexes in the MicroPython runtime. There is no direct exploit path from this commit.
Security candidatefix(core): make the GFXMMU frame buffers writable by the T3W1 applicationby tychovrahe · bcc7f4d5 · Oct 12, 2026 · 13 filesMessage 97 · StrongLow 36Details
Commit message · tychovrahe
fix(core): make the GFXMMU frame buffers writable by the T3W1 application
On T3W1 every pixel the application wrote to the frame buffer with the CPU was silently lost; only DMA2D transfers reached it. The anti-aliased edges of rounded rectangles and circles, and the blur, were missing on hardware, which the dark theme hid.
The GFXMMU stayed privileged-only. Its privilege attribute lives in the GTZC TZSC, and the secure monitor locks the TZSC configuration (LCK, until reset) at the end of its init, so the non-secure kernel's attempt in display_set_unpriv_access() to make it unprivileged was refused. An unprivileged access to a privileged resource is a silent fail (RM0456 5.4.2): reads return zero, writes are ignored, no event is raised, so no fault ever pointed at it.
Configure the frame buffer access in tz_init() instead, on every layout: the secure monitor before it locks the TZSC, the secure kernel of the non-secmon layouts at its start. Unprivilege the physical frame buffers first, so that the GFXMMU's own bus transactions (the LTDC refresh; a securable peripheral that is a bus master issues transactions with its TZSC privilege, RM0456 3.6.3) stay legal, then the GFXMMU. The MPU keeps gating which buffer the application may touch. The regions come from the model's memory layout, so display_set_unpriv_access() and its driver implementations go away. tz_set_sram_unpriv() gets the same secure/ non-secure alias handling as tz_set_sram_unsecure() so the monitor can name the buffers by their non-secure addresses.
Move the TZSC privilege setters (SAES, TAMP, GFXMMU) out of the shared sys/trustzone module into sec/trustzone (sec/tz_periph.h), available to secure builds only, so a non-secure build that calls one fails to compile instead of failing silently at runtime. They now also refuse to run once the TZSC is locked, and the SAES and TAMP ones are not built into the secure monitor, which has no caller for them. Gate the secure AES unprivileged path, their other caller, on secure mode the same way; it is only reachable from secure-only code anyway.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
[no changelog]
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
credential or privilege statecryptography-sensitive path
AI analysis · Low 36/100
This commit fixes a display bug on the Trezor T3W1 hardware where the application could not directly write to the screen's frame buffer. Because of a TrustZone security-controller misconfiguration, CPU-drawn pixels were silently ignored, so only graphics copied by the DMA engine showed up. The patch moves the privilege setup to the correct early initialization stage and removes a broken runtime path that could not work once the controller was locked. It also hardens the code so future mistakes cause compile-time or runtime failures instead of silent no-ops.
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Lower-prioritytest(solana): update UI fixturesby Jakub Janků · f460a1c0 · Oct 11, 2026 · 1 fileMessage 67 · AdequateTriage 0Details
Commit message · Jakub Janků
test(solana): update UI fixtures
[no changelog]
67/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Mentions testing or verification! No meaningful explanatory body
Lower-priorityfix(core/sys): clean up IPC queues when task is killedby Yudistira Putra · 461e58e5 · Oct 11, 2026 · 1 fileMessage 85 · StrongTriage 0Details
Commit message · Yudistira Putra
fix(core/sys): clean up IPC queues when task is killed
When a task terminates abnormally or is terminated via systask_kill(), sysevents_notify_task_killed() dispatches notification to registered event sources. The IPC driver left task_killed unassigned in g_ipc_handle_vmt, leaving inbound receive queues in g_ipc_driver.queue pointing to unmapped or deallocated task memory. Any subsequent ipc_send() directed to that terminated task would see queue->ptr != NULL and write into stale memory.
Assign on_task_killed in g_ipc_handle_vmt to zero inbound receive queues registered by the killed task.
[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
Security candidatefeat(core/caesar): make more nav consistentby obrusvit · 042523a0 · Oct 10, 2026 · 5 filesMessage 57 · ThinInformational 15Details
Commit message · obrusvit
feat(core/caesar): make more nav consistent
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
cryptography-sensitive pathboot or update path
AI analysis · Informational 15/100
This commit is a user-interface cleanup for the Trezor hardware wallet's 'Caesar' layout. It removes unused button styles, unifies how on-screen menus and pagination work, and moves some confirmation screens from Rust into Python so they behave consistently with other models. There is no indication of a security bug or fix.
Security candidatefix(core/caesar): reset button state on attachby obrusvit · e4087c48 · Oct 10, 2026 · 2 filesMessage 57 · ThinLow 49Details
Commit message · obrusvit
fix(core/caesar): reset button state on attach
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
cryptography-sensitive path
AI analysis · Low 49/100
This commit fixes two UI state-reset bugs in the Trezor hardware wallet's 'Caesar' layout. When a screen layout is restarted (an 'Attach' event), the code now forgets any button presses that happened while the layout was inactive and clears a stuck 'Shift' key state. Without the fix, a previously pressed button or held Shift could be incorrectly remembered when returning to a screen, potentially causing an unintended action or confusing the user interface. The commit itself does not describe this as a security fix, and no independent researcher is credited.