TZ
← All projectsTrezor

Trezor firmware

Firmware monorepo for Trezor One, Model T, and Safe devices.

BitcoinHardware walletsNormal
Repository coverage

3768 commits in the local evidence base

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.

1328security candidates435second-pass queue3191AI analyses
201commits · 30 days
450commits · 60 days
1754commits · 180 days
2832commits · 365 days
Backfill bands
Aug 5 → Feb 61298 seen115 candidatesComplete
Feb 6 → Jun 6775 seen58 candidatesComplete
Jun 6 → Jul 6217 seen13 candidatesComplete
Jul 6 → Aug 5360 seen54 candidatesComplete
Commit communication

Does the history explain itself?

Message quality measures whether a commit identifies its scope, purpose, rationale, testing, and supporting references. It does not change the security-severity score.

68/100 average clarity
841Strong · 80–100
1731Adequate · 60–79
1189Thin · 40–59
7Opaque · 0–39
1security candidate with opaque commit messaging
Read the scoring rubric →
Developer activity

Who is changing the project?

Public Git author strings; identities are not independently verified.

DeveloperCommitsCandidatesAnalyzedHigh riskMessage avg.
tychovrahe394164355667
Jakub Janků1023067681
Roman Zeyde721230639372
obrusvit333135281364
cepetr301111228259
PrisionMike153101149271
Andrew Kozlik893885267
Petr Susil1159286
Martin Pastyřík291025175
M1nd3r292106248071
Ioan Bizău23076230059
Lukas Bielesch1067592066
Analysis record

Published AI watches

Last scanned 5 minutes ago

Informational 15 AI analysisMessage 90 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

ci(core): reuse HW tests Slack webhook

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.

abfe74f9by Michal Kazda+1−51 file
No security note in commit
Informational 15 AI analysisMessage 90 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

test(clear_signing): name the skipped cases

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…

98deb5b0by PrisionMike+25−92 files
No security note in commit
Informational 15 AI analysisMessage 95 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

test(clear_signing): run the cases without display format

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…

05c1f4efby PrisionMike+63−225 files
No security note in commit
Informational 15 AI analysisMessage 72 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

fix(translations): fix failing tutorial test in FR and small update to PT

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…

29cbc419by Michal Kazda+19−193 files
No security note in commit
Informational 10 AI analysisMessage 95 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

chore(core/rust): reduce coverage map size

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)
9bf2fc3aby M1nd3r+1−11 file
No security note in commit
Informational 15 AI analysisMessage 57 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

chore(translations): sync Crowdin translations

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…

b2e8b5e6by Thalarion+141−1837 files
No security note in commit
Informational 12 AI analysisMessage 67 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

test(clear_signing): edge cases for arrays

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
dcdf3068by PrisionMike+169−01 file
No security note in commit
High 70 AI analysisMessage 62 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

refactor(core): harden task switching against fault injections

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
2f159c6bby cepetr+16−51 file
Vendor flagged security relevance
Informational 15 AI analysisMessage 67 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

fix(tests): removed unused is_dynamic

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…

2ada2691by PrisionMike+6−323 files
No security note in commit
Informational 21 AI analysisMessage 62 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

feat(clear_signing): update proto defs for features to be supported.

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.
84cb6a4bby PrisionMike+1207−979 files
No security note in commit
Informational 19 AI analysisMessage 62 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

chore(python): fix protocol_v1 probe for bridge transport

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
46492ba4by M1nd3r+18−124 files
No security note in commit
Informational 15 AI analysisMessage 80 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

feat(core): show language name in change confirm

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…

5ff5cba0by Michal Kazda+295−67 files
No security note in commit
Informational 15 AI analysisMessage 67 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

fix(translations): fix failing tests in ES and 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…

9a12ab12by Michal Kazda+15−103 files
No security note in commit
Low 47 AI analysisMessage 85 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

chore(crypto): hardening against potential side-channel leakage

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
7829d7c7by M1nd3r+27−93 files
Vendor flagged security relevance
Informational 15 AI analysisMessage 72 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

feat(ci, clear_signing): add clear signing device tests as a nightly run.

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 …

fea125baby PrisionMike+2986−2117 files
No security note in commit
Informational 15 AI analysisMessage 57 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

chore(core): move `keccak_32` to unittests

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…

f3225451by Roman Zeyde+8−122 files
No security note in commit
Informational 15 AI analysisMessage 63 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

chore: remove SmartCash

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
b6d65c00by Roman Zeyde+5−52916 files
No security note in commit
Informational 15 AI analysisMessage 77 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

chore(common,core,legacy,crypto): remove Groestlcoin

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
e22d597dby Roman Zeyde+41−446845 files
No security note in commit
Informational 15 AI analysisMessage 47 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

chore(core): remove Tezos

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 …

433075c0by obrusvit+9531−1751964 files
No security note in commit
Informational 24 AI analysisMessage 85 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

fix(legacy): lower maximum auto-lock delay to 149 hours

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
c108f275by Ondřej Vejpustek+16−64 files
No security note in commit
Repository ledger

Explore captured commits

Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.

AI review queuedchore(tests): add test for back from amountby Ioan Bizău · 25a0c80a · Nov 25, 2025 · 2 filesMessage 67 · AdequateInformational 15Details
Commit message · Ioan Bizău

chore(tests): add test for back from amount

[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
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit only adds a new automated test for the Trezor hardware wallet. It simulates a user pressing the 'back' button while confirming a Bitcoin transaction amount, then completing the transaction normally. There is no change to the actual wallet firmware or production code, so it does not introduce or fix any security issue on its own.

AI review queuedchore(core): sign translationsby Roman Zeyde · f740f1eb · Nov 19, 2025 · 1 fileMessage 47 · ThinInformational 15Details
Commit message · Roman Zeyde

chore(core): sign translations

[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 pathtranslation-only discountsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit simply adds a new digital signature entry to a JSON file that records approved translation bundles for the Trezor hardware wallet. It is a routine metadata update with no code changes and no apparent security relevance.

AI review queueddocs(core): changelog for 2.9.4by Roman Zeyde · 26ef9c62 · Nov 19, 2025 · 23 filesMessage 57 · ThinInformational 15Details
Commit message · Roman Zeyde

docs(core): changelog for 2.9.4

[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
second-pass: unusually broad change
AI analysis · Informational 15/100

This commit is purely a documentation change: it compiles the release notes for Trezor firmware version 2.9.4 by moving individual changelog fragments into the main CHANGELOG files. No source code, configuration, or executable files were modified, so it cannot introduce or fix a security vulnerability on its own.

AI review queuedrefator(core): refactor tropic certificate cacheby Ondřej Vejpustek · 2f857bf6 · Nov 10, 2025 · 3 filesMessage 45 · ThinInformational 15Details
Commit message · Ondřej Vejpustek

refator(core): refactor tropic certificate cache

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
second-pass: broader security terminology
AI analysis · Informational 15/100

This commit is a code cleanup: it moves the Tropic chip certificate cache out of the production-test command file and into the shared Tropic driver, then exposes two helper functions so other code can fetch the cached public key and certificate chain. There is no visible security bug being fixed or introduced in the diff itself.

AI review queuedchore(core): remove italian localizationby obrusvit · 4b691a3e · Nov 7, 2025 · 29 filesMessage 57 · ThinInformational 15Details
Commit message · obrusvit

chore(core): remove italian localization

[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: unusually broad changesecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit simply removes the Italian language translation files and related font glyph definitions from the Trezor firmware. It is a routine localization cleanup with no security relevance. No code that handles cryptography, authentication, or device security is changed.

AI review queuedchore(core): remove Bolt-specific stringsby obrusvit · 985835f4 · Nov 5, 2025 · 6 filesMessage 80 · StrongInformational 18Details
Commit message · obrusvit

chore(core): remove Bolt-specific strings

- these strings are specific for reset flow in Bolt layout, remove them
from other layouts.
- done to reduce size of translation blobs

[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 pathtranslation-only discountsecond-pass: security-sensitive path
AI analysis · Informational 18/100

This commit is a routine cleanup of translation files for the Trezor hardware wallet firmware. It removes or empties text strings used only by the older 'Bolt' user-interface layout from newer layouts (Caesar, Delizia, Eckhart) to make translation files smaller. There is no code change, no security fix, and no vulnerability introduced.

AI review queuedfix(ui): break on unitby Ioan Bizău · c1559ce8 · Nov 5, 2025 · 6 filesMessage 50 · ThinInformational 15Details
Commit message · Ioan Bizău

fix(ui): break on unit

[no changelog]

50/100 · ThinMessage clarity
✓ Subject identifies a change✓ 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 is a cosmetic user-interface change. It replaces a non-breaking space between a number and its unit (like '1.23 BTC') with a regular space so the unit can wrap to the next line on small screens. There is no security impact.

AI review queuedchore: make genby obrusvit · 3ef747bc · Nov 4, 2025 · 1 fileMessage 40 · ThinInformational 15Details
Commit message · obrusvit

chore: make gen

[no changelog]

40/100 · ThinMessage clarity
✓ Subject identifies a change✓ 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 only updates a generated metadata file (signatures.json) that records the latest approved translation bundle for the Trezor device. It changes a timestamp, commit hash, and Merkle root pointer. There is no code change and no security-relevant behavior change visible in the diff.

AI review queuedchore: add characters to PT fontby Ioan Bizău · 085f973c · Nov 4, 2025 · 23 filesMessage 57 · ThinInformational 15Details
Commit message · Ioan Bizău

chore: add characters to PT font

[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
second-pass: unusually broad change
AI analysis · Informational 15/100

This commit adds two missing Portuguese characters, 'À' and 'ª', to the device's font files and fixes a spelling typo in a code generator file ('portugese' to 'portuguese'). It is a routine localization/typography update with no security relevance.

AI review queuedtest(ethereum): Add fixture for an unkown function callby PrisionMike · b4cb9951 · Nov 3, 2025 · 2 filesMessage 95 · StrongInformational 15Details
Commit message · PrisionMike

test(ethereum): Add fixture for an unkown function call

Every unkown call should not have an unkown contract address screen lest users get used to ignoring the warning screens.
[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
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit only adds a new test case for Ethereum transactions. It does not change any production code, so it cannot directly introduce or fix a security vulnerability. The test checks how the device displays a transaction when the called function, token, and blockchain are all unknown. The commit message hints at a user-interface design concern—avoiding unnecessary warning screens so users don't learn to ignore them—but that concern is not implemented in this change.

AI review queuedchore(core): remove redunant payment request sanitizer [no changelog]by M1nd3r · 00e9f105 · Oct 27, 2025 · 1 fileMessage 77 · AdequateLow 26Details
Commit message · M1nd3r

chore(core): remove redunant payment request sanitizer
[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
defensive validationsigning or wallet pathsecond-pass: near security thresholdsecond-pass: security-sensitive path
AI analysis · Low 26/100

This commit removes a safety check that ensured each memo inside a Bitcoin payment request contained exactly one memo type. The change is described by the developer as removing a redundant sanitizer, suggesting the validation is believed to happen elsewhere. Without access to the rest of the codebase or vendor confirmation, it is unclear whether this weakens security or is genuinely redundant.

AI review queuedfix(core/rust): fix UB due to unaligned access in protobuf codecby matejcik · 5a0f3a62 · Oct 23, 2025 · 5 filesMessage 74 · AdequateModerate 61Details
Commit message · matejcik

fix(core/rust): fix UB due to unaligned access in protobuf codec

74/100 · AdequateMessage clarity
✓ 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 · Moderate 61/100

This commit fixes undefined behavior in the Rust-based protobuf codec inside Trezor firmware. The code was reading multi-byte integers from data files that were not guaranteed to be properly aligned in memory, which can cause crashes or unpredictable behavior on some hardware. The patch ensures the data files are loaded with correct memory alignment and removes the use of 'packed' structs that forced unaligned access. It is a defensive hardening fix rather than a confirmed remote exploit.

AI review queueddocs(python): changelog for 0.20.0-dev0by matejcik · 9faa614a · Oct 20, 2025 · 22 filesMessage 57 · ThinInformational 15Details
Commit message · matejcik

docs(python): changelog for 0.20.0-dev0

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
second-pass: unusually broad change
AI analysis · Informational 15/100

This commit is purely a documentation update: it gathers individual changelog fragments into the main CHANGELOG.md file for the Python trezorlib package version 0.20.0-dev0. No program code was changed, so it cannot by itself introduce or fix a security vulnerability.

AI review queuedchore(test): add payment requests test case used in connect-e2e tests [no changelog]by M1nd3r · 27fa2a17 · Oct 18, 2025 · 3 filesMessage 87 · StrongInformational 15Details
Commit message · M1nd3r

chore(test): add payment requests test case used in connect-e2e 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 only adds a new test case and updates expected test screenshots. It does not change the actual Trezor firmware code that users run. The new test verifies that a payment request without a memo or nonce behaves as expected and does not trigger a nonce-reuse error. There is no security fix or vulnerability here.

AI review queuedchore: let br_code be Warningby Ioan Bizău · cb65178a · Oct 16, 2025 · 2 filesMessage 57 · ThinInformational 15Details
Commit message · Ioan Bizău

chore: let br_code be Warning

[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 is a minor internal cleanup change in the Trezor hardware wallet firmware. It removes explicit button-request type labels from two warning screens in the Ripple and Stellar cryptocurrency apps, letting them default to a generic 'Warning' category instead of 'ConfirmOutput'. There is no visible security bug or vulnerability being fixed.

AI review queuedchore: warning for Ripple destination tag missingby Ioan Bizău · 99b3f9fb · Oct 16, 2025 · 9 filesMessage 57 · ThinInformational 20Details
Commit message · Ioan Bizău

chore: warning for Ripple destination tag missing

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 adds a user-facing warning in Trezor hardware wallets when signing a Ripple transaction that does not include a destination tag. Destination tags are often required by exchanges to credit the correct account, so missing one can lead to lost funds. The change only shows an extra warning screen; it does not alter how transactions are validated or signed.

AI review queuedfeat: 32 bytes amount in ETH payment requestsby Ioan Bizău · abb2816c · Oct 16, 2025 · 15 filesMessage 57 · ThinLow 36Details
Commit message · Ioan Bizău

feat: 32 bytes amount in ETH payment requests

[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 · Low 36/100

This commit changes how payment-request amounts are encoded in Trezor firmware. Previously amounts were 8-byte numbers; now they can be 8 or 32 bytes, with 32 bytes used for Ethereum/EVM transactions. The change is a feature update to support larger EVM token amounts, not a clearly disclosed security fix. It does add length checks and an overflow guard, which reduces risk, but the change touches the trusted payment-request verification path, so any bug there could affect what amount the user is asked to approve.

AI review queuedchore(tests): long values in payment requestsby Ioan Bizău · ba67a2de · Oct 16, 2025 · 2 filesMessage 67 · AdequateInformational 12Details
Commit message · Ioan Bizău

chore(tests): long values in payment requests

[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
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 12/100

This commit only adds new automated tests. It checks that Trezor devices correctly reject payment-request amounts encoded with the wrong number of bytes (for Bitcoin) or values that are too large (for Ethereum). There is no change to the actual firmware or production code, and the commit message explicitly marks itself as a test-only chore with no changelog.

AI review queuedchore(core): Crowdin partial syncby obrusvit · 8da475da · Oct 15, 2025 · 10 filesMessage 72 · AdequateInformational 15Details
Commit message · obrusvit

chore(core): Crowdin partial sync

- including gen and fixtures

[no changelog]

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 pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit is a routine translation and localization update for the Trezor firmware. It updates translated user-facing strings in several languages, fixes a typo ('minumum' to 'minimum'), adjusts some strings to be device-layout-specific, and refreshes the corresponding UI test fixture hashes. There is no code behavior change and no security impact.

AI review queuedchore(core): sign translationsby obrusvit · 09907258 · Oct 14, 2025 · 1 fileMessage 62 · AdequateInformational 15Details
Commit message · obrusvit

chore(core): sign translations

- note: translations are signed from branch
`release/translations/25.10.21`

[no changelog]

62/100 · AdequateMessage clarity
✓ Descriptive subject✓ 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 simply adds a new cryptographic signature to a list that verifies official language translation files for the Trezor hardware wallet. It does not change any code, fix any bug, or introduce any security weakness. It is a routine administrative update so devices can trust the latest translation pack.

AI review queuedchore(tests): generate certificate chain for Tropicby Ioan Bizău · 46b5510e · Oct 14, 2025 · 4 filesMessage 72 · AdequateInformational 15Details
Commit message · Ioan Bizău

chore(tests): generate certificate chain for Tropic

[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
second-pass: broader security terminology
AI analysis · Informational 15/100

This commit only adds four test-only certificate and private-key files under the tests/tropic_model directory. They are clearly labeled as test fixtures, not used in production firmware, and the commit message explicitly says '[no changelog]'. There is no code change and no indication of a security fix or vulnerability.

AI review queuedfix(core): fix crash when setting wipe codeby tychovrahe · 66b0a65e · Oct 12, 2025 · 1 fileMessage 72 · AdequateLow 29Details
Commit message · tychovrahe

fix(core): fix crash when setting wipe code

[no changelog]

(cherry picked from commit da76bd501dd1bfefba472a969f213253ac6fc7cf)

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
second-pass: broader security terminology
AI analysis · Low 29/100

This commit fixes a crash that could occur when setting or changing the Trezor device's wipe code. The fix moves a memory-protection reconfiguration call to happen before user-interface progress is initialized. The crash appears to be a reliability bug rather than a security vulnerability that an attacker could exploit to steal funds or bypass protections.

AI review queuedfix(core): fix crash when setting wipe codeby tychovrahe · da76bd50 · Oct 10, 2025 · 1 fileMessage 57 · ThinLow 40Details
Commit message · tychovrahe

fix(core): fix crash when setting wipe code

[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
second-pass: broader security terminology
AI analysis · Low 40/100

This commit fixes a crash that could occur when setting or changing the Trezor device's wipe code (a special PIN that wipes the device). The fix moves a memory-protection reconfiguration call earlier, before user-interface progress initialization. The crash appears to be a reliability bug rather than a security vulnerability that would let an attacker steal funds, but a crash during security-sensitive wipe-code setup could disrupt the user experience or potentially be used in a denial-of-service scenario.

AI review queuedchore(core): remove unused translations per layoutby obrusvit · 1b5250c7 · Oct 8, 2025 · 9 filesMessage 62 · AdequateInformational 15Details
Commit message · obrusvit

chore(core): remove unused translations per layout

[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 pathtranslation-only discountsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit is a routine cleanup of translation strings in the Trezor firmware. It changes how some text labels are stored so that different device screen layouts (Bolt, Caesar, Delizia, Eckhart) can have their own versions of the same string, often leaving unused layouts with an empty string. There is no indication this fixes or introduces a security vulnerability.

AI review queuedchore(core): pull some translations from Crowdinby obrusvit · f24354b9 · Oct 7, 2025 · 7 filesMessage 57 · ThinInformational 15Details
Commit message · obrusvit

chore(core): pull some translations from Crowdin

[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 pathtranslation-only discountsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit only updates translated user-interface text strings for Bluetooth-related screens in several language files. It adds labels like 'Apps connected', 'Host info', 'MAC Address', and 'Waiting for host' in Czech, German, Spanish, French, Italian, and Portuguese, and refreshes the translation signature metadata. There is no executable code change, no security fix, and no vulnerability introduced.