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-priorityfix(core): validate the `--port` range in the emulator launchersby Ondřej Vejpustek · 18c79c4e · Nov 4, 2026 · 3 filesMessage 85 · StrongTriage 8Details
Commit message · Ondřej Vejpustek
fix(core): validate the `--port` range in the emulator launchers
An out-of-range port silently wraps modulo 65536 in the firmware and the launcher times out. The upper bound leaves room for the interface offsets.
[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
tests(clear_signing): 1inch ethunoswap unknown token as native
[no changelog]
(cherry picked from commit 1f18d6f93dd8886afc15df25d3c8664206c0a07b)
75/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Mentions testing or verification
Why it was queued
signing boundarysigning or wallet path
AI analysis · Informational 15/100
This commit only adds new test fixtures and a test case for the Trezor hardware wallet's Ethereum 'clear signing' feature. It tells the device how to display a specific 1inch swap function (ethUnoswap) on screen so users can verify what they are signing. There is no change to firmware code, no bug fix, and no security patch.
Security candidaterefactor(core): rename N1W1 to K1N1by Martin Milata · 16e1ade6 · Nov 4, 2026 · 54 filesMessage 57 · ThinInformational 15Details
Commit message · Martin Milata
refactor(core): rename N1W1 to K1N1
[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
boot or update path
AI analysis · Informational 15/100
This commit is a large but purely cosmetic rename: every occurrence of the internal feature/capability name 'N1W1' is changed to 'K1N1' across build files, protocol definitions, generated code, translations, tests, and documentation. No security behavior is altered.
- Report firmware, kernel, secmon and bootloader memory usage from the existing core_firmware builds (universal and btconly firmware) - Runs on PRs and pushes to main; fork PRs upload without the API key - Post the PR comment from a workflow_run job so it works for forks - The report step never fails the firmware build - Exclude the MicroPython heap from the firmware usage - Leave ALIGN padding out of section sizes (exclude_alignment) - Add a manually dispatched onboard workflow that backfills reports for the targets in .github/membrowse-targets.json
[no changelog]
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
update trustdocumentation-only discount
AI analysis · Informational 15/100
This commit adds a new CI feature that uploads firmware memory-usage reports to a third-party service called MemBrowse. It does not change any firmware code, cryptographic logic, or user-facing behavior. It only affects GitHub Actions automation and is purely informational for developers reviewing pull requests.
Lower-prioritychore(core): update fixturesby Michal Kazda · 28bb10a2 · Nov 3, 2026 · 1 fileMessage 47 · ThinTriage 0Details
Commit message · Michal Kazda
chore(core): update fixtures [no changelog]
47/100 · ThinMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope! No meaningful explanatory body
Lower-prioritychore(core): update fixturesby Michal Kazda · a7240950 · Nov 3, 2026 · 1 fileMessage 47 · ThinTriage 0Details
Commit message · Michal Kazda
chore(core): update fixtures [no changelog]
47/100 · ThinMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope! No meaningful explanatory body
Lower-priorityci: notify Slack on nightly HW test failureby Michal Kazda · 05db0ac6 · Nov 3, 2026 · 1 fileMessage 82 · StrongTriage 0Details
Commit message · Michal Kazda
ci: notify Slack on nightly HW test failure
- post to Slack when a scheduled hardware test run fails - manual runs and forks don't notify
[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
documentation-only discount
Lower-prioritychore(tools): update Dockerfile for oss-scannerby obrusvit · 6cd69cbc · Nov 3, 2026 · 1 fileMessage 57 · ThinTriage 0Details
Commit message · obrusvit
chore(tools): update Dockerfile for oss-scanner
[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 candidatefix(clear_signing): show unknown tokens as UKWN even when native addr provided.by PrisionMike · 21dffd0f · Nov 3, 2026 · 3 filesMessage 77 · AdequateModerate 64Details
Commit message · PrisionMike
fix(clear_signing): show unknown tokens as UKWN even when native addr provided.
(cherry picked from commit 190c527d556a97d8aeaa46f83089c3feff7351b4)
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
signing boundarysigning or wallet path
AI analysis · Moderate 64/100
This update fixes how Trezor hardware wallets display Ethereum token amounts when a transaction descriptor does not specify which token is involved. Previously, the device rejected such descriptors outright. The fix makes the device show the raw amount with an 'unknown token' label (UNKN) instead of either failing or accidentally treating it as the network's native currency (like ETH). This prevents a malicious or sloppy descriptor from tricking the user into thinking they are sending a known token or native currency when the device actually cannot identify the token contract.
Lower-priorityfeat(core): add a port option to `prodtest_emu.py`by Ondřej Vejpustek · e4521ae6 · Nov 3, 2026 · 1 fileMessage 85 · StrongTriage 0Details
Commit message · Ondřej Vejpustek
feat(core): add a port option to `prodtest_emu.py`
Expose the existing `port` parameter of `get_prodtest_emulator()` as `-P`/`--port` with the `TREZOR_UDP_PORT` fallback, mirroring `emu.py`. Useful for running multiple emulators in parallel.
[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(core): update fixturesby Michal Kazda · f7e39598 · Nov 3, 2026 · 1 fileMessage 47 · ThinTriage 0Details
Commit message · Michal Kazda
chore(core): update fixtures [no changelog]
47/100 · ThinMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope! No meaningful explanatory body
Lower-priorityfix(core): fail when `-c` is used without a commandby Ondřej Vejpustek · ccb29249 · Nov 3, 2026 · 1 fileMessage 77 · AdequateTriage 0Details
Commit message · Ondřej Vejpustek
fix(core): fail when `-c` is used without a command
[no changelog]
Co-authored-by: Petr Sedláček <63123927+M1nd3r@users.noreply.github.com>
77/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
Lower-priorityfix(core): make the T3T2 secure monitor build againby tychovrahe · 70a28ac9 · Nov 3, 2026 · 1 fileMessage 85 · StrongTriage 0Details
Commit message · tychovrahe
fix(core): make the T3T2 secure monitor build again
- tzsc_ensure_unlocked() has callers only in some builds: the secure monitor compiles out the SAES/TAMP setters and only the GFXMMU parts (U5A9/U5G9) have the GFXMMU one, so a U58 secure monitor ended up with an unused static function and -Werror=unused-function - mark it __attribute__((unused)), the convention secret.c and ft3168.c already use for build-dependent helpers
[no changelog]
Co-Authored-By: Claude Fable 5.1 <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): suspend Optiga from the kernel without an RTCby tychovrahe · d0faabb8 · Nov 3, 2026 · 1 fileMessage 85 · StrongTriage 0Details
Commit message · tychovrahe
fix(core): suspend Optiga from the kernel without an RTC
- the non-RTC branch of optiga_suspend() called optiga_deinit(), which is secure-only and has no secure-monitor call, so a secmon-layout model with Optiga but no RTC (T2B1, T3B1, T3T1, T3T2) could not link its kernel once the suspend feature was enabled - call optiga_close_channel() and optiga_power_down() instead, which is what optiga_deinit() does and which the kernel already reaches through the secure monitor on the RTC path
[no changelog]
Co-Authored-By: Claude Fable 5.1 <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
(cherry picked from commit f001779a2bc816608d913bca2aa7f85b7b797bf2)
72/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
Why it was queued
update trustboot or update path
AI analysis · Informational 0/100
This commit updates the bootloader binary files and their recorded hash values for two Trezor hardware wallet models (T2B1 and T3B1). The change is described as a routine chore with no changelog entry. There is no information in the commit message or diff indicating what changed inside the bootloader, why it was updated, or whether it fixes any security issue.
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
cryptography-sensitive pathseed or entropy pathsigning or wallet pathboot or update path
AI analysis · Informational 15/100
This commit is purely a code-style cleanup. It turns on two new lint checks in the project's Python linter (ruff) and renames single-letter variables like 'l' to clearer names like 'length', 'line', 'left', etc. No program behavior is changed, and there are no security fixes.
Security candidatechore(translations): adding the missing line in the wallet created screen of Caesarby Michal Kazda · 20269fc7 · Nov 2, 2026 · 8 filesMessage 95 · StrongInformational 15Details
Commit message · Michal Kazda
chore(translations): adding the missing line in the wallet created screen of Caesar - without changing the other languages the some tests would break so it is done in this commit directly instead of Crowdin for later processing [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
Why it was queued
cryptography-sensitive pathsigning or wallet pathboot or update path
AI analysis · Informational 15/100
This commit is a routine translation and user-interface text update. It adds a missing line break in one on-screen message for the 'Caesar' layout and adjusts wording in several language files so the text fits correctly. There is no security issue here.
Lower-prioritychore(core): changed token contract address to contract addressby Michal Kazda · 6734d6c6 · Nov 2, 2026 · 3 filesMessage 62 · AdequateTriage 0Details
Commit message · Michal Kazda
chore(core): changed token contract address to contract address - plus generated files [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(core): generate filesby Michal Kazda · 2acb9859 · Nov 2, 2026 · 5 filesMessage 47 · ThinInformational 15Details
Commit message · Michal Kazda
chore(core): generate files [no changelog]
47/100 · ThinMessage clarity
✓ Descriptive subject✓ 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 is a routine regeneration of translation files. It adds one new menu string ('Turn off'), updates several punctuation marks in user-facing text, and refreshes the cryptographic signature that protects the translation bundle. There is no code behavior change and no security issue visible in the diff.
Security candidatechore(translations): add menu__turn_off stringby Michal Kazda · 881eb139 · Nov 2, 2026 · 3 filesMessage 80 · StrongInformational 15Details
Commit message · Michal Kazda
chore(translations): add menu__turn_off string - in ES translation the same string cannot be used as the menu item for turning a device off and for disabling features [no changelog]
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
boot or update path
AI analysis · Informational 15/100
This commit is a routine translation/UI cleanup. It adds a new text label 'menu__turn_off' so that the Spanish translation can use different wording for the device power-off menu item versus the wording used for disabling features. There is no security-relevant change to device behavior, cryptography, or access controls.
Lower-prioritychore(translations): various improvements to English copyby Michal Kazda · 927dd74b · Nov 2, 2026 · 1 fileMessage 62 · AdequateTriage 0Details
Commit message · Michal Kazda
chore(translations): various improvements to English copy [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
translation-only discount
Lower-prioritychore(core/ward): use AnyBytes for key/value parameter typesby Roman Zeyde · 5a4c7ee8 · Nov 2, 2026 · 1 fileMessage 77 · AdequateTriage 0Details
Commit message · Roman Zeyde
chore(core/ward): use AnyBytes for key/value parameter types
It will allow using `bytearray` directly without casting it to `bytes`.
[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-prioritychore(core): generate filesby Michal Kazda · 9d81dde2 · Nov 2, 2026 · 3 filesMessage 47 · ThinTriage 0Details
Commit message · Michal Kazda
chore(core): generate files [no changelog]
47/100 · ThinMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope! No meaningful explanatory body
Lower-prioritychore(translations): reworded `Check wallet backup` title to `Wallet backup check`by Michal Kazda · 00f70095 · Nov 2, 2026 · 1 fileMessage 62 · AdequateTriage 0Details
Commit message · Michal Kazda
chore(translations): reworded `Check wallet backup` title to `Wallet backup check` [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