CommitWatch RSS
TZ
← All projectsTrezor

Trezor firmware

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

BitcoinHardware walletsNormal
Source repository ↗
Repository coverage

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

916security candidates311second-pass queue1354AI analyses
342commits · 30 days
588commits · 60 days
1363commits · 180 days
2653commits · 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
473Strong · 80–100
1321Adequate · 60–79
862Thin · 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.
PrisionMike945982273
Andrew Kozlik712436265
Roman Zeyde572177253171
tychovrahe292104125161
Jakub Janků22917182
Martin Pastyřík23811173
cepetr19682103059
Ioan Bizău23076140059
obrusvit21376107064
M1nd3r20671105071
Lukas Bielesch846771067
Martin Milata1744677063
Analysis record

Published AI watches

Last scanned 50 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 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
Open full analysis →Source 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
Open full analysis →Source 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
Open full analysis →Source 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
Open full analysis →Source 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
Open full analysis →Source 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
Open full analysis →Source 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
Open full analysis →Source 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
Open full analysis →Source 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
Open full analysis →Source 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
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 47 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

docs: add xtask documentation

This commit only adds documentation. It updates the table of contents and adds a new markdown page plus a diagram explaining the project's 'xtask' build helper. No code, build scripts, or firmware logic was changed, so it cannot introduce …

4879dababy cepetr+296−03 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 57 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

ci(core): fix nightly ARM emulator filename

This commit fixes a filename-renaming step in the project's automated nightly build pipeline. It ensures ARM64 emulator files get the correct name expected by another testing tool. There is no change to the actual Trezor firmware code, dev…

ab95f08fby Martin Milata+3−01 file
No security note in commit
Open full analysis →Source commit ↗
Informational 12 AI analysisMessage 62 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

chore(vendor): avoid micropython submodule noise in git status

This is a routine housekeeping change to reduce clutter in Git's status output for a third-party component (the MicroPython submodule). There is no indication it changes any code that runs on the Trezor device or affects security.

06cab32bby Martin Milata+1−11 file
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-prioritychore: update definitions timestampby PrisionMike · de494a07 · Jun 18, 2026 · 2 filesMessage 62 · AdequateTriage 0Details
Commit message · PrisionMike

chore: update definitions timestamp

(cherry picked from commit bdefd3c04be9b242cd901422778bc46ec8545821)

62/100 · AdequateMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope✓ Provides an explanatory body
Lower-prioritydocs(core): changelog for 2.12.1by PrisionMike · ac39a86d · Jun 18, 2026 · 15 filesMessage 72 · AdequateTriage 0Details
Commit message · PrisionMike

docs(core): changelog for 2.12.1

(cherry picked from commit 872ac9b19092714cee6814188a3ee9959e9520a6)

72/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
Lower-prioritychore: update releases.jsonby PrisionMike · a2f69d1a · Jun 18, 2026 · 1 fileMessage 62 · AdequateTriage 0Details
Commit message · PrisionMike

chore: update releases.json

(cherry picked from commit 6654b212ebd65b9478eaf8f65e282e81726b362c)

62/100 · AdequateMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope✓ Provides an explanatory body
Lower-priorityfix(core): changelog errors fixed.by PrisionMike · 914929b4 · Jun 18, 2026 · 5 filesMessage 72 · AdequateTriage 0Details
Commit message · PrisionMike

fix(core): changelog errors fixed.

(cherry picked from commit 6e2bee09c94845e271d41a0d31025d046cfc81d9)

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
documentation-only discount
Security candidatefix(core): device should be lockable when SD protection is onby Roman Zeyde · 99cc0249 · Jun 18, 2026 · 3 filesMessage 85 · StrongLow 43Details
Commit message · Roman Zeyde

fix(core): device should be lockable when SD protection is on

Previously, the device wasn't lockable if the PIN wasn't set.

[no changelog]

(cherry picked from commit 2f762e4c6d745a24def57f871689d68cd58871af)

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

This update fixes a bug where a Trezor hardware wallet with SD-card protection enabled could not be locked if no PIN was set. The device should be lockable whenever SD protection is active, because the SD card itself acts as a security factor. The change makes the homescreen use a broader 'can lock' check instead of only checking whether a PIN is configured. A new automated test also verifies that pressing and holding the screen can lock the device in this configuration.

Lower-prioritychore: upload signed secmonby PrisionMike · e386995b · Jun 18, 2026 · 1 fileMessage 62 · AdequateTriage 0Details
Commit message · PrisionMike

chore: upload signed secmon

(cherry picked from commit 64698d0d844e3322eca435beaae3df602aa08b10)

62/100 · AdequateMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope✓ Provides an explanatory body
AI review queuedchore(translations): upload signed translationsby PrisionMike · 67cc06e2 · Jun 18, 2026 · 1 fileMessage 72 · AdequateInformational 15Details
Commit message · PrisionMike

chore(translations): upload signed translations

(cherry picked from commit 7d7eb296412dc993f78976fe7f41dcf80d50019b)

72/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
Why it was queued
signing or wallet pathtranslation-only discountsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit adds a new digital signature entry to a JSON file that records approved translation packages for Trezor hardware wallets. It is a routine administrative update with no code changes and no apparent security relevance.

Security candidatefix(core): fix eth signing `data_length` checkby M1nd3r · a4e3fcc1 · Jun 18, 2026 · 1 fileMessage 72 · AdequateLow 49Details
Commit message · M1nd3r

fix(core): fix eth signing `data_length` check

[no changelog]

(cherry picked from commit 3f4f146340b7adefb7ebf149414fd39b7a4efb00)

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 boundarysigning or wallet path
AI analysis · Low 49/100

This commit replaces internal programming assertions (which crash the device if they fail) with proper error handling for Ethereum transaction signing when a payment request is involved. It ensures that if someone supplies a payment request verifier, the transaction must have zero data bytes and must actually include a payment request object. Without the fix, a malformed or unexpected input could trigger an assertion failure instead of a clean error, potentially causing the device to crash or behave unpredictably during signing.

Lower-priorityfeat(core/prodtest): add uptime commandby tychovrahe · 996062f2 · Jun 18, 2026 · 3 filesMessage 57 · ThinTriage 0Details
Commit message · tychovrahe

feat(core/prodtest): add uptime command

[no changelog]

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Lower-priorityfix(core): fix hw revision for T3B1by cepetr · bfbe2af4 · Jun 18, 2026 · 1 fileMessage 57 · ThinTriage 0Details
Commit message · cepetr

fix(core): fix hw revision for T3B1

[no changelog]

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Security candidatechore(core,secmon): release version bump to 2.12.2 and 1.0.12by PrisionMike · d621b2e1 · Jun 17, 2026 · 9 filesMessage 62 · AdequateInformational 15Details
Commit message · PrisionMike

chore(core,secmon): release version bump to 2.12.2 and 1.0.12

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

This commit is a routine version bump for a Trezor firmware release. It only changes version numbers in header files and translation metadata, plus updates the signed translation package reference. There are no code changes that affect security or device behavior.

Security candidatefix(core/xtask): add `"ui_debug_overlay"` feature on debug buildsby Roman Zeyde · dcb779af · Jun 17, 2026 · 1 fileMessage 77 · AdequateInformational 18Details
Commit message · Roman Zeyde

fix(core/xtask): add `"ui_debug_overlay"` feature on debug builds

It will show the top-right red-square marker on firmware/bootloader/prodtest.

[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
update trust
AI analysis · Informational 18/100

This commit fixes a build configuration issue so that debug builds of Trezor firmware, bootloader, and production-test firmware automatically enable a visual 'ui_debug_overlay' feature. That feature displays a small red square marker in the top-right corner of the screen, making it obvious when a debug/non-production build is running. It is a UI/UX and build-system change, not a fix for an exploitable security vulnerability.

Lower-priorityfeat(core/build): add reset command to xtaskby tychovrahe · 1e0f365d · Jun 17, 2026 · 3 filesMessage 57 · ThinTriage 0Details
Commit message · tychovrahe

feat(core/build): add reset command to xtask

[no changelog]

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Lower-priorityrefactor(core/build): extract run_openocd_command functionby tychovrahe · 7030c8e2 · Jun 17, 2026 · 1 fileMessage 62 · AdequateTriage 0Details
Commit message · tychovrahe

refactor(core/build): extract run_openocd_command function

[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
Security candidatefeat(tools): script to verify signed firmwaresby obrusvit · 0cbc8f59 · Jun 17, 2026 · 4 filesMessage 95 · StrongInformational 15Details
Commit message · obrusvit

feat(tools): script to verify signed firmwares

- verfy_signed_firmware.py compares SIGNED and UNSIGNED
bootloader/secmon/firmware binary
- firstly, it checks that those binaries are identical apart from the
signature field
- secondly, it checks the signatures are valid
- using this tool will be recommended in the ReleaseChecklist

[no changelog]

95/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✓ Names security-relevant behavior explicitly
Why it was queued
signing boundaryupdate trustsigning or wallet pathboot or update path
AI analysis · Informational 15/100

This commit adds a new helper script that lets developers check whether a signed Trezor firmware file truly matches its unsigned counterpart and whether its digital signature is valid. It is a defensive verification tool, not a fix for a security flaw, and introduces no vulnerability in the device code itself.

Lower-prioritychore(core): update "About Tropic" text in tutorialby Roman Zeyde · 3a54a09b · Jun 17, 2026 · 4 filesMessage 62 · AdequateTriage 0Details
Commit message · Roman Zeyde

chore(core): update "About Tropic" text in tutorial

[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
Security candidatefeat(core/prodtest): introduce prodtest error codesby tychovrahe · 406f0d11 · Jun 16, 2026 · 34 filesMessage 62 · AdequateInformational 20Details
Commit message · tychovrahe

feat(core/prodtest): introduce prodtest error codes

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
boot or update path
AI analysis · Informational 20/100

This commit is a feature addition to Trezor's internal production-test firmware. It replaces generic string-based error messages with a structured, numbered error-code system. There is no direct security vulnerability being fixed or introduced; it is a maintainability and diagnostics improvement for factory testing tools.

Lower-priorityfix(core/prodtest): fix error message in check_cert_chainby tychovrahe · 3aca8286 · Jun 16, 2026 · 1 fileMessage 62 · AdequateTriage 0Details
Commit message · tychovrahe

fix(core/prodtest): fix error message in check_cert_chain

[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
Lower-priorityfix(core/prodtest): fix trace and error message in prodtest_pm_charge_disableby tychovrahe · 00d8b0f2 · Jun 16, 2026 · 1 fileMessage 62 · AdequateTriage 0Details
Commit message · tychovrahe

fix(core/prodtest): fix trace and error message in prodtest_pm_charge_disable

[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
Lower-priorityrefactor(core/prodtest): move syslog prodtest command to prodtest projectby tychovrahe · 5e97e32f · Jun 16, 2026 · 5 filesMessage 62 · AdequateTriage 0Details
Commit message · tychovrahe

refactor(core/prodtest): move syslog prodtest command to prodtest project

[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
Lower-priorityfix(core/prodtest): fix error processing in prodtest_secure_channel_handshake_2by tychovrahe · bb3d30a8 · Jun 16, 2026 · 1 fileMessage 62 · AdequateTriage 0Details
Commit message · tychovrahe

fix(core/prodtest): fix error processing in prodtest_secure_channel_handshake_2

[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
Lower-prioritytest(core): de-duplicate backup success confirmationby Roman Zeyde · e27d7663 · Jun 16, 2026 · 1 fileMessage 87 · StrongTriage 0Details
Commit message · Roman Zeyde

test(core): de-duplicate backup success confirmation

Also, improve single-share confirmation at `load_N_shares()`.

[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-prioritychore(deps): bump `idna` v 3.10->v3.15by M1nd3r · 48e377f7 · Jun 16, 2026 · 1 fileMessage 85 · StrongTriage 0Details
Commit message · M1nd3r

chore(deps): bump `idna` v 3.10->v3.15

Resolves: https://github.com/trezor/trezor-firmware/security/dependabot/131

[no changelog]

85/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly
Why it was queued
automated dependency-update discount
AI review queuedchore: tweak hardcoded LiFi definitionsby Ioan Bizău · 9ad5fa49 · Jun 15, 2026 · 1 fileMessage 57 · ThinInformational 19Details
Commit message · Ioan Bizău

chore: tweak hardcoded LiFi definitions

[no changelog]

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 19/100

This is a small maintenance update to Trezor's Ethereum clear-signing definitions for the LiFi cross-chain swap service. It adds alternative contract addresses for LiFi on four blockchains where the service uses a different address than usual, and tweaks a few on-screen labels (for example changing 'Recipient' to 'Receiver' and adjusting capitalization). There is no indication of a security vulnerability being fixed.

Lower-prioritychore: update fixturesby Ioan Bizău · 6b982254 · Jun 15, 2026 · 1 fileMessage 40 · ThinTriage 0Details
Commit message · Ioan Bizău

chore: update fixtures

[no changelog]

40/100 · ThinMessage clarity
✓ Subject identifies a change✓ Uses a recognizable type or scope! No meaningful explanatory body