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.
AI review queuedtest(core): drop `test_descriptor_all_formatters` unit testby Roman Zeyde · 3704e769 · Jul 1, 2026 · 1 fileMessage 87 · StrongInformational 15Details
Commit message · Roman Zeyde
test(core): drop `test_descriptor_all_formatters` unit test
It should be covered by device tests.
[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
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit simply removes a single unit test from the Trezor firmware test suite. The test covered Ethereum 'clear signing' formatting logic, and the commit message says it is being dropped because it should be covered by device tests instead. No production code was changed, so this does not introduce or fix a security vulnerability by itself.
✓ 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 pathtranslation-only discountsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit is a routine synchronization of translated user-interface text strings for the Trezor hardware wallet firmware. It updates wording in Czech, German, Spanish, French, and Portuguese translation files, plus the translation signature metadata. There are no code, logic, cryptographic, or security behavior changes.
AI review queuedchore(tron): scaffolding for `WithdrawBalanceContract`by PrisionMike · 2b93024e · Jun 29, 2026 · 18 filesMessage 62 · AdequateInformational 15Details
Commit message · PrisionMike
chore(tron): scaffolding for `WithdrawBalanceContract`
[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
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit adds support for a new Tron blockchain operation called 'WithdrawBalanceContract' (claiming voting rewards). It is a feature addition: new message types, generated code, translations, and a test fixture. There is no indication of a security bug or vulnerability fix in the diff.
AI review queuedrefactor(core): close other workflows when starting `ProgressLayout`by Roman Zeyde · ada6a447 · Jun 26, 2026 · 4 filesMessage 62 · AdequateLow 26Details
Commit message · Roman Zeyde
refactor(core): close other workflows when starting `ProgressLayout`
[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
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 26/100
This commit moves the responsibility for closing other on-screen workflows into the ProgressLayout class itself, rather than having each individual feature call a separate 'close others' function. It is a code cleanup (refactor) and does not appear to introduce or fix a security vulnerability. The change makes UI behavior more consistent but does not change what the device ultimately allows.
AI review queuedrefactor(core/rust): implement io::Errorby matejcik · c6fa8ca2 · Jun 26, 2026 · 2 filesMessage 72 · AdequateInformational 12Details
Commit message · matejcik
refactor(core/rust): implement io::Error
to stop relying on micropython's Error type
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
parser or protocol pathsecond-pass: security-sensitive path
AI analysis · Informational 12/100
This is a small internal code cleanup in the Trezor firmware's Rust code. It introduces a dedicated Rust error type for input/output operations so the code no longer borrows MicroPython's error type directly. The behavior appears unchanged: the same end-of-buffer condition still returns an equivalent EOF error, and the bytes-type check still returns the same type error. There is no indication this fixes or introduces a security vulnerability.
AI review queuedrefactor(core/rust): move micropython's Error to micropython moduleby matejcik · 58b4aea4 · Jun 26, 2026 · 22 filesMessage 77 · AdequateInformational 15Details
Commit message · matejcik
refactor(core/rust): move micropython's Error to micropython module
in preparation of micropython spin-off to a separate crate, and error handling rework in the trezor_lib
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
parser or protocol pathsecond-pass: unusually broad changesecond-pass: security-sensitive path
AI analysis · Informational 15/100
This is a routine internal code reorganization in the Trezor firmware's Rust code. It moves the existing `Error` type from a top-level module into the `micropython` module and updates import paths accordingly. There is no change to user-facing behavior, no fix for a vulnerability, and no new security-sensitive logic.
AI review queuedfix(solana): show the program id for unknown programs in the tx details view instead of a generic "Unsupported program" label.by Sammy Harris · 7ea33494 · Jun 25, 2026 · 4 filesMessage 77 · AdequateInformational 20Details
Commit message · Sammy Harris
fix(solana): show the program id for unknown programs in the tx details view instead of a generic "Unsupported program" label.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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 or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 20/100
This change improves the Trezor hardware wallet's Solana transaction confirmation screen. When a transaction contains an unknown program (smart contract), the device now shows the actual program ID instead of a generic 'Unsupported program' label. This helps users make a more informed decision before approving a transaction, but it is a user-interface improvement rather than a fix for a code vulnerability.
AI review queuedfix(solana): use template for indexed cosigners [no changelog]by Michal Kazda · 4c25a6fd · Jun 21, 2026 · 7 filesMessage 77 · AdequateInformational 16Details
Commit message · Michal Kazda
fix(solana): use template for indexed cosigners [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
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 16/100
This commit fixes a minor user-interface wording issue in Trezor's Solana app. Previously, the device built the cosigner label by manually combining the word 'Cosigner' with a number, which could cause problems for translations. Now it uses a proper translation template 'Cosigner {0}'. There is no direct evidence this is a security vulnerability, but inconsistent or untranslatable labels could theoretically contribute to user confusion when reviewing multisig signers.
AI review queuedchore(translations): upload signed translationsby PrisionMike · 67cc06e2 · Jun 18, 2026 · 1 fileMessage 72 · AdequateInformational 15Details
Commit message · PrisionMike
chore(translations): upload signed translations
(cherry picked from commit 7d7eb296412dc993f78976fe7f41dcf80d50019b)
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
signing or wallet pathtranslation-only discountsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit adds a new digital signature entry to a JSON file that records approved translation packages for Trezor hardware wallets. It is a routine administrative update with no code changes and no apparent security relevance.
AI review queuedchore: tweak hardcoded LiFi definitionsby Ioan Bizău · 9ad5fa49 · Jun 15, 2026 · 1 fileMessage 57 · ThinInformational 19Details
Commit message · Ioan Bizău
chore: tweak hardcoded LiFi definitions
[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 19/100
This is a small maintenance update to Trezor's Ethereum clear-signing definitions for the LiFi cross-chain swap service. It adds alternative contract addresses for LiFi on four blockchains where the service uses a different address than usual, and tweaks a few on-screen labels (for example changing 'Recipient' to 'Receiver' and adjusting capitalization). There is no indication of a security vulnerability being fixed.
AI review queuedchore: add hardcoded 1inch definitionsby Ioan Bizău · 730cbd94 · Jun 15, 2026 · 2 filesMessage 80 · StrongInformational 19Details
Commit message · Ioan Bizău
chore: add hardcoded 1inch definitions
This reverts commit dc1f3a1b4d81900ab0a406617f5efb7e200df14e but adds more definitions that what was there.
[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
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 19/100
This commit adds human-readable display definitions for 1inch decentralized-exchange swap transactions on Trezor hardware wallets. It tells the wallet how to decode and label 1inch swap parameters (amounts, beneficiary, last pool) so users can verify what they are signing on the device screen. The change is purely a data/configuration addition plus matching tests; it does not alter cryptographic code, transaction validation, or signing logic. There is no indication in the commit that this fixes a security vulnerability.
AI review queuedfeat(tron): add (Un)DelegateResourceContract support.by PrisionMike · 55000b59 · Jun 12, 2026 · 8 filesMessage 77 · AdequateInformational 12Details
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 12/100
This commit adds support for two new Tron blockchain transaction types—delegating and undelegating bandwidth or energy resources—on Trezor hardware wallets. It is a feature addition, not a security fix. The code adds user confirmation screens, input validation, and test fixtures, with no obvious signs of a vulnerability being patched.
AI review queuedfix(python): skip stale protocol v1 responsesby Roman Zeyde · 1edb54ac · Jun 12, 2026 · 4 filesMessage 57 · ThinLow 47Details
Commit message · Roman Zeyde
fix(python): skip stale protocol v1 responses
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
parser or protocol pathsecond-pass: security-sensitive path
AI analysis · Low 47/100
This update fixes a bug in the Trezor Python library where reconnecting to a Trezor device could fail if an old, unread response was still waiting in the communication channel. The fix makes the library clear out up to 10 stale responses before it checks whether the device speaks the older protocol v1. A new test simulates a host disconnect mid-operation and verifies that a new client can reconnect successfully.
AI review queuedchore(tron): boilerplate support for (un)delegate resource instructions.by PrisionMike · ef510943 · Jun 12, 2026 · 23 filesMessage 77 · AdequateInformational 15Details
Commit message · PrisionMike
chore(tron): boilerplate support for (un)delegate resource instructions.
- Benign string refactorings with eos. [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
signing or wallet pathsecond-pass: unusually broad changesecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit adds the data structures and translations needed to support two new Tron blockchain operations—delegating and undelegating staked resources—but does not include the actual code that would handle or sign those operations. It also moves a few shared user-interface labels from the EOS section to a common 'words' section. There is no security issue visible in this patch.
AI review queuedchore(rust): remove unneeded `script_type` from Trezor::get_public_key()by Roman Zeyde · a87197ed · Jun 8, 2026 · 4 filesMessage 62 · AdequateInformational 18Details
Commit message · Roman Zeyde
chore(rust): remove unneeded `script_type` from Trezor::get_public_key()
[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
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 18/100
This is a small cleanup change in the Rust Trezor client library. It removes an unused `script_type` parameter from the `get_public_key()` function and its callers. The parameter was being set in the request to the Trezor device, but the device does not actually need or use it for this operation. There is no security vulnerability here—just code simplification.
AI review queuedrefactor(core/build): stop treating emulator as a separate HW board, instead use it to emulate the selected boardby tychovrahe · 566dc7db · Jun 8, 2026 · 22 filesMessage 62 · AdequateInformational 15Details
Commit message · tychovrahe
refactor(core/build): stop treating emulator as a separate HW board, instead use it to emulate the selected board
[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
second-pass: unusually broad change
AI analysis · Informational 15/100
This commit is a build-system cleanup. It removes separate 'emulator board' configuration files and instead makes the emulator reuse the real hardware board's settings, only swapping in a special emulator header and the Unix display/touch drivers. There is no user-facing change or security fix visible in the diff.
AI review queuedfeat(core/build): add board and target configuration filesby tychovrahe · 9bf8a898 · Jun 8, 2026 · 23 filesMessage 62 · AdequateInformational 15Details
Commit message · tychovrahe
feat(core/build): add board and target configuration 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
Why it was queued
second-pass: unusually broad change
AI analysis · Informational 15/100
This commit adds new configuration files describing Trezor hardware models and build targets. It is a build-system feature with no user-facing behavior change and no apparent security relevance.
AI review queuedfix(core/cardano): don't access TR in global ctxby copilot-swe-agent[bot] · 9365fb01 · Jun 3, 2026 · 6 filesMessage 57 · ThinInformational 20Details
Commit message · copilot-swe-agent[bot]
fix(core/cardano): don't access TR in global ctx
[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 20/100
This commit is a code-quality fix in the Cardano app of the Trezor firmware. It removes direct access to the global translation object (TR) at the time the Python module is first loaded, and instead reads the translated strings only when they are actually needed. This avoids a potential startup-time crash or import-order problem if the translation system is not fully initialized when the module is imported. There is no direct evidence in the commit that this is an exploitable security vulnerability.
AI review queueddocs(core): document why `_waiting_screen` doesn't send ButtonRequestsby Roman Zeyde · 4fa4371a · Jun 3, 2026 · 1 fileMessage 74 · AdequateInformational 15Details
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Explains rationale or failure mode! No meaningful explanatory body
Why it was queued
parser or protocol pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit only adds comments explaining existing behavior in a Trezor firmware source file. No code logic was changed, no bugs were fixed, and no security vulnerability is present in the diff.
AI review queuedfix(core): avoid failing ButtonRequest handling at `ContinueOnErrors`by Roman Zeyde · f12deee6 · Jun 3, 2026 · 3 filesMessage 85 · StrongLow 44Details
Commit message · Roman Zeyde
fix(core): avoid failing ButtonRequest handling at `ContinueOnErrors`
No more button requests / errors will be sent later during the backup workflow after an I/O-related error/timeout.
Host will be ignored until the backup workflow is over - sending the final "Success" response may fail.
Other workflows can be aborted after user cancellation via `_waiting_screen()`.
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
parser or protocol pathsecond-pass: security-sensitive path
AI analysis · Low 44/100
This update fixes a bug in how the Trezor device handles on-screen button prompts when communication with the host computer hits errors or timeouts. Previously, an input/output problem during a backup could cause the device to send extra button requests or errors after the workflow should have ended, and the final 'Success' message could fail to send. The fix makes the device ignore further host messages until the backup workflow finishes, and lets users cancel other workflows through a new waiting screen. It is a reliability and defensive fix rather than a clear-cut remote exploit.
AI review queuedchore(core): update communication-related stringsby Roman Zeyde · ef194b4a · Jun 2, 2026 · 7 filesMessage 57 · ThinInformational 15Details
Commit message · Roman Zeyde
chore(core): update communication-related strings
[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 only changes user-facing text strings and their generated lookup tables in the Trezor firmware. It rewords a message about communication problems and adds a second, milder version of the message. There are no code behavior changes, no fixes to logic bugs, and no security-relevant functionality altered.
AI review queuedchore(deps): bump urllib3 in /tools/automatic_battery_testerby dependabot[bot] · 2bda8865 · May 29, 2026 · 1 fileMessage 93 · StrongInformational 15Details
Commit message · dependabot[bot]
chore(deps): bump urllib3 in /tools/automatic_battery_tester
Bumps [urllib3](https://github.com/urllib3/urllib3) from 2.6.3 to 2.7.0. - [Release notes](https://github.com/urllib3/urllib3/releases) - [Changelog](https://github.com/urllib3/urllib3/blob/main/CHANGES.rst) - [Commits](https://github.com/urllib3/urllib3/compare/2.6.3...2.7.0)
✓ 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
This is a routine automated dependency update by Dependabot that bumps the urllib3 library from version 2.6.3 to 2.7.0 inside a small internal testing tool (automatic_battery_tester). The change is a single line in a requirements file. There is no indication in the commit that this fixes a security issue, and the tool is not part of the Trezor firmware that runs on user devices.
AI review queuedfix(core): skip bitcoin.signtx_decred test on BTC_ONLYby M1nd3r · 80c9f204 · May 29, 2026 · 1 fileMessage 72 · AdequateInformational 15Details
Commit message · M1nd3r
fix(core): skip bitcoin.signtx_decred test on BTC_ONLY
[no changelog]
72/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit only changes a test file so that a Decred signing test is skipped when the firmware is built in Bitcoin-only mode. It does not modify any production firmware code, wallet behavior, or cryptographic logic. There is no security issue here.
AI review queuedtest(solana): sign message with many cosignersby Jakub Janků · e0b2dea3 · May 29, 2026 · 2 filesMessage 67 · AdequateInformational 15Details
Commit message · Jakub Janků
test(solana): sign message with many cosigners
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
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit only adds a new test case for Solana message signing with 64 cosigners and updates the expected screen snapshots used by automated testing. It does not change any firmware code that runs on the Trezor device, so it cannot introduce a security vulnerability or fix one.
AI review queuedchore(ci): skip `auto-assign` job for botsby M1nd3r · c784179b · May 29, 2026 · 1 fileMessage 57 · ThinInformational 15Details
Commit message · M1nd3r
chore(ci): skip `auto-assign` job for bots
[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 pathdocumentation-only discountsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This is a minor GitHub workflow change that stops an automatic pull-request assignment job from running when the pull request is opened by a bot account (whose username ends with '[bot]'). It has no security relevance to the Trezor firmware itself or to user funds.