CommitWatch RSS
TZ
← All projectsTrezor

Trezor firmware

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

BitcoinHardware walletsNormal
Source repository ↗
Repository coverage

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

915security candidates307second-pass queue1045AI analyses
338commits · 30 days
577commits · 60 days
1352commits · 180 days
2649commits · 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
470Strong · 80–100
1316Adequate · 60–79
859Thin · 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.
Andrew Kozlik702427266
Roman Zeyde566176208171
tychovrahe292104109161
PrisionMike945975173
Jakub Janků19915184
Martin Pastyřík2389173
cepetr1968282059
Ioan Bizău23076116059
obrusvit2137683064
M1nd3r2067177071
Lukas Bielesch846767067
Martin Milata1744646063
Analysis record

Published AI watches

Last scanned 57 minutes ago

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
Open full analysis →Source 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
Open full analysis →Source 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
Open full analysis →Source 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
Open full analysis →Source 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
Open full analysis →Source 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
Open full analysis →Source commit ↗
Informational 17 AI analysisMessage 57 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

feat(xtask): introduce project-toml build-options

This commit is a build-system refactoring for Trezor firmware. It moves the mapping of command-line build options to Rust/cargo features out of hard-coded Rust logic and into per-project TOML files. It also adds a small change so debug bui…

Build-option mapping now lives in project.toml files, increasing the attack surface for supply-chain/build-configuration tamperingMakefile change automatically enables debug-link for PYOPT=0 debug buildsValidation added to reject storage_insecure_testing_mode in production builds
d44de007by cepetr+681−40817 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 67 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

test(ethereum): fix incorrect address checksum

This commit only updates test data. It corrects the capitalization (checksum) of Ethereum addresses used in automated tests and refreshes the expected screen-shot hashes those tests compare against. There are no changes to the actual Trezo…

2b1938ccby Tomas Martykan+52−523 files
No security note in commit
Open full analysis →Source commit ↗
Low 33 AI analysisMessage 67 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

fix(python/trezorlib): enable entropy check on T1 by default

This commit changes the Trezor Python library so that, when setting up a Trezor Model One (the original Trezor 1 device), it now performs an entropy check by default if the device runs firmware 1.13.1 or newer. Previously, the library only…

Enables a previously disabled security/validation feature (entropy check) for a specific device modelAdds version-gated behavior to avoid errors on older firmwareDefensive hardening of wallet setup randomness verification
a4af9107by Andrew Kozlik+10−42 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 57 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

chore(core): remove scons related files

This commit is a routine cleanup that removes the old SCons build system files from the Trezor Core firmware repository. It deletes Makefiles, SConscripts, and related Python helper scripts, but does not change any firmware source code, cr…

a4b25c31by cepetr+5−927554 files
No security note in commit
Open full analysis →Source commit ↗
Informational 22 AI analysisMessage 80 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

refactor(core): assorted micropython-1.28.0 fixes

This commit updates Trezor's embedded MicroPython interpreter from an older version to 1.28.0. It pulls in several upstream MicroPython bug fixes, including stricter buffer-size checks for converting integers to bytes, a new stack-safety A…

Synchronizes upstream MicroPython fixes that include buffer-size and stack-safety hardeningPrevents Ctrl+C interruption of frozen boot code, reducing denial-of-service/control-flow risk during bootFixes sys.stdout.buffer.write() return value, which could affect code relying on correct I/O semantics
7ba7879dby Martin Milata+36−4012 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 70 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

refactor(core): use mp_obj_new_str_from_cstr

This commit is a simple code cleanup that replaces a common MicroPython string-creation pattern with a new helper function. It does not change what the code does, only how it is written. There is no security issue visible in the change.

6a889e6aby Martin Milata+3−33 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 80 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

refactor(core): replace hexlify with bytes.hex()

This is a large but straightforward internal cleanup: the project switched from using the MicroPython `ubinascii` module's `hexlify`/`unhexlify` functions to the standard Python `bytes.hex()` and `bytes.fromhex()` methods. The change remov…

44aa469eby Martin Milata+1334−1383120 files
No security note in commit
Open full analysis →Source commit ↗
Informational 18 AI analysisMessage 70 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

refactor(core): replace m_new_obj_with_finaliser

This commit is a routine code cleanup in the Trezor firmware's embedded MicroPython modules. It replaces an older, two-step object allocation pattern with a newer helper that allocates memory and sets the object type in one step. The chang…

No security-relevant logic changes observedNo input validation changesNo memory safety bug fixes (e.g., no overflow, use-after-free, or uninitialized memory fixes)
142794eaby Martin Milata+40−5619 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 80 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

refactor(core): bundle the utimeq module

This commit is a routine maintenance refactor. MicroPython removed its built-in 'utimeq' module, so Trezor copied the same code into its own firmware tree and renamed it to 'timeq'. There is no security bug being fixed and no new vulnerabi…

617bc806by Martin Milata+284−2211 files
No security note in commit
Open full analysis →Source commit ↗
Informational 17 AI analysisMessage 70 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

refactor(core): use mp_obj_new_str_from_vstr

This is a code cleanup change in Trezor's firmware that swaps one MicroPython internal helper for another. It replaces calls that create byte or string objects from a vstr buffer with newer, purpose-built helpers. The commit message says t…

Refactor only: helper function renames with equivalent semanticsNew str helper adds UTF-8 validation; bytes helper does not validateNo input validation, length, or error-handling changes observed
7ea11191by Martin Milata+72−7433 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 85 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

refactor(core): switch to slots-based mp_obj_type_t

This commit is a routine internal cleanup that switches how Trezor's firmware defines built-in MicroPython object types. It replaces older, manually-written type structures with a newer macro provided by the upstream MicroPython project. T…

ab51798fby Martin Milata+163−16624 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 62 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

refactor(core/rust): bindgen wrapper for calling static micropython functions

This commit is a straightforward internal code refactor. It adds a small C wrapper file so that Rust code can call two specific internal MicroPython functions that are declared as static/inline in headers. There is no user-facing change, n…

d5121d92by Martin Milata+20−06 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 80 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

build(core): adjust mpy-cross paths

This commit is a routine build-system update for the Trezor firmware. It changes where the build process looks for the MicroPython cross-compiler binary (mpy-cross) and synchronizes a configuration header with newer MicroPython code. There…

2ef70e16by Martin Milata+18−264 files
No security note in commit
Open full analysis →Source commit ↗
Low 30 AI analysisMessage 80 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

build(core): collect micropython GC root pointers

This commit updates the Trezor firmware build system to use a newer MicroPython mechanism for tracking special memory pointers called 'root pointers.' It removes hard-coded lists of these pointers from configuration files and instead colle…

GC root pointer handling changedBuild system now auto-collects root pointers instead of hard-coding themRemoves manual MICROPY_PORT_ROOT_POINTERS lists
fc128f3dby Martin Milata+75−107 files
No security note in commit
Open full analysis →Source 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-prioritytest(stellar): check parsed op countby Jakub Janků · c8966440 · Jul 22, 2026 · 1 fileMessage 67 · AdequateTriage 0Details
Commit message · Jakub Janků

test(stellar): check parsed op count

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
Lower-prioritytest(stellar): merge test_xdr with test_sign_txby Jakub Janků · 9a1ee9a3 · Jul 22, 2026 · 1 fileMessage 100 · StrongTriage 0Details
Commit message · Jakub Janků

test(stellar): merge test_xdr with test_sign_tx

test_xdr is not a proper device test, it uses the device just to
build payment requests which are then immediately dropped and unused.

Also note that the test fixtures were never recorded
(tests/ui_tests/fixtures.json has no test_xdr entry). This is because
the test depends on stellar-sdk which is not installed by default.

100/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Mentions testing or verification
Security candidatetest(ethereum): check function signature at source.by PrisionMike · 54c20421 · Jul 22, 2026 · 2 filesMessage 100 · StrongInformational 15Details
Commit message · PrisionMike

test(ethereum): check function signature at source.

- Improves on #7308
- instead of copying func sig, we import it from source.
- We can also safely use raw bytes instead of unhexlify at source.

[no changelog]

100/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✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly
Why it was queued
signing boundarysigning or wallet path
AI analysis · Informational 15/100

This is a test-only refactoring commit. It changes how Ethereum function signatures are represented in firmware source code (from hex strings converted at runtime to raw byte literals) and updates the corresponding unit test to verify those signatures against Solidity function definitions. There is no runtime behavior change and no security fix or vulnerability.

Security candidaterefactor(core): use simpler `interact` in FIDO & ButtonRequest waitingby Roman Zeyde · c3895435 · Jul 22, 2026 · 6 filesMessage 77 · AdequateInformational 12Details
Commit message · Roman Zeyde

refactor(core): use simpler `interact` in FIDO & ButtonRequest waiting

Refactor FIDO-related layouts and ButtonRequest-waiting layout, so they use the new helper function.

[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 pathauthentication pathparser or protocol path
AI analysis · Informational 12/100

This commit is a straightforward internal code cleanup. It replaces several direct uses of a lower-level UI helper (`Layout(...).get_result()`) with a simpler wrapper function (`interact_simple`). The behavior described in the comments—specifically that the waiting screen must not start its own ButtonRequest handler—is preserved in the new helper usage. There is no indication this change fixes or introduces a security vulnerability.

Security candidatefix(core): re-implement `draw_simple()` to avoid scoping violationsby Roman Zeyde · d772ca89 · Jul 22, 2026 · 8 filesMessage 100 · StrongLow 32Details
Commit message · Roman Zeyde

fix(core): re-implement `draw_simple()` to avoid scoping violations

Use a basic form of `interact()`, to be sure that passphrase prompt
layout will be properly stopped.

Following #7282.

[no changelog]

100/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Links an issue, advisory, or supporting reference
Why it was queued
access controlcryptography-sensitive pathboot or update pathauthentication path
AI analysis · Low 32/100

This commit fixes a UI lifecycle bug in Trezor firmware. The old `draw_simple()` function started a layout but did not properly wait for it to finish or stop it, which could leave stale UI tasks running ('scoping violations'). The new `interact_simple()` runs the layout to completion and returns its result, ensuring the passphrase prompt is correctly stopped. The security relevance is implied by the commit title and comments, but no explicit security disclosure or CVE is present.

Lower-priorityfix(l10n): updated blanking rules + removed unused [no changelog]by Michal Kazda · 66d0c0f2 · Jul 21, 2026 · 2 filesMessage 77 · AdequateTriage 0Details
Commit message · Michal Kazda

fix(l10n): updated blanking rules + removed unused
[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
translation-only discount
Lower-priorityfix(l10n): applied new blanking rules [no changelog]by Michal Kazda · c5b2760b · Jul 21, 2026 · 1 fileMessage 77 · AdequateTriage 0Details
Commit message · Michal Kazda

fix(l10n): applied new blanking rules
[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
translation-only discount
Lower-priorityfix(l10n): generated files added [no changelog]by Michal Kazda · ea0f76b9 · Jul 21, 2026 · 3 filesMessage 72 · AdequateTriage 0Details
Commit message · Michal Kazda

fix(l10n): generated files added
[no changelog]

72/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
Lower-prioritytest(core): use layout-specific expected `view_all_data` stringby Roman Zeyde · 8ecf0875 · Jul 21, 2026 · 1 fileMessage 87 · StrongTriage 0Details
Commit message · Roman Zeyde

test(core): use layout-specific expected `view_all_data` string

Previous code didn't work with blanked translated strings.

[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
Lower-priorityfix(ci): use both runners for HW tests of T2B1 [no changelog]by Michal Kazda · 3c70d736 · Jul 21, 2026 · 1 fileMessage 87 · StrongTriage 0Details
Commit message · Michal Kazda

fix(ci): use both runners for HW tests of T2B1
[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
documentation-only discount
Security candidatefeat: Add master fingerprint calculation.by Andrew Kozlik · eb5b3f4c · Jul 21, 2026 · 9 filesMessage 72 · AdequateInformational 13Details
Commit message · Andrew Kozlik

feat: Add master fingerprint calculation.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

72/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
Why it was queued
boot or update path
AI analysis · Informational 13/100

This commit adds a new build-time tooling feature for Trezor firmware: it calculates a single 'master fingerprint' that summarizes all the individual firmware image fingerprints produced during a reproducible build. It also improves the existing fingerprint tool so each fingerprint is labeled with the device model and image type (bootloader, firmware, etc.). There is no indication this change fixes a security bug or introduces a vulnerability; it is a transparency/reproducibility improvement.

Security candidatefix: build-docker.sh: build T1B1 firmware only for firmware targetby Andrew Kozlik · 17890ebf · Jul 21, 2026 · 2 filesMessage 85 · StrongInformational 15Details
Commit message · Andrew Kozlik

fix: build-docker.sh: build T1B1 firmware only for firmware target

The legacy build ignored --targets and ran on every invocation that included
T1B1. CI invokes the script separately for prodtest/bootloader and for firmware,
so each T1B1 job built the identical legacy firmware twice.

85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
update trust
AI analysis · Informational 15/100

This commit fixes a CI/build script inefficiency. The build script was building the same T1B1 (original Trezor) firmware twice because it ignored the requested build target. The fix makes the legacy T1B1 firmware build run only when the 'firmware' target is explicitly requested, and adjusts the CI workflow to initialize the build environment once and skip the redundant bootloader/prodtest step for T1B1. There is no security vulnerability here—just wasted build time.

Lower-priorityfix: build-docker.sh: fix --no-init usageby Andrew Kozlik · 6307fc7b · Jul 21, 2026 · 1 fileMessage 80 · StrongTriage 0Details
Commit message · Andrew Kozlik

fix: build-docker.sh: fix --no-init usage

1. With --no-init the snapshot's checkout stayed pinned at the commit it was
created from, so re-running for a branch that has moved would silently build
the old sources.

2. Dereference annotated tag objects correctly when resolving COMMIT_HASH.

3. Abort if shell.nix changed since the environment was initialized.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

80/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Lower-priorityfeat: build-docker.sh: skip bitcoin-only variants for targets that do not have oneby Andrew Kozlik · fd6e136b · Jul 21, 2026 · 1 fileMessage 77 · AdequateTriage 0Details
Commit message · Andrew Kozlik

feat: build-docker.sh: skip bitcoin-only variants for targets that do not have one

Co-Authored-By: Claude Fable 5 <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
Lower-priorityfeat: build-docker.sh: add --init-only and skip no-op docker commitsby Andrew Kozlik · 91b53c61 · Jul 21, 2026 · 1 fileMessage 62 · AdequateTriage 0Details
Commit message · Andrew Kozlik

feat: build-docker.sh: add --init-only and skip no-op docker commits

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Lower-prioritybuild: silence udevCheckHook in nix-shell, there are no udev rules to checkby Andrew Kozlik · 41692dc2 · Jul 21, 2026 · 1 fileMessage 62 · AdequateTriage 0Details
Commit message · Andrew Kozlik

build: silence udevCheckHook in nix-shell, there are no udev rules to check

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Security candidatechore: update nixpkgsby M1nd3r · 85ea63c0 · Jul 21, 2026 · 5 filesMessage 63 · AdequateInformational 15Details
Commit message · M1nd3r

chore: update nixpkgs

- Updated to the last successful build of nixpkgs-unstable, hash: f600ea449c7b5bb596fa1cf21c871cc5b9e31316
- Includes minor formatting adjustments.

[no changelog]

63/100 · AdequateMessage clarity
✓ Subject identifies a change✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
boot or update path
AI analysis · Informational 15/100

This commit is a routine maintenance update to the Nix package set used for building and development. It also includes minor formatting cleanups in unrelated files, such as removing now-unnecessary type-checker suppression comments and an unused import. There is no visible security fix or vulnerability being patched.

Lower-prioritychore(core): remove SDL error suppressionby M1nd3r · ab211a4f · Jul 21, 2026 · 1 fileMessage 98 · StrongTriage 0Details
Commit message · M1nd3r

chore(core): remove SDL error suppression

- Suppression of SDL error messages in tests was introduced in: https://github.com/trezor/trezor-firmware/pull/7111. It is no longer needed, as the issues have been resolved by updating nixpkgs to include newer sdl3 version.

[no changelog]

98/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Lower-prioritychore(deps): update astroid, pydantic, and pylintby M1nd3r · 50df0d20 · Jul 21, 2026 · 3 filesMessage 80 · StrongTriage 0Details
Commit message · M1nd3r

chore(deps): update astroid, pydantic, and pylint

The following packages were updated to support Python 3.14:

- Updated astroid v2.15.8 -> v3.3.11
- Updated pydantic v1.10.22 -> v1.10.26
- Updated pylint v2.11 -> v3.3.9

[no changelog]

80/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Lower-prioritychore(python): regenerate OPTIONS.rstby M1nd3r · d09dc64a · Jul 21, 2026 · 2 filesMessage 72 · AdequateTriage 0Details
Commit message · M1nd3r

chore(python): regenerate OPTIONS.rst

- Includes fix of ethereum CLI docstring.

[no changelog]

72/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
Lower-priorityfix(build): force UV to use nix-provided Pythonby M1nd3r · f07b610c · Jul 21, 2026 · 1 fileMessage 72 · AdequateTriage 0Details
Commit message · M1nd3r

fix(build): force UV to use nix-provided Python

[no changelog]

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

72/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
Security candidatefix(l10n): updating and fixing English strings - fewer versions per different layout - added period in places where it was missing - new description string for PIN reenter on Delizia [no changelog]by Michal Kazda · 42dbc643 · Jul 21, 2026 · 2 filesMessage 85 · StrongInformational 15Details
Commit message · Michal Kazda

fix(l10n): updating and fixing English strings
- fewer versions per different layout
- added period in places where it was missing
- new description string for PIN reenter on Delizia
[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
Why it was queued
access control
AI analysis · Informational 15/100

This commit only changes user-visible text strings in the Trezor firmware. It updates English translations, removes duplicate layout-specific versions of the same phrase, adds missing periods, and introduces a new description string shown when re-entering a PIN on the Delizia device layout. There is no code behavior change that would affect security.

AI review queuedfix(l10n): updated generated files [no changelog]by Michal Kazda · 6ee734ad · Jul 21, 2026 · 5 filesMessage 72 · AdequateInformational 15Details
Commit message · Michal Kazda

fix(l10n): updated generated files
[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 refresh of automatically generated translation files. It updates user-facing text strings (for example, changing punctuation or wording of on-screen messages) and adds one new string used during PIN setup. There is no change to security logic, cryptography, or how the device protects funds.

Lower-priorityfix(l10n): updated fixtures [no changelog]by Michal Kazda · 27ea3039 · Jul 21, 2026 · 1 fileMessage 72 · AdequateTriage 0Details
Commit message · Michal Kazda

fix(l10n): updated 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
AI review queuedchore(core): add ETH calldata digest translated stringby Roman Zeyde · a4097f69 · Jul 21, 2026 · 6 filesMessage 62 · AdequateInformational 15Details
Commit message · Roman Zeyde

chore(core): add ETH calldata digest translated string

[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 only adds a new user-facing text label, 'ERC-8213 digest', used when a Trezor device displays Ethereum transaction details. There is no code that processes transaction data, cryptography, or user authorization. It is a translation/string asset change with no security relevance on its own.