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 candidatefix(core): show RSOD after a fault in an IRQ handlerby cepetr · 46f736e6 · Nov 5, 2026 · 6 filesMessage 62 · AdequateLow 34Details
Commit message · cepetr
fix(core): show RSOD after a fault in an IRQ handler
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 · Low 34/100
This update changes how Trezor hardware wallets recover when something goes wrong inside an interrupt handler. Previously, the device could freeze silently instead of showing the red error screen (RSOD). Now it unwinds nested interrupt handlers and shows the error screen. The change is a robustness improvement, not a direct fix for an exploitable vulnerability, but the freeze behavior could have been used to make a device hang or confuse a user.
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.
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.
(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.
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.
Security candidatechore(translations): replace backup__title_backup_wallet with reset__recovery_wallet_backup_titleby Michal Kazda · f7e36aa3 · Nov 2, 2026 · 5 filesMessage 77 · AdequateInformational 15Details
Commit message · Michal Kazda
chore(translations): replace backup__title_backup_wallet with reset__recovery_wallet_backup_title - simplifies and unifies the terminology - makes backup__title_backup_wallet obsolete, so it is removed [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
Why it was queued
cryptography-sensitive pathboot or update path
AI analysis · Informational 15/100
This commit is a routine user-interface cleanup: it swaps one on-screen title ('Back up wallet') for another existing title ('Recovery wallet backup') and removes the old translation key. There is no security change, no bug fix, and no behavior change beyond the visible label text.
Security candidatechore(translations): replace reset__check_backup_title with recovery__title_dry_runby Michal Kazda · 722778d7 · Nov 2, 2026 · 6 filesMessage 77 · AdequateInformational 15Details
Commit message · Michal Kazda
chore(translations): replace reset__check_backup_title with recovery__title_dry_run - simplifies and unifies the terminology - makes reset__check_backup_title obsolete, so it is removed [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
Why it was queued
cryptography-sensitive pathboot or update path
AI analysis · Informational 15/100
This commit is a routine cleanup of on-screen text labels. It replaces one internal label name (reset__check_backup_title) with another (recovery__title_dry_run) that already exists, and removes the old label from translation files. The actual user-facing text shown on the device does not change: both labels display 'Check backup' on the affected device layouts. There is no security-relevant code change.
Security candidatestyle: remove quotes from type annotationsby M1nd3r · d8ab1ed0 · Oct 30, 2026 · 45 filesMessage 45 · ThinInformational 15Details
Commit message · M1nd3r
style: remove quotes from type annotations
[no changelog]
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
boot or update pathauthentication pathparser or protocol path
AI analysis · Informational 15/100
This commit is a pure code-style cleanup. It removes unnecessary quotation marks around type annotations (for example, changing 'Session' to Session) across many Python files. These changes do not alter what the code does, how it handles data, or how it protects secrets. There is no security impact.
Security candidatestyle: use PEP 604 syntax where possibleby M1nd3r · a68d4ee0 · Oct 30, 2026 · 38 filesMessage 68 · AdequateInformational 15Details
Commit message · M1nd3r
style: use PEP 604 syntax where possible
- Replaced `Optional[X]` annotation by PEP 604 syntax `X | None` where possible. - Replaced `Union[X, Y]` annotation by PEP 604 syntax `X | Y` where possible. - Added `from __future__ import annotations` where necessary.
[no changelog]
68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
cryptography-sensitive pathboot or update pathauthentication path
AI analysis · Informational 15/100
This is a pure code-style cleanup. It replaces older Python type annotations like `Optional[X]` and `Union[X, Y]` with the newer `X | None` and `X | Y` syntax, and adds `from __future__ import annotations` where needed so the new syntax works on Python 3.9. No behavior of the code changes, and there is no security relevance.
Security candidatechore(core): drop MetaMask EIP-7702 supportby Roman Zeyde · 1528e6ea · Oct 30, 2026 · 7 filesMessage 57 · ThinInformational 18Details
Commit message · Roman Zeyde
chore(core): drop MetaMask EIP-7702 support
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 pathauthentication path
AI analysis · Informational 18/100
This commit removes built-in support for MetaMask's EIP-7702 smart-contract wallet delegation address from Trezor firmware. After this change, Trezor will no longer recognize MetaMask's specific delegation contract as a trusted/known delegate, so any EIP-7702 authorization using that MetaMask address will be rejected with an 'Unknown EIP-7702 delegate address' error instead of being signed. This is a deliberate feature removal, not a code vulnerability fix. It reduces the attack surface by no longer blessing a third-party contract as a known delegate, but it does not patch an exploitable bug.
- This option significantly decreases the stack required for ML-DSA operations, with acceptable slowdown.
[no changelog]
70/100 · AdequateMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
cryptography-sensitive path
AI analysis · Informational 15/100
This commit turns on a build-time option called MLD_CONFIG_REDUCE_RAM for the ML-DSA cryptographic code used in Trezor firmware. The stated purpose is to lower the amount of stack memory consumed during ML-DSA (post-quantum digital signature) operations, accepting a small performance slowdown. There is no indication in the commit that this fixes a security bug, vulnerability, or exploit. It appears to be a routine memory-optimization change.
It was added in 52d34955e7 to our code, but never used in C code. It was introduced to upstream by https://github.com/bitcoin-core/secp256k1/pull/366/changes/001f1763c76c2f5599cdb8713692c618191226fe
[no changelog]
88/100 · StrongMessage clarity
✓ 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
boot or update path
AI analysis · Informational 15/100
This commit removes an unused compiler flag from the build system for the older Trezor firmware. The flag was defined but never referenced anywhere in the source code, so removing it has no functional or security effect.
build(core+legacy+crypto): remove unused `ENABLE_MODULE_GENERATOR` flag
It is part of the https://github.com/BlockstreamResearch/secp256k1-zkp fork (added in 52d34955e7). After we moved to https://github.com/bitcoin-core/secp256k1 (in 67f3af619a) it's no longer used.
[no changelog]
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
cryptography-sensitive pathboot or update path
AI analysis · Informational 15/100
This commit removes an unused compiler flag called ENABLE_MODULE_GENERATOR from three build files. The flag was left over from an older version of a cryptographic library and no longer has any effect after Trezor switched to a different library version. There is no functional code change and no security risk.
build(core+legacy+crypto): remove deprecated `ECMULT_GEN_PREC_BITS` flag
It has been removed in https://github.com/bitcoin-core/secp256k1/pull/1058 and released in https://github.com/bitcoin-core/secp256k1/blob/master/CHANGELOG.md#050---2024-05-06.
[no changelog]
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
cryptography-sensitive pathboot or update path
AI analysis · Informational 18/100
This commit removes an obsolete compiler flag called ECMULT_GEN_PREC_BITS from the build scripts for Trezor's cryptographic code. The upstream secp256k1 library deleted this flag in version 0.5.0, so Trezor is simply cleaning up its build configuration to match. There is no indication this change fixes an active security vulnerability; it is routine build maintenance.
Security candidatedocs(core): changelog for bootloader 2.1.18by obrusvit · 621d7978 · Oct 29, 2026 · 2 filesMessage 72 · AdequateInformational 15Details
Commit message · obrusvit
docs(core): changelog for bootloader 2.1.18
[no changelog]
(cherry picked from commit e2b710f84783630ab790993cd9078ec5ee1d3c7c)
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 15/100
This commit is purely a documentation update. It moves a bootloader user-interface change note from a pending changelog fragment into the official bootloader changelog for version 2.1.18. There are no code changes and no security implications.
Security candidatedocs(legacy): changelog for 1.14.3by obrusvit · ebcec1b8 · Oct 29, 2026 · 4 filesMessage 72 · AdequateInformational 15Details
Commit message · obrusvit
docs(legacy): changelog for 1.14.3
[no changelog]
(cherry picked from commit a6c65360a4c328c4fcc75294cfec46132e8b1eb7)
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
boot or update path
AI analysis · Informational 15/100
This commit is purely a documentation update: it moves three changelog entries from draft files into the official CHANGELOG.md for the Trezor legacy firmware version 1.14.3. No code, firmware logic, or security behavior is changed. The listed security items describe changes that were already made in earlier commits and are only being summarized here.
Security candidatetest(python): add generation of test attestation certificatesby M1nd3r · a135aa85 · Oct 29, 2026 · 8 filesMessage 87 · StrongInformational 15Details
Commit message · M1nd3r
test(python): add generation of test attestation certificates
- Also, generate test certificates for existing models.
[no changelog]
87/100 · StrongMessage clarity
✓ Specific, 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
update trust
AI analysis · Informational 15/100
This commit only adds test infrastructure: a script that generates fake attestation certificates for Trezor emulators and copies them into a test directory. The certificates use publicly documented hardcoded debug keys and are used by automated tests. There is no change to production firmware, real device security, or user-facing behavior.
Security candidatefix(core): make CLI autocomplete order-independentby tychovrahe · a87f044c · Oct 29, 2026 · 1 fileMessage 85 · StrongInformational 21Details
Commit message · tychovrahe
fix(core): make CLI autocomplete order-independent
- cli_autocomplete() used '\0' both as "no match yet" and as "this command ends here", so whether Tab stopped at a full name such as "reboot" or ran on to "reboot-to-bootloader" depended on the order of the command array. - Track the first match separately. Seen in the emulator, whose constructor registration keeps source order; on hardware GCC emits the section in reverse, which happened to hide it.
[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
Why it was queued
update trust
AI analysis · Informational 21/100
This is a minor bug fix in the command-line interface (CLI) autocomplete feature used inside Trezor devices. When a user typed a partial command like 'reboot' and pressed Tab, the autocomplete behavior could differ depending on the internal order of the command list. In some builds (real hardware) it happened to work; in others (emulator) it could skip past a complete command name and suggest a longer one instead. The fix separates two meanings of the special '\0' character so autocomplete behaves consistently regardless of command order. There is no direct evidence this is a security vulnerability.
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
credential or privilege state
AI analysis · Informational 15/100
This commit adds extra diagnostic commands to a hardware CI test script. It collects more information about USB ports and PCI devices when a Trezor hardware test fails, to help engineers debug permission or connectivity issues. There is no change to the firmware, wallet logic, cryptography, or any user-facing security behavior.
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
authentication path
AI analysis · Low 43/100
This commit tightens how the Trezor Python library checks whether a connected hardware wallet is genuine. It adds stricter rules: certificates must now include a device model name, revoked and allowed keys cannot be mixed, signature types must match the chip that produced them, and older firmware that lacks new MCU-style proof support is rejected with a clear error. These are defensive hardening changes rather than a fix for a known active attack.
Security candidatefix(core/caesar): use Marquee in HS notifby obrusvit · b3fb1bde · Oct 27, 2026 · 2 filesMessage 57 · ThinInformational 18Details
Commit message · obrusvit
fix(core/caesar): use Marquee in HS notif
[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 18/100
This is a user-interface polish change for the Trezor hardware wallet's Caesar homescreen layout. It makes long notification messages scroll smoothly using a 'Marquee' component instead of being cut off or overlapping warning icons. There is no security-relevant behavior change; it is purely about how text is displayed on screen.