CommitWatch RSS
TZ
← All projectsTrezor

Trezor firmware

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

BitcoinHardware walletsNormal
Source repository ↗
Repository coverage

2660 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
343commits · 30 days
587commits · 60 days
1362commits · 180 days
2652commits · 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
861Thin · 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 5 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.

Security candidaterefactor(core/eckhart): simplify device menu handlingby Roman Zeyde · e6e514c9 · Jun 29, 2026 · 7 filesMessage 85 · StrongInformational 15Details
Commit message · Roman Zeyde

refactor(core/eckhart): simplify device menu handling

- use Qstrs as DeviceMenuResult variants
- replace `result_arg` by an explicit `DeviceMenuMsg` variant
- don't replace `DeviceMenuMsg::Close` by `CANCELLED`
- unify parent menu ID & menu refresh logic

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

This is a code cleanup (refactor) for the device menu on a specific Trezor hardware wallet model. It changes how menu actions are represented internally (from numbers to named strings) and simplifies how the menu decides which submenu to show next. There is no indication this fixes a security bug or introduces a vulnerability.

Lower-priorityfix(core): logic error in `ToifInfo::parse`by obrusvit · 368d6203 · Jun 27, 2026 · 5 filesMessage 82 · StrongTriage 0Details
Commit message · obrusvit

fix(core): logic error in `ToifInfo::parse`

- device test wrong TOIF prefix
- chore: rename relevant test functions to caesar

[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
Security candidatedocs(core/rust): fix a small typoby Roman Zeyde · 72540c6c · Jun 26, 2026 · 1 fileMessage 57 · ThinInformational 15Details
Commit message · Roman Zeyde

docs(core/rust): fix a small typo

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

This commit fixes a spelling mistake in a code comment ('Chcek' to 'Check'). No program logic, user interface behavior, or security properties were changed.

Security candidatechore(core/rust): use `deref()` instead of `deref_mut()`by Roman Zeyde · 61557dca · Jun 26, 2026 · 1 fileMessage 62 · AdequateInformational 12Details
Commit message · Roman Zeyde

chore(core/rust): use `deref()` instead of `deref_mut()`

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

This is a one-line code cleanup in the user-interface code for a Trezor hardware wallet screen. It changes a mutable borrow (`deref_mut`) to an immutable borrow (`deref`) where the code only reads a value. This is a routine Rust style/refactor change with no visible security effect.

Lower-prioritychore(core): update translated fixturesby Martin Milata · cdf92109 · Jun 26, 2026 · 1 fileMessage 57 · ThinTriage 0Details
Commit message · Martin Milata

chore(core): update translated fixtures

[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-prioritybuild(core): enable VCP for PYOPT=0 firmwareby Martin Milata · fad75e2d · Jun 26, 2026 · 1 fileMessage 57 · ThinTriage 0Details
Commit message · Martin Milata

build(core): enable VCP for PYOPT=0 firmware

[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): Show plain warning for multisig GetAddress.by Andrew Kozlik · 311c950a · Jun 26, 2026 · 4 filesMessage 95 · StrongTriage 0Details
Commit message · Andrew Kozlik

fix(core): Show plain warning for multisig GetAddress.

T3T1 and T3W1 show a danger dialog for multisig GetAddress and for
multi-account spends, which is unjustified, since there is nothing
inherently dangerous about these operations. A danger dialog is very
difficult to bypass, resulting in the user not even being able to
verify the multisig address. A standard warning dialog is sufficient.

[no changelog]

95/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification
Lower-prioritychore(deps): bump cryptography to v48.0.1by M1nd3r · b8952401 · Jun 26, 2026 · 2 filesMessage 93 · StrongTriage 0Details
Commit message · M1nd3r

chore(deps): bump cryptography to v48.0.1

- cryptography v48.0.0 -> v48.0.1

- Fixes https://github.com/trezor/trezor-firmware/security/dependabot/135.

- Changelog: https://cryptography.io/en/latest/changelog/#v48-0-1

[no changelog]

93/100 · StrongMessage clarity
✓ 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✓ Names security-relevant behavior explicitly
Why it was queued
automated dependency-update discount
Security candidatechore(deps): added `construct-typing` for typecheckingby M1nd3r · 855c08a9 · Jun 26, 2026 · 8 filesMessage 85 · StrongInformational 15Details
Commit message · M1nd3r

chore(deps): added `construct-typing` for typechecking

- `construct-typing` is used for typechecking in files using `Construct`.
- Also fixed formatting of type/pyright ignore comments.
[no changelog]

Co-authored-by: matejcik <596073+matejcik@users.noreply.github.com>

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

This commit only adds a development dependency called construct-typing to improve type checking and adjusts some type-checker ignore comments. It does not change how the Trezor firmware or tools behave at runtime, and it does not fix or introduce any security issue.

Lower-priorityci: hw: don't run core tests if only T1B1 is chosenby Martin Milata · 211c4dba · Jun 26, 2026 · 1 fileMessage 72 · AdequateTriage 0Details
Commit message · Martin Milata

ci: hw: don't run core tests if only T1B1 is chosen

72/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
documentation-only discount
Lower-priorityci: hw: fix T1B1 firmware pathby Martin Milata · 6d6a1aa3 · Jun 26, 2026 · 2 filesMessage 57 · ThinTriage 0Details
Commit message · Martin Milata

ci: hw: fix T1B1 firmware path

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
AI review queuedrefactor(core): close other workflows when starting `ProgressLayout`by Roman Zeyde · ada6a447 · Jun 26, 2026 · 4 filesMessage 62 · AdequateLow 26Details
Commit message · Roman Zeyde

refactor(core): close other workflows when starting `ProgressLayout`

[no changelog]

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 26/100

This commit moves the responsibility for closing other on-screen workflows into the ProgressLayout class itself, rather than having each individual feature call a separate 'close others' function. It is a code cleanup (refactor) and does not appear to introduce or fix a security vulnerability. The change makes UI behavior more consistent but does not change what the device ultimately allows.

Security candidatetest(core): don't run FIDO2 tests on BTC-only buildsby Roman Zeyde · f386bdf8 · Jun 26, 2026 · 1 fileMessage 72 · AdequateInformational 15Details
Commit message · Roman Zeyde

test(core): don't run FIDO2 tests on BTC-only builds

[no changelog]

72/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
authentication path
AI analysis · Informational 15/100

This commit only changes a test file so that FIDO2/WebAuthn tests are skipped on Bitcoin-only firmware builds. It does not change any production code, wallet logic, or security behavior. There is no vulnerability or security fix here.

Security candidatefix(python): fix trezorctl get-sessionby matejcik · fda4ad4b · Jun 26, 2026 · 2 filesMessage 92 · StrongLow 32Details
Commit message · matejcik

fix(python): fix trezorctl get-session

* if an invalid base64 string is set in TREZOR_SESSION_ID, trezorctl
would crash.
* when resuming a THP session, pairing.finish() was not called, leading
to an invalid state. Ensure that pairing.finish() is called even in case
a pairing flow did not run.
* change `@get_session(passphrase=False)` to mean "do not prompt for
passphrase" as opposed to "force use standard wallet". That matches the
actual usages in code.
* try resuming session first in `get_session`, so that if we do have
a session to resume, prompt_passphrase=False will use it without
(re)deriving a standard wallet. (There is no situation where we explicitly
*need* a standard wallet for something, what we actually have are situations
where we *don't need* to ask for passphrase.)
* take advantage of improved ensure_unlocked() and remove trezorctl-specific
reuse of standard session (which is now no longer auto-created).

92/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
Why it was queued
access control
AI analysis · Low 32/100

This commit fixes the `trezorctl get-session` command in Trezor's Python library. It prevents crashes when an invalid session ID is supplied, ensures a required pairing step is completed when resuming secure (THP) sessions, and changes the meaning of `passphrase=False` from 'always use a standard wallet' to 'do not ask for a passphrase.' These are reliability and state-correctness fixes in the command-line tool, not the hardware wallet firmware itself.

Lower-prioritytests: fix expected responses after ensure_unlocked() modificationby matejcik · 83032224 · Jun 26, 2026 · 1 fileMessage 60 · AdequateTriage 0Details
Commit message · matejcik

tests: fix expected responses after ensure_unlocked() modification

60/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Lower-priorityfix(python): explicitly derive root fingerprint in get_root_fingerprint()by matejcik · a4ca63d6 · Jun 26, 2026 · 1 fileMessage 85 · StrongTriage 0Details
Commit message · matejcik

fix(python): explicitly derive root fingerprint in get_root_fingerprint()

instead of using ensure_unlocked() to do it

that was basically incorrect before, and now ensure_unlocked() stopped
doing it so ¯\_(ツ)_/¯.

85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Security candidaterefactor(python/trezorctl): respect prompt_passphrase when creating a new sessionby matejcik · 011a3413 · Jun 26, 2026 · 1 fileMessage 85 · StrongLow 35Details
Commit message · matejcik

refactor(python/trezorctl): respect prompt_passphrase when creating a new session

the previous sequence of changes removed a short circuit path for "not
prompt_passphrase", this commit restores the correct behavior

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 35/100

This commit fixes a regression in the Trezor command-line tool (trezorctl). A recent earlier change accidentally removed a shortcut that skips asking the user for their passphrase when the caller explicitly says it is not needed. Because of that regression, trezorctl could prompt for or require a passphrase even in situations where it should not, such as when running commands that do not need a wallet. The patch restores the intended behavior by adding a `prompt_passphrase` flag and returning an empty passphrase when it is false.

Lower-prioritytests: add test for TrezorClient.ensure_unlocked()by matejcik · dcb6938d · Jun 26, 2026 · 1 fileMessage 60 · AdequateTriage 0Details
Commit message · matejcik

tests: add test for TrezorClient.ensure_unlocked()

60/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Security candidatechore: update UI fixturesby matejcik · 05711517 · Jun 26, 2026 · 1 fileMessage 85 · StrongInformational 15Details
Commit message · matejcik

chore: update UI fixtures

ensure_unlocked() no longer derives a session so all tests where a PIN
keyboard is shown after an ensure_unlocked() call will see changed
entropy

85/100 · StrongMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Names security-relevant behavior explicitly
Why it was queued
entropy or randomness
AI analysis · Informational 15/100

This commit only updates expected test screenshots (called UI fixtures) recorded as cryptographic hashes. The firmware code itself is not changed. The message explains that a helper function called ensure_unlocked() no longer creates a new session, so tests that show a PIN keyboard afterward now produce different screen images. This is a routine test-maintenance change with no direct security impact.

Security candidatefeat(python): client.ensure_unlocked() works without deriving a sessionby matejcik · b56edf29 · Jun 26, 2026 · 2 filesMessage 85 · StrongInformational 19Details
Commit message · matejcik

feat(python): client.ensure_unlocked() works without deriving a session

The trick here is that ApplySettings requires a PIN unlock, but if we
don't specify any setting to apply, nothing happens. (And we get a
failure "no setting provided" which we don't care about.)
ApplySettings doesn't need seed derivation and so works on a seedless
session, so we can use _get_any_session() to call it, and save time
deriving the seed in the common case.

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 19/100

This is a small optimization in the Trezor Python library. The `ensure_unlocked()` helper used to pick or create a wallet session, which forced the hardware wallet to derive the master seed just to check if the device was unlocked. The new code instead sends a harmless 'ApplyFlags(0)' command, which requires the user to enter their PIN but does not need seed derivation. This is a performance and usability improvement, not a security fix. There is no evidence in the commit of a vulnerability being patched.

Lower-priorityfix(core/eckhart): don't close device menu on `GetFeatures`by Roman Zeyde · 087e7934 · Jun 26, 2026 · 4 filesMessage 77 · AdequateTriage 0Details
Commit message · Roman Zeyde

fix(core/eckhart): don't close device menu on `GetFeatures`

Use `AVOID_RESTARTING_FOR` on TS7 (where the heap is the largest).

77/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
Lower-priorityfix(core): fix `AVOID_RESTARTING_FOR` handling in THPby Roman Zeyde · 7b570c25 · Jun 25, 2026 · 2 filesMessage 97 · StrongTriage 0Details
Commit message · Roman Zeyde

fix(core): fix `AVOID_RESTARTING_FOR` handling in THP

Similar to how it's done on v1 protocol handler.
Otherwise, recovery flow is interrupted by `GetFeatures` on TS7.

[no changelog]

97/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
Lower-prioritytest(core): make sure recovery flow is not restarted on `GetFeatures`by Roman Zeyde · 587e791a · Jun 25, 2026 · 2 filesMessage 72 · AdequateTriage 0Details
Commit message · Roman Zeyde

test(core): make sure recovery flow is not restarted on `GetFeatures`

[no changelog]

72/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Mentions testing or verification! No meaningful explanatory body
Lower-prioritytest(core): use capability name when skipping a testby Roman Zeyde · 3b8714a5 · Jun 25, 2026 · 1 fileMessage 87 · StrongTriage 0Details
Commit message · Roman Zeyde

test(core): use capability name when skipping a test

Previously, it was logging capability index instead.

[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 review queuedfix(solana): show the program id for unknown programs in the tx details view instead of a generic "Unsupported program" label.by Sammy Harris · 7ea33494 · Jun 25, 2026 · 4 filesMessage 77 · AdequateInformational 20Details
Commit message · Sammy Harris

fix(solana): show the program id for unknown programs in the tx details view instead of a generic "Unsupported program" label.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

77/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 20/100

This change improves the Trezor hardware wallet's Solana transaction confirmation screen. When a transaction contains an unknown program (smart contract), the device now shows the actual program ID instead of a generic 'Unsupported program' label. This helps users make a more informed decision before approving a transaction, but it is a user-interface improvement rather than a fix for a code vulnerability.