TZ
← All projectsTrezor

Trezor firmware

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

BitcoinHardware walletsNormal
Repository coverage

2673 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.

923security candidates311second-pass queue2662AI analyses
323commits · 30 days
552commits · 60 days
1337commits · 180 days
2644commits · 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.

66/100 average clarity
482Strong · 80–100
1323Adequate · 60–79
863Thin · 40–59
5Opaque · 0–39
Read the scoring rubric →
Developer activity

Who is changing the project?

Public Git author strings; identities are not independently verified.

DeveloperCommitsCandidatesAnalyzedHigh riskMessage avg.
tychovrahe292104292461
Roman Zeyde579182576272
PrisionMike945994273
Andrew Kozlik712470265
obrusvit21376213164
Jakub Janků22919182
Martin Pastyřík24823173
cepetr19682196059
Ioan Bizău23076230059
M1nd3r20772207071
Lukas Bielesch846784067
Martin Milata17446174063
Analysis record

Published AI watches

Last scanned 52 minutes ago

Informational 15 AI analysisMessage 72 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

test(core/ethereum): EIP-7702 tuple nonce must be non-zero

This commit only changes test data and expected screen fingerprints for Trezor's Ethereum EIP-7702 signing tests. It replaces one test case that used a nonce of 0 with the same scenario using a nonce of 67, because the real-world protocol …

Test-only change with no production code modificationEIP-7702 tuple nonce constraint reflected in test dataExpected UI test hashes regenerated for renamed test vector
76cd2ed4by Roman Zeyde+28−282 files
No security note in commit
Informational 15 AI analysisMessage 85 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

build(core): propagate emulator feature from projects

This commit is a build-system cleanup for the Trezor firmware's Rust code. It changes how the 'emulator' feature flag is passed between different software components. The firmware project no longer supports the emulator feature (which make…

5642074cby matejcik+5−44 files
No security note in commit
Low 27 AI analysisMessage 93 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

refactor(core): digest EIP-1559/EIP-7702 magic without RLP encoding

This commit is a small internal cleanup in Trezor's Ethereum signing code. It changes how two special 'magic' bytes (the transaction type markers for newer Ethereum transaction formats) are fed into the cryptographic hash. Previously the c…

Refactor of cryptographic hashing path for Ethereum transaction signingRemoval of implicit assumption that RLP encodes small integers as single bytesChange affects EIP-1559 and EIP-7702 transaction type markers
2362bc6fby Roman Zeyde+6−32 files
No security note in commit
Informational 15 AI analysisMessage 98 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

test(core): test RLP self-encoding bytestrings

This commit only adds a new unit test to the Trezor firmware codebase. It verifies that very short Ethereum RLP-encoded byte strings and small positive integers encode to themselves, which is a known property of the RLP specification. No p…

41538733by Roman Zeyde+16−01 file
No security note in commit
Informational 18 AI analysisMessage 57 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

chore(core): remove sha1 from regular FW

This commit removes the SHA-1 hashing function from the regular Trezor firmware. SHA-1 is an old, weak hash algorithm that is no longer considered secure for sensitive uses. The change deletes the code that exposes SHA-1 to apps running on…

Removal of a deprecated cryptographic primitive (SHA-1) from the firmware API surfaceReduction of attack surface and prevention of future misuse of a collision-vulnerable hashNo direct vulnerability patch or memory-safety bug is present in the diff
16d15774by M1nd3r+0−2006 files
No security note in commit
Low 27 AI analysisMessage 62 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

refactor(crypto): pass static public key to `noise_xxpsk3_*_init()`

This commit changes how a cryptographic library sets up secure connections. Previously, the code automatically calculated the public key from the private key. Now, the caller must provide the public key directly. This is a code-quality ref…

Cryptographic key handling changed: public key is now supplied rather than derivedPotential reduction of key-mismatch risk if caller provides correct public keyNew null-pointer check added for static_public_key
1b3128a4by Ondřej Vejpustek+20−92 files
No security note in commit
Informational 15 AI analysisMessage 57 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

refactor(crypto): change order of parameters

This commit simply reorders the arguments of an internal function called dh() and updates every place that calls it. The actual math and security behavior are unchanged; it is a code cleanup with no security effect.

33a119eeby Ondřej Vejpustek+15−151 file
No security note in commit
Informational 15 AI analysisMessage 47 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

refactor(crypto): prefix enums

This commit simply renames two groups of internal status labels (called enums) in the Trezor firmware's cryptographic code. The old names like WAITING_FOR_REQUEST1 were shared between two different parts of the code, so the developer gave …

f1c74046by Ondřej Vejpustek+26−222 files
No security note in commit
Low 37 AI analysisMessage 57 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

fix(crypto): prevent calling `memzero(NULL, ...)`

This commit fixes three places in the Trezor firmware's cryptographic code where a memory-clearing function could be called with a NULL pointer. In practice, passing NULL to memzero is harmless on Trezor's platform (it does nothing), but i…

NULL pointer passed to memory-zeroing helper in cryptographic codeUndefined behavior in C standard library contractDefensive hardening in Noise protocol implementation
0394e934by Ondřej Vejpustek+11−51 file
No security note in commit
Informational 18 AI analysisMessage 62 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

refactor(crypto): return remote static key from `noise_xxpsk3_*_handle_*()`

This commit is a code cleanup (refactor) for the cryptographic handshake code used in Trezor devices. It changes how the other party's long-term public key is returned to the caller: instead of storing it inside an internal state structure…

Removal of long-term public key storage from internal handshake stateCaller-supplied output buffer for remote static public key reduces internal secret retentionError-path memzero of returned key material on failure
3ead1aa6by Ondřej Vejpustek+79−423 files
No security note in commit
Informational 15 AI analysisMessage 62 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

refactor(xtask): rename ProjectProfile to ProjectConfig

This commit is a simple rename from 'ProjectProfile' to 'ProjectConfig' in two Rust source files. It only changes variable names, struct names, and error messages. There is no change to program logic, security behavior, or how data is hand…

581b37bcby cepetr+18−182 files
No security note in commit
Informational 15 AI analysisMessage 47 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

refactor(xtask): introduce ResolvedBuildArgs

This commit is a straightforward internal code refactor in Trezor's build tooling. It introduces a new ResolvedBuildArgs structure that centralizes default values for command-line build options before they are used. There is no change to u…

c24d1be8by cepetr+99−295 files
No security note in commit
Informational 15 AI analysisMessage 57 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

refactor(xtask): make build args tristate

This commit is a straightforward internal refactor of the Trezor firmware build tool's command-line argument handling. It changes many on/off flags from plain booleans to optional booleans so they can explicitly be set to true, false, or l…

271e249aby cepetr+57−561 file
No security note in commit
Informational 15 AI analysisMessage 57 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

refactor(xtask): introduce build options

This commit is a straightforward internal code reorganization in Trezor's build tooling. It moves build-option definitions from one Rust source file to a new module and adds the ability to load those options from a configuration file. Ther…

75085e2aby cepetr+275−2007 files
No security note in commit
Informational 15 AI analysisMessage 57 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

feat(xtask): introduce build presets

This commit is a developer tooling change for the Trezor firmware build system. It introduces 'build presets'—named configuration bundles stored in TOML files—so developers can select common build settings with a single command-line flag i…

eefe8f7fby cepetr+397−419 files
No security note in commit
Informational 15 AI analysisMessage 62 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

feat(xtask): upgrade manifest.yaml for tf-tools 0.3.0

This commit is a routine update to a build-system manifest file used by Trezor's internal tooling. It reorganizes and re-labels feature flags (for example, moving options between 'Features', 'Debugging', and 'Signing' groups and simplifyin…

57b28b89by cepetr+86−1351 file
No security note in commit
Informational 15 AI analysisMessage 62 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

feat(core): add tf-tools 0.3.1+ configuration file

This commit adds a single configuration file for a Trezor developer tool (a VS Code extension). It only points the tool to existing folders in the repository and contains no executable code, no secrets, and no changes to firmware behavior.…

e554f618by cepetr+8−01 file
No security note in commit
Informational 15 AI analysisMessage 62 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

refactor(xtask): rename ResolvedBuild to ResolvedBuildFeatures

This commit is a simple internal code cleanup: it renames a Rust data structure called ResolvedBuild to ResolvedBuildFeatures and updates the places that use it. There are no functional changes, no security fixes, and no changes to how the…

aaa2780bby cepetr+5−52 files
No security note in commit
Informational 15 AI analysisMessage 57 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

fix(core): fix up clippy warnings in storage.rs

This is a tiny code cleanup commit that replaces two calls to `ptr::null()` with Rust's `unwrap_or_default()` to silence automated Clippy lint warnings. It does not change what value is produced (still a null pointer when no salt is provid…

62354461by cepetr+2−21 file
No security note in commit
Informational 15 AI analysisMessage 47 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

refactor(xtask): simplify dependencies

This commit is a straightforward internal code cleanup in Trezor's build tooling. It moves a data structure and two helper methods from one Rust source file to another and updates callers accordingly. There is no change to user-facing beha…

6268349fby cepetr+9−193 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.

Lower-priorityfix(core): don't send `ButtonRequest` after unpairingby Roman Zeyde · 3bf6da87 · Sep 10, 2025 · 1 fileMessage 89 · StrongInformational 19Details
Commit message · Roman Zeyde

fix(core): don't send `ButtonRequest` after unpairing

Otherwise, it will fail since BLE is disconnected.

[no changelog]

89/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Explains rationale or failure mode
AI analysis · Informational 19/100

This is a small bug fix in the Trezor hardware wallet firmware. After a user unpairs a Bluetooth device, the device was trying to send a button-press request over the now-disconnected Bluetooth link, which would fail. The fix stops sending that request during the success screen shown right after unpairing. It is a robustness fix, not a security vulnerability fix.

Security candidatefix(core/bootloader): account for slow nRF startup - wait before displaying the start buttonby tychovrahe · 2a4ddb4f · Sep 10, 2025 · 5 filesMessage 62 · AdequateLow 26Details
Commit message · tychovrahe

fix(core/bootloader): account for slow nRF startup - wait before displaying the start button

[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
update trustboot or update path
AI analysis · Low 26/100

This bootloader-only change adds a short wait and a temporary logo screen when a Trezor device has no firmware installed and Bluetooth (BLE) is enabled. The goal is to give the wireless nRF chip time to finish starting up before the user sees the 'Start' setup button. Without this delay, the device could briefly show the start button while the Bluetooth state is still unknown, which might lead to a confusing or inconsistent setup experience. There is no direct evidence in the commit that this fixes an exploitable security vulnerability.

Lower-priorityfix(nordic/ble): adjust advertising interval settings to please apple devicesby tychovrahe · a25f4fc0 · Sep 10, 2025 · 1 fileMessage 62 · AdequateInformational 18Details
Commit message · tychovrahe

fix(nordic/ble): adjust advertising interval settings to please apple devices

[no changelog]

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
AI analysis · Informational 18/100

This commit changes how a Trezor Bluetooth device broadcasts its presence to Apple devices. It makes the device advertise more frequently at first, then slow down after 30 seconds, and adds a lock to prevent simultaneous changes. There is no clear security bug being fixed; it appears to be a compatibility/stability improvement for iPhones and iPads.

Lower-prioritychore(core): remove unneeded `sleep()` from `test_repeated_backup_via_device`by Roman Zeyde · b40ec910 · Sep 9, 2025 · 1 fileMessage 62 · AdequateInformational 15Details
Commit message · Roman Zeyde

chore(core): remove unneeded `sleep()` from `test_repeated_backup_via_device`

[no changelog]

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
AI analysis · Informational 15/100

This commit removes a short 0.1-second delay from an automated test script. It does not change the actual Trezor firmware or any code that runs on user devices. There is no security issue here.

Lower-prioritychore(core): remove unused code in session manager [no changelog]by M1nd3r · a121c0de · Sep 9, 2025 · 1 fileMessage 77 · AdequateInformational 15Details
Commit message · M1nd3r

chore(core): remove unused code in session manager
[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
AI analysis · Informational 15/100

This commit simply deletes an unused helper function that created a special type of session without a cache entry. There is no functional change to active code, no bug fix, and no security relevance.

Security candidatechore(core): raise exception for invalid ThpCreateNewSession messages [no changelog]by M1nd3r · a51895aa · Sep 9, 2025 · 1 fileMessage 77 · AdequateLow 37Details
Commit message · M1nd3r

chore(core): raise exception for invalid ThpCreateNewSession messages
[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
authentication path
AI analysis · Low 37/100

This commit tightens how the Trezor hardware wallet handles passphrase-protected sessions. Previously, a host could supply a passphrase in a message even when the device was configured to require the passphrase only on the device. Now the firmware raises an error in that case, preventing the host from silently overriding the 'always on device' setting. The change also adds a debug-only warning when a session is created with a passphrase while passphrase protection is disabled on the device.

Security candidatetest(python): add device test for passphrase on device [no changelog]by M1nd3r · 8cc43871 · Sep 9, 2025 · 1 fileMessage 87 · StrongInformational 15Details
Commit message · M1nd3r

test(python): add device test for passphrase on device
[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
access control
AI analysis · Informational 15/100

This commit only adds a new automated test for an existing feature. It does not change the actual Trezor firmware or its security behavior. The test checks that when a user enables 'passphrase always entered on device,' the device correctly rejects passphrases sent from the computer and accepts passphrases typed directly on the device. There is no security fix or vulnerability introduced here.

Lower-prioritychore(test): update fixtures [no changelog]by M1nd3r · 1f2a0c66 · Sep 9, 2025 · 1 fileMessage 82 · StrongInformational 15Details
Commit message · M1nd3r

chore(test): update fixtures
[no changelog]

82/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Mentions testing or verification
AI analysis · Informational 15/100

This commit only adds new expected screen snapshots (called 'fixtures') for an automated user-interface test. It does not change any firmware code, wallet logic, or security behavior. There is no security issue here.

Security candidatechore(core): update type annotation for `button_request` in `trezorui_api` [no changelog]by M1nd3r · 296422e4 · Sep 9, 2025 · 2 filesMessage 77 · AdequateInformational 15Details
Commit message · M1nd3r

chore(core): update type annotation for `button_request` in `trezorui_api`
[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
boot or update path
AI analysis · Informational 15/100

This commit only changes a type annotation in documentation and generated mock files. It replaces `tuple[int, str]` with `tuple[ButtonRequestType, str]` for a function that returns button request information. No actual code behavior changes, and there is no security relevance.

Lower-prioritychore(core): add type annotation to `loop.py` [no changelog]by M1nd3r · 9630495c · Sep 9, 2025 · 3 filesMessage 77 · AdequateInformational 15Details
Commit message · M1nd3r

chore(core): add type annotation to `loop.py`
[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
AI analysis · Informational 15/100

This commit only adds Python type annotations to the scheduler/loop module and a couple of related files. It does not change runtime behavior, fix a bug, or alter security logic. It is a code-quality/refactoring change.

Lower-priority refactor(test): replace all Union usage by | syntax in `/tests` [no changelog]by M1nd3r · 87614b54 · Sep 9, 2025 · 1 fileMessage 87 · StrongInformational 15Details
Commit message · M1nd3r

refactor(test): replace all Union usage by | syntax in `/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
AI analysis · Informational 15/100

This is a minor code cleanup in the test suite only. It replaces an older Python type-hint style (`Union[...]`) with a newer, equivalent syntax (`|`) in a single test helper file. There is no change to the actual Trezor firmware or to any runtime behavior, and no security relevance.

AI review queued refactor(core): replace all Union usage by | syntax in core except `core/vendor` [no changelog]by M1nd3r · 60cc5c06 · Sep 9, 2025 · 7 filesMessage 77 · AdequateInformational 15Details
Commit message · M1nd3r

refactor(core): replace all Union usage by | syntax in core except `core/vendor`
[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 15/100

This commit is a routine code cleanup that replaces older Python type-hint syntax (Union[...]) with the newer pipe syntax (|). It also updates one helper function to return None instead of the string 'dynamic' for consistency. There is no change to program logic, no security fix, and no vulnerability introduced.

Security candidatechore(core): use Python's `NotImplementedError` for missing layoutsby Roman Zeyde · 9f7df35d · Sep 8, 2025 · 7 filesMessage 77 · AdequateInformational 15Details
Commit message · Roman Zeyde

chore(core): use Python's `NotImplementedError` for missing layouts

Also, remove method-specific error messages, since it could be deduced
from the exception traceback.

[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 is a routine code cleanup in the Trezor firmware's user-interface layer. It replaces a custom 'not implemented' error message with Python's standard NotImplementedError and removes some method-specific error strings. There is no security-relevant change: the same functions still fail in the same situations, only the error type and wording differ.

Security candidatefix(core): mark THP `app_name` and `host_name` with yellowby Roman Zeyde · c5fc0c09 · Sep 8, 2025 · 15 filesMessage 70 · AdequateInformational 19Details
Commit message · Roman Zeyde

fix(core): mark THP `app_name` and `host_name` with yellow

Fixes #5557.

[no changelog]

70/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
cryptography-sensitive pathsigning or wallet pathboot or update path
AI analysis · Informational 19/100

This commit changes how the Trezor hardware wallet displays pairing and connection prompts for its new Bluetooth-like 'THP' protocol. Instead of building the prompt sentence in Python code, it now uses a dedicated Rust UI screen that highlights the app name and host name in yellow. This is a user-experience and anti-phishing improvement, not a fix for a remotely exploitable vulnerability. The change only affects on-screen text formatting and which UI component is used; it does not change cryptographic checks, authorization logic, or data parsing.

Lower-prioritychore(core): don't use empty strings in `trezortranslate_keys.pyi`by Roman Zeyde · dc8552b7 · Sep 8, 2025 · 2 filesMessage 62 · AdequateInformational 15Details
Commit message · Roman Zeyde

chore(core): don't use empty strings in `trezortranslate_keys.pyi`

[no changelog]

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
AI analysis · Informational 15/100

This commit updates translation stub files used during development and type-checking. It replaces placeholder empty strings with actual English text and changes the template so it picks the first non-empty translation when generating stubs. There is no runtime firmware change and no security relevance.

Lower-priorityrefactor(core): don't store text continuation flag in `Op::Text`by Roman Zeyde · bc75f981 · Sep 8, 2025 · 1 fileMessage 85 · StrongInformational 13Details
Commit message · Roman Zeyde

refactor(core): don't store text continuation flag in `Op::Text`

Also, increase `MAX_OPS` a bit, since each `Op` takes less RAM now.

After:
```
print-type-size type: `ui::component::text::op::Op<'_>`: 12 bytes, alignment: 4 bytes
print-type-size variant `Text`: 12 bytes
print-type-size field `.0`: 12 bytes
print-type-size variant `Font`: 8 bytes
print-type-size padding: 4 bytes
print-type-size field `.0`: 4 bytes, alignment: 4 bytes
print-type-size variant `Chunkify`: 8 bytes
print-type-size padding: 2 bytes
print-type-size field `.0`: 6 bytes, alignment: 2 bytes
print-type-size variant `CursorOffset`: 6 bytes
print-type-size padding: 2 bytes
print-type-size field `.0`: 4 bytes, alignment: 2 bytes
print-type-size variant `Color`: 5 bytes
print-type-size padding: 2 bytes
print-type-size field `.0`: 3 bytes, alignment: 1 bytes
print-type-size variant `LineSpacing`: 4 bytes
print-type-size padding: 2 bytes
print-type-size field `.0`: 2 bytes, alignment: 2 bytes
print-type-size variant `Alignment`: 3 bytes
print-type-size padding: 2 bytes
print-type-size field `.0`: 1 bytes, alignment: 1 bytes
print-type-size variant `LineBreaking`: 3 bytes
print-type-size padding: 2 bytes
print-type-size field `.0`: 1 bytes, alignment: 1 bytes
print-type-size variant `NextPage`: 0 bytes
print-type-size type: `ui::display::font::GlyphData`: 12 bytes, alignment: 4 bytes
```

Before:
```
print-type-size type: `ui::component::text::op::Op<'_>`: 16 bytes, alignment: 4 bytes
print-type-size variant `Text`: 16 bytes
print-type-size field `.0`: 12 bytes
print-type-size field `.1`: 4 bytes
print-type-size variant `Font`: 8 bytes
print-type-size padding: 4 bytes
print-type-size field `.0`: 4 bytes, alignment: 4 bytes
print-type-size variant `Chunkify`: 8 bytes
print-type-size padding: 2 bytes
print-type-size field `.0`: 6 bytes, alignment: 2 bytes
print-type-size variant `CursorOffset`: 6 bytes
print-type-size padding: 2 bytes
print-type-size field `.0`: 4 bytes, alignment: 2 bytes
print-type-size variant `Color`: 5 bytes
print-type-size padding: 2 bytes
print-type-size field `.0`: 3 bytes, alignment: 1 bytes
print-type-size variant `LineSpacing`: 4 bytes
print-type-size padding: 2 bytes
print-type-size field `.0`: 2 bytes, alignment: 2 bytes
print-type-size variant `Alignment`: 3 bytes
print-type-size padding: 2 bytes
print-type-size field `.0`: 1 bytes, alignment: 1 bytes
print-type-size variant `LineBreaking`: 3 bytes
print-type-size padding: 2 bytes
print-type-size field `.0`: 1 bytes, alignment: 1 bytes
print-type-size variant `NextPage`: 0 bytes
```

[no changelog]

85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
AI analysis · Informational 13/100

This is a small internal code cleanup in the Trezor firmware's text-rendering system. It removes a flag stored inside text-drawing instructions and tracks it separately instead, which slightly reduces memory use and allows more drawing instructions to be stored. There is no indication this fixes a security bug or changes user-visible behavior in a risky way.

Security candidatechore(core): rename `OpTextLayout::add_text` to `add_text_with_font`by Roman Zeyde · 4e1f32aa · Sep 8, 2025 · 6 filesMessage 62 · AdequateInformational 15Details
Commit message · Roman Zeyde

chore(core): rename `OpTextLayout::add_text` to `add_text_with_font`

[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
cryptography-sensitive pathboot or update path
AI analysis · Informational 15/100

This commit is a simple rename of a Rust function from `add_text` to `add_text_with_font` across several UI layout files. It does not change any behavior, logic, or security properties of the code. It is a routine code cleanup with no user-visible or security impact.

Lower-priorityrefactor(core): don't store text font in `Op::Text`by Roman Zeyde · e66d4dec · Sep 8, 2025 · 1 fileMessage 85 · StrongInformational 13Details
Commit message · Roman Zeyde

refactor(core): don't store text font in `Op::Text`

Also, increase `MAX_OPS` a bit, since each `Op` takes less RAM now.

After:
```
print-type-size type: `ui::component::text::op::Op<'_>`: 16 bytes, alignment: 4 bytes
print-type-size variant `Text`: 16 bytes
print-type-size field `.0`: 12 bytes
print-type-size field `.1`: 4 bytes
print-type-size variant `Font`: 8 bytes
print-type-size padding: 4 bytes
print-type-size field `.0`: 4 bytes, alignment: 4 bytes
print-type-size variant `Chunkify`: 8 bytes
print-type-size padding: 2 bytes
print-type-size field `.0`: 6 bytes, alignment: 2 bytes
print-type-size variant `CursorOffset`: 6 bytes
print-type-size padding: 2 bytes
print-type-size field `.0`: 4 bytes, alignment: 2 bytes
print-type-size variant `Color`: 5 bytes
print-type-size padding: 2 bytes
print-type-size field `.0`: 3 bytes, alignment: 1 bytes
print-type-size variant `LineSpacing`: 4 bytes
print-type-size padding: 2 bytes
print-type-size field `.0`: 2 bytes, alignment: 2 bytes
print-type-size variant `Alignment`: 3 bytes
print-type-size padding: 2 bytes
print-type-size field `.0`: 1 bytes, alignment: 1 bytes
print-type-size variant `LineBreaking`: 3 bytes
print-type-size padding: 2 bytes
print-type-size field `.0`: 1 bytes, alignment: 1 bytes
print-type-size variant `NextPage`: 0 bytes
```

Before:
```
print-type-size type: `ui::component::text::op::Op<'_>`: 20 bytes, alignment: 4 bytes
print-type-size variant `Text`: 17 bytes
print-type-size field `.0`: 12 bytes
print-type-size field `.1`: 4 bytes
print-type-size field `.2`: 1 bytes
print-type-size variant `Font`: 8 bytes
print-type-size padding: 4 bytes
print-type-size field `.0`: 4 bytes, alignment: 4 bytes
print-type-size variant `Chunkify`: 8 bytes
print-type-size padding: 2 bytes
print-type-size field `.0`: 6 bytes, alignment: 2 bytes
print-type-size variant `CursorOffset`: 6 bytes
print-type-size padding: 2 bytes
print-type-size field `.0`: 4 bytes, alignment: 2 bytes
print-type-size variant `Color`: 5 bytes
print-type-size padding: 2 bytes
print-type-size field `.0`: 3 bytes, alignment: 1 bytes
print-type-size variant `LineSpacing`: 4 bytes
print-type-size padding: 2 bytes
print-type-size field `.0`: 2 bytes, alignment: 2 bytes
print-type-size variant `Alignment`: 3 bytes
print-type-size padding: 2 bytes
print-type-size field `.0`: 1 bytes, alignment: 1 bytes
print-type-size variant `LineBreaking`: 3 bytes
print-type-size padding: 2 bytes
print-type-size field `.0`: 1 bytes, alignment: 1 bytes
print-type-size variant `NextPage`: 0 bytes
print-type-size end padding: 3 bytes
```

[no changelog]

85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
AI analysis · Informational 13/100

This is a routine internal code cleanup in the Trezor firmware's on-screen text rendering system. It removes the font field from individual text-drawing instructions and instead tracks the next font to use separately, slightly reducing memory use per instruction and allowing a few more instructions to be stored. There is no indication this fixes a security bug or changes user-visible behavior.

AI review queuedbuild(deps): bump pillow in /tools/automatic_battery_testerby dependabot[bot] · 7bdcb666 · Sep 8, 2025 · 1 fileMessage 93 · StrongInformational 15Details
Commit message · dependabot[bot]

build(deps): bump pillow in /tools/automatic_battery_tester

Bumps [pillow](https://github.com/python-pillow/Pillow) from 11.2.1 to 11.3.0.
- [Release notes](https://github.com/python-pillow/Pillow/releases)
- [Changelog](https://github.com/python-pillow/Pillow/blob/main/CHANGES.rst)
- [Commits](https://github.com/python-pillow/Pillow/compare/11.2.1...11.3.0)

---
updated-dependencies:
- dependency-name: pillow
dependency-version: 11.3.0
dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>

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
documentation-only discountautomated dependency-update discountsecond-pass: broader security terminology
AI analysis · Informational 15/100

This is a routine automated dependency update by Dependabot, bumping the Python image-processing library Pillow from version 11.2.1 to 11.3.0 inside an internal testing tool. The change is a single version number in a requirements file for the automatic battery tester, which is not part of the Trezor firmware that runs on devices or handles cryptocurrency secrets. There is no indication in the commit that this fixes a security issue, and no verified security references were supplied.

Lower-prioritychore(python): clean out Makefileby matejcik · 2b08fcfc · Sep 8, 2025 · 1 fileMessage 57 · ThinInformational 15Details
Commit message · matejcik

chore(python): clean out Makefile

[no changelog]

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
AI analysis · Informational 15/100

This commit is a routine cleanup of a Python package Makefile. It removes old setup.py-based build and install targets and switches the distribution target to use the modern 'uv' build tool. There is no security relevance in the diff itself.

Security candidatestyle: update to black 25 style, silence new flake8 warningsby matejcik · 87f5f12d · Sep 8, 2025 · 38 filesMessage 50 · ThinInformational 15Details
Commit message · matejcik

style: update to black 25 style, silence new flake8 warnings

[no changelog]

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
cryptography-sensitive pathsigning or wallet pathboot or update pathauthentication path
AI analysis · Informational 15/100

This commit is purely a code-style update. It reformats Python source files to match the latest version of the Black formatter, changes uppercase hex escapes in byte strings to lowercase, removes unnecessary 'global' declarations, and adjusts some 'with' statements and trailing commas to satisfy updated flake8 rules. There are no functional changes to the firmware, tests, or tooling.

Lower-prioritybuild(python/tools): migrate toiftool to uvby matejcik · 51c833d8 · Sep 8, 2025 · 2 filesMessage 57 · ThinInformational 15Details
Commit message · matejcik

build(python/tools): migrate toiftool to uv

[no changelog]

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
AI analysis · Informational 15/100

This commit is a routine build tooling change. It switches the Python packaging for a small internal command-line tool (toiftool) from Poetry to uv, updating only documentation and the pyproject.toml configuration file. There is no change to the tool's actual code, dependencies, or behavior, and no security relevance is apparent.

Lower-prioritybuild(core/tools): migrate trezor_core_tools to uvby matejcik · 26d67572 · Sep 8, 2025 · 3 filesMessage 62 · AdequateInformational 15Details
Commit message · matejcik

build(core/tools): migrate trezor_core_tools to uv

[no changelog]

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
AI analysis · Informational 15/100

This commit is a routine build tooling change. It switches the Python packaging tool for Trezor's internal developer utilities from Poetry to uv, updates the pyproject.toml configuration format, and adds an empty __init__.py file. There is no indication of any security fix, vulnerability, or behavior change in the actual tools.

Lower-prioritybuild(tools): migrate trezor-pylint-plugin to uvby matejcik · 25c30024 · Sep 8, 2025 · 2 filesMessage 57 · ThinInformational 15Details
Commit message · matejcik

build(tools): migrate trezor-pylint-plugin to uv

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
AI analysis · Informational 15/100

This commit is a routine build tooling change. It switches the packaging setup for an internal Python linting plugin from Poetry to uv/hatchling, updates the Python version requirement from 3.8+ to 3.9+, and removes pinned wildcard dependency versions. There is no change to firmware, wallet logic, cryptography, or any runtime security behavior.

AI review queuedbuild: migrate to uv, drop poetry everywhereby matejcik · 8a75794d · Sep 8, 2025 · 29 filesMessage 72 · AdequateInformational 15Details
Commit message · matejcik

build: migrate to uv, drop poetry everywhere

except for HWI and ts-tvl that are using it locally

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

This commit is a routine build-system housekeeping change for the Trezor firmware repository. It replaces the Python Poetry package manager with the `uv` package manager across CI workflows, build scripts, and documentation. No device firmware code, cryptographic logic, or security-sensitive behavior is modified. The change is purely about how development dependencies are installed and invoked.