Every captured commit receives deterministic security triage and a separate communication-quality score. Security candidates and broader second-pass signals receive full-patch Ollama analysis.
Message quality measures whether a commit identifies its scope, purpose, rationale, testing, and supporting references. It does not change the security-severity score.
This is a routine GitHub Actions workflow fix. It changes which Slack webhook secret is used for nightly test failure notifications and removes a now-unnecessary safety check. There is no security vulnerability in the change itself.
This commit only improves a test report for Trezor's clear-signing feature. It changes how skipped test cases are listed in a nightly summary, showing each skipped case's source file and calldata size instead of just counting them by reaso…
This commit only changes test scripts and documentation for the Trezor firmware clear-signing test suite. It makes the tests run more registry cases—specifically those where the developer definitions do not yet have a display format—so the…
This commit updates French and Portuguese translation strings in the Trezor firmware and refreshes the translation signature metadata. The changes are purely wording adjustments (for example, replacing abbreviations like 'nº' with the full…
This commit changes a code-coverage tracking map inside the Trezor firmware from a claimed capacity of 1,048,576 entries down to 65,536 entries. The commit message says the old capacity was never truly that large because the heapless libra…
No cryptographic or secret-handling code changedNo input parsing, deserialization, or memory allocator changesChange is in a debug/test instrumentation module (coverage)
This commit is a routine update of translated user-interface text strings for the Trezor hardware wallet. It adds new translations (for example, warnings about exporting public keys and Solana blind-signing prompts), updates existing wordi…
This commit only adds new test cases for Ethereum clear-signing array parsing. It does not change any production code, so it cannot introduce a new security vulnerability on its own. The tests verify that malformed arrays (out-of-bounds of…
test-only changeno production code modifiedadds defensive test coverage for ABI decoding edge cases
This commit hardens the Trezor firmware's task scheduler against fault-injection attacks. These attacks use physical techniques like voltage glitches or laser pulses to trick the device into executing code with higher privileges than inten…
Fault-injection hardening (FIH) explicitly mentioned in commit title and code commentsPrivilege-level transition split into multiple guarded stepsAdded runtime invariant check that only the kernel task may run privileged
This commit only removes an unused parameter called `is_dynamic` from test helper functions and from test data in three test files. It does not change any production firmware code, wallet behavior, or security logic. It is a cleanup of the…
This commit updates the data-format definitions used by Trezor devices for Ethereum 'clear signing' (showing human-readable details of smart-contract interactions). It adds support for more numeric types, new path-step structures, and extr…
Schema expansion increases attack surface for future clear-signing parser logic, but no new parser logic is present in this commit.Replacement of NotImplementedError with InvalidFormatDefinition is a defensive change that turns unimplemented paths into a handled error rather than a crash/DoS vector.New optional fields and deprecated old fields (is_dynamic, lookup_address) are backward-compatible changes.
This is a bug-fix patch in the Python Trezor client library. It changes how the software probes whether a connected device uses the older protocol v1. Previously, the probe tried to read and throw away leftover data, but that read could ac…
No security-relevant signal in commit message or diffFix is described as a connectivity/functional bug, not a vulnerabilityNo mention of CVE, researcher credit, or security advisory
This commit is a user-interface improvement, not a security fix. It changes the language-change confirmation prompt on Trezor devices so that it shows a human-readable language name (for example, 'French') instead of a raw code like 'fr-FR…
This commit updates Spanish and French translation strings in the Trezor firmware and refreshes the translation signature file. The changes are purely textual wording adjustments (for example, changing 'Mostrar palab.' to 'Mostrar palabras…
This commit hardens cryptographic code in Trezor firmware against two potential side-channel leaks. First, it simplifies how a secret condition value is checked inside an assert statement so the compiler produces only one branch instead of…
Side-channel hardening in constant-time cryptographic primitivesReplacement of double-evaluation volatile assert with single-branch assertElimination of secret-dependent memory access in elliptic-curve scalar multiplication
This commit adds a new nightly automated testing workflow for Ethereum 'clear signing' on Trezor hardware wallets. It does not change any wallet firmware code that users run; it only adds test scripts, CI configuration, documentation, and …
This commit is a routine code cleanup. It removes a small helper function called keccak_32 from a shared crypto utility file and places an equivalent helper directly inside the only test file that still uses it. There is no change to how t…
This commit removes support for a cryptocurrency called SmartCash from Trezor hardware wallets. It deletes coin definitions, support entries, and a custom cryptographic curve used only by SmartCash. There is no security vulnerability being…
No security-relevant signals detectedPure feature removal / code cleanup
This commit removes all support for the Groestlcoin cryptocurrency from Trezor firmware. It deletes coin definitions, the custom Groestl hash algorithm code, related address/transaction handling, and tests. There is no security vulnerabili…
No security-relevant change: pure feature removalNo new attack surface introducedNo vulnerability patched or created
This commit removes all support for the Tezos cryptocurrency from Trezor firmware, software libraries, and documentation. It is a feature-removal change, not a security fix or vulnerability patch. There is no indication in the commit that …
This update reduces the longest allowed screen-lock timeout on older Trezor devices from about 6 days down to 149 hours (just over 6 days). It makes the legacy firmware behave the same as newer Trezor firmware and prevents users from setti…
Bounds enforcement added for a configurable security-relevant timeoutAlignment of security policy between legacy and core firmware variantsTest coverage added for boundary values above and below new maximum
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Lower-priorityfeat(core): accept dev and prod root packet keys in non-prod buildsby cepetr · cab64caa · Nov 12, 2026 · 2 filesMessage 62 · AdequateTriage 0Details
Commit message · cepetr
feat(core): accept dev and prod root packet keys in non-prod 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
Lower-prioritytest: increase fixture name length limit a bitby Roman Zeyde · 01257980 · Nov 12, 2026 · 2 filesMessage 67 · AdequateTriage 0Details
Commit message · Roman Zeyde
test: increase fixture name length limit a bit
[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
✓ Descriptive subject✓ Uses a recognizable type or scope! No meaningful explanatory body
Security candidatefix(legacy): lower maximum auto-lock delay to 149 hoursby Ondřej Vejpustek · c108f275 · Nov 11, 2026 · 4 filesMessage 85 · StrongInformational 24Details
Commit message · Ondřej Vejpustek
fix(legacy): lower maximum auto-lock delay to 149 hours
This aligns the limit with the core firmware.
`config_getAutoLockDelayMs()` clamps the stored value, so a device that already stores a longer delay starts using the new maximum after the update. The stored value itself is not rewritten.
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
boot or update path
AI analysis · Informational 24/100
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 setting an extremely long auto-lock delay. Devices that already had a longer delay stored will silently use the new lower limit after updating, without changing the saved value.
✓ Descriptive subject✓ Uses a recognizable type or scope! No meaningful explanatory body
AI review queueddocs(core): drop unusued changelogby obrusvit · c3c045f1 · Nov 11, 2026 · 1 fileMessage 57 · ThinInformational 15Details
Commit message · obrusvit
docs(core): drop unusued changelog
[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 pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit simply deletes an unused changelog snippet file. It removes one line of text that described an Ethereum token-parsing improvement. No code, firmware behavior, or security fix is changed.
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Lower-prioritychore(deps): update rustix, libc, and linux-raw-sysby M1nd3r · c4076ebe · Nov 11, 2026 · 2 filesMessage 100 · StrongTriage 0Details
Commit message · M1nd3r
chore(deps): update rustix, libc, and linux-raw-sys
- Resolves rustix's unsoundness issue https://rustsec.org/advisories/RUSTSEC-2026-0486. - Updated rustix v1.1.3 -> v1.1.6. - Updated libc v0.2.177 -> v0.2.191. - Updated linux-raw-sys v0.11.0 -> v0.12.1. - Packages libc and linux-raw-sys need to be updated because of rustix's raised minimal requirements.
[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✓ Links an issue, advisory, or supporting reference
Lower-priorityrefactor(core): move root packet keys to separate fileby cepetr · 21d0e8e1 · Nov 11, 2026 · 2 filesMessage 62 · AdequateTriage 0Details
Commit message · cepetr
refactor(core): move root packet keys to separate file
[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-priorityci(core): don't error on GC leaks in HW testsby Roman Zeyde · 93127ae4 · Nov 11, 2026 · 3 filesMessage 67 · AdequateTriage 0Details
Commit message · Roman Zeyde
ci(core): don't error on GC leaks in HW tests
[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
Security candidatefeat(vendor): zero memory freed by the MicroPython GCby Martin Pastyřík · 2dae13d5 · Nov 11, 2026 · 3 filesMessage 97 · StrongLow 45Details
Commit message · Martin Pastyřík
feat(vendor): zero memory freed by the MicroPython GC
Bump MicroPython and enable `MICROPY_GC_CLEAR_ON_SWEEP` and `MICROPY_GC_CLEAR_ON_FREE`, so that memory freed by the GC sweep or released by `gc_free()` and `gc_realloc()` is zeroed.
[no changelog] Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
boot or update path
AI analysis · Low 45/100
This commit updates the MicroPython interpreter used in Trezor hardware wallets so that memory freed by the garbage collector is overwritten with zeros. The goal is to reduce the risk that leftover secrets (such as private keys or PIN data) remain in memory after they are no longer needed. It is a defensive hardening change, not a fix for a known exploitable bug.
✓ Descriptive subject✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
cryptography-sensitive pathsigning or wallet path
AI analysis · Informational 15/100
This commit is a routine regeneration of font files used by the Trezor hardware wallet's user interface. It updates glyph bitmaps, spacing values, and comments across many font source files, but does not change any executable logic, cryptographic code, or security-sensitive behavior. There is no indication this is a security fix or introduces a vulnerability.
Lower-priorityfix(core): (un)register usb handles in usb_start/stopby cepetr · 884c69a1 · Nov 11, 2026 · 5 filesMessage 62 · AdequateTriage 0Details
Commit message · cepetr
fix(core): (un)register usb handles in usb_start/stop
[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-prioritystyle: ignore files in .venv directoriesby M1nd3r · 95a7289c · Nov 10, 2026 · 3 filesMessage 45 · ThinTriage 0Details
Commit message · M1nd3r
style: ignore files in .venv directories
[no changelog]
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Co-authored-by: onvej-sl <38104856+onvej-sl@users.noreply.github.com> Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
95/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✓ Names security-relevant behavior explicitly
Why it was queued
access controlauthentication path
AI analysis · Informational 15/100
This commit only adds a new Python unit-test file for Trezor's device-authentication logic. It does not change any production code, cryptographic checks, or firmware behavior. There is no security vulnerability introduced or fixed here.
Security candidaterefactor(python): add `signature_unsafe_expanded` into `_ed25519`by M1nd3r · 0b6f470b · Nov 10, 2026 · 1 fileMessage 85 · StrongInformational 18Details
Commit message · M1nd3r
refactor(python): add `signature_unsafe_expanded` into `_ed25519`
[no changelog]
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Co-authored-by: onvej-sl <38104856+onvej-sl@users.noreply.github.com>
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
signing boundary
AI analysis · Informational 18/100
This commit adds a new helper function for creating Ed25519 digital signatures when the secret key has already been expanded into its internal components. It is explicitly marked as unsafe and for testing only, and it does not change any existing security behavior. The change appears to be a code refactor to support a specific key-storage format used by another project (Tropic).
Lower-priorityci: use dollar syntax for local 'uses:'by Martin Milata · f7616d33 · Nov 9, 2026 · 16 filesMessage 80 · StrongTriage 0Details
Commit message · Martin Milata
ci: use dollar syntax for local 'uses:'
See also: https://docs.zizmor.sh/audits/#self-repository
80/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Lower-prioritychore: add freetype and fonttools to uv envby obrusvit · 1e66ccc6 · Nov 9, 2026 · 2 filesMessage 57 · ThinTriage 0Details
Commit message · obrusvit
chore: add freetype and fonttools to uv env
[no changelog]
57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body