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.
Message quality measures whether a commit identifies its scope, purpose, rationale, testing, and supporting references. It does not change the security-severity score.
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
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
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.
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 …
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
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
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…
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…
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…
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…
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…
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…
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.…
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…
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…
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…
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 …
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
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…
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.
✓ 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
boot or update path
AI analysis · Informational 17/100
This commit changes how the Trezor firmware build system handles source-line information in its embedded MicroPython interpreter. Previously, enabling or disabling source-line data required rebuilding the MicroPython cross-compiler. After this change, the same compiler binary can include or omit source lines via a command-line flag. This is a build-system convenience and optimization; it does not fix a vulnerability in user-facing code.
build(core): exclude `storage.cache_codec` from THP builds
THP PYOPT=1 builds don't need it.
THP PYOPT=0 builds need DebugLink functionality, but don't use `CodecContext`'s cache-related methods.
Reduces THP build flash usage by ~1kB.
[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 18/100
This is a build-system cleanup for Trezor firmware. It removes an unused storage cache module from a specific firmware variant (THP builds) to save about 1 kB of flash space. The code change also makes sure that when the module is excluded, the few functions that relied on it are skipped too. There is no direct security bug here, but any build-system change that alters which code is compiled into a hardware wallet deserves a quick sanity check.
- fix incorrectly placed connection indicator in some cases - slightly align the label
[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
boot or update path
AI analysis · Informational 15/100
This commit fixes visual alignment of icons and text on the Trezor hardware wallet's homescreen for the Eckhart layout. It adjusts where the connection indicator and device label are drawn so they line up correctly with the battery icon. There is no security relevance in this change.
Lower-prioritybuild(core): use portable sed languageby matejcik · a918d4ae · Apr 10, 2026 · 1 fileMessage 57 · ThinInformational 15Details
Commit message · matejcik
build(core): use portable sed language
that works on macos at least
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 changes a build script to use a more portable way of writing sed commands. It replaces a non-standard regular-expression feature with one that works on macOS. There is no security relevance: the change only affects how source code is preprocessed during firmware builds and does not alter runtime behavior or introduce any vulnerability.
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
AI analysis · Informational 24/100
This commit increases the secure monitor (secmont) stack size from 12 KB to 80 KB on Trezor hardware wallets and shifts memory layout to make room for it. A larger stack reduces the chance that a security-critical component runs out of memory and misbehaves, but the change itself is a routine resource adjustment, not a proven fix for an active attack. The commit does not describe any security bug or credit a researcher.
Lower-prioritychore(l10n): update and run blanker script [no changelog]by Michal Kazda · 4fc92b8e · Apr 10, 2026 · 3 filesMessage 77 · AdequateInformational 15Details
Commit message · Michal Kazda
chore(l10n): update and run blanker script [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
AI analysis · Informational 15/100
This commit is a routine localization update. It regenerates translation files so that some on-screen text strings are left blank for certain device models or languages while keeping them present for others. There is no code behavior change, no bug fix, and no security relevance.
Lower-prioritydocs: remove SECURITY.md to fall back to the organization defaultby Jan Komarek · f45b057b · Apr 9, 2026 · 2 filesMessage 67 · AdequateInformational 15Details
Commit message · Jan Komarek
docs: remove SECURITY.md to fall back to the organization default
67/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Names security-relevant behavior explicitly! No meaningful explanatory body
Why it was queued
documentation-only discount
AI analysis · Informational 15/100
This commit simply removes the repository's own SECURITY.md file and updates the README to point users to the organization's default security policy on GitHub instead. It is a documentation-only change with no code modifications and no direct security impact on the firmware or device.
Lower-priorityfix(tests): skip test on "THP" instead of on "eckhart"by M1nd3r · f09d834b · Apr 9, 2026 · 1 fileMessage 95 · StrongInformational 11Details
Commit message · M1nd3r
fix(tests): skip test on "THP" instead of on "eckhart"
- Skipped `test_apply_homescreen_jpeg_single_message` on all devices with THP, as the message is too big for the protocol.
[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
AI analysis · Informational 11/100
This commit only changes a test file. It adjusts which hardware models and protocol versions skip a test that sends a large JPEG homescreen image in a single message. The change is not a fix to product firmware and does not address a security vulnerability.
chore(eckhart, ui): make warning style for footer optional
- Warning_footer is not "footer" + "is_footer_warning" - Changes had to be propagated across other layouts for commonality.
[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
cryptography-sensitive pathboot or update path
AI analysis · Informational 19/100
This is a routine user-interface refactor for the Trezor hardware wallet firmware. It renames a parameter from 'warning_footer' to 'footer' and allows the footer text to be shown either as a warning (red/alert style) or as a normal informational hint. The change touches many UI test snapshots because screen layouts changed slightly, but there is no evidence of a security vulnerability or fix.
Eckhart should not have cancel option as a 'x' on the action bar but should instead be an option in the menu, like Delizia.
80/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
boot or update path
AI analysis · Informational 15/100
This is a user-interface consistency patch for the Trezor hardware wallet's 'Eckhart' design. It moves the 'cancel' option from a small 'X' button on the action bar into a menu, matching how the newer 'Delizia' design already works. There is no security bug being fixed here; it is purely a layout and navigation change.
✓ 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 is a routine cleanup of unused text strings in the Trezor firmware's translation system. It removes labels like 'Enter', 'Sending from account:', and 'Good to know' from generated translation files because they are no longer used anywhere in the user interface. There is no change to security logic, cryptography, or device behavior.
Lower-prioritychore(deps): bump `pyright` to version `1.1.408`by M1nd3r · 6e20287b · Apr 9, 2026 · 8 filesMessage 80 · StrongInformational 15Details
✓ 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
AI analysis · Informational 15/100
This commit removes the project's custom Nix-based packaging for the Pyright type-checking tool and stops using that custom package in the developer shell. It is a build/development tooling cleanup, not a security fix or vulnerability. There are no changes to the Trezor firmware code that runs on devices or to user-facing applications.
- update of tarballs for `nixpkgs` and `rustOverlay` for more recent ones - inlcudes update of `uv` to version `0.10.10` (from `0.7.14`) which fixes an issue with alternating revision number when updating `uv.lock` file (PRs from dependabot have `revision = 3`, PRs made by other contributors using the older `uv` have `revision = 2`) - note that `nixpkgs.llvmPackages_17` are no longer availble in the new `nixpkgs`
80/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
automated dependency-update discount
AI analysis · Informational 15/100
This is a routine build-environment maintenance update. It refreshes the versions of two Nix package collections used by Trezor's developer shell and updates the `uv` Python packaging tool from 0.7.14 to 0.10.10. The change does not touch the firmware code, wallet logic, cryptography, or any user-facing security feature. There is no indication of a security vulnerability being fixed.
Security candidatefix(style): update C-style to be compliant with clang-format 21.1.8by M1nd3r · 8bdfe004 · Apr 9, 2026 · 67 filesMessage 77 · AdequateInformational 15Details
Commit message · M1nd3r
fix(style): update C-style to be compliant with clang-format 21.1.8
- previous clang-format version was 17.0.6
[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 pathseed or entropy pathboot or update path
AI analysis · Informational 15/100
This commit is purely a code-style cleanup. It updates the project's C source files so they match the formatting rules of a newer version of the clang-format tool (version 21.1.8 instead of 17.0.6). The changes are limited to whitespace, line breaks, comment placement, and how macros and attributes are laid out. No program logic, security checks, or behavior were changed.
The user will be prompted to choose the method if it's unset on T3W1.
[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 14/100
This commit removes a default value for the backup_method setting used during wallet recovery on Trezor devices. Previously, if a recovery app did not explicitly choose a backup method, the device would default to 'Display' (showing shares on screen). After this change, the device will ask the user to choose instead. This is a small user-experience and behavior change, not a fix for a known security vulnerability.
Lower-prioritychore: propagate `BackupMethod` from `trezorctl` to recovery handlerby Roman Zeyde · 8f1d4baf · Apr 9, 2026 · 4 filesMessage 97 · StrongInformational 18Details
Commit message · Roman Zeyde
chore: propagate `BackupMethod` from `trezorctl` to recovery handler
Currently supports only display-based method. It will be used by the host in order to skip the choice layout, if the method is already known.
[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
AI analysis · Informational 18/100
This commit adds a way for the Trezor host software (trezorctl) to tell the device which backup/recovery method to use during wallet recovery. Right now only the existing display-based method is actually supported; the new parameter is mainly plumbing so the host can skip an extra user-choice screen in future versions. There is no obvious security bug in the change itself.
AI review queuedchore(deps): bump cryptography from 46.0.6 to 46.0.7by dependabot[bot] · e073774b · Apr 9, 2026 · 1 fileMessage 93 · StrongInformational 16Details
Commit message · dependabot[bot]
chore(deps): bump cryptography from 46.0.6 to 46.0.7
Bumps [cryptography](https://github.com/pyca/cryptography) from 46.0.6 to 46.0.7. - [Changelog](https://github.com/pyca/cryptography/blob/main/CHANGELOG.rst) - [Commits](https://github.com/pyca/cryptography/compare/46.0.6...46.0.7)
✓ 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
This is an automated dependency update by Dependabot that bumps the Python 'cryptography' library from version 46.0.6 to 46.0.7 in the project's lock file. The change only updates recorded download URLs and cryptographic hashes for the new version. There is no indication in the commit itself that this fixes a known security vulnerability, and no security advisory was supplied. It is best treated as a routine maintenance patch.
Lower-priorityfix(core): separate `0x` prefix when showing Ethereum addressby Roman Zeyde · 403c0df4 · Apr 9, 2026 · 4 filesMessage 62 · AdequateInformational 22Details
Commit message · Roman Zeyde
fix(core): separate `0x` prefix when showing Ethereum address
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 22/100
This commit changes how Ethereum addresses are visually displayed on Trezor devices. When the optional 'chunkify' feature is enabled, the '0x' prefix is now shown as a separate chunk from the rest of the address, making it easier for users to read and verify addresses. There is no direct security vulnerability being fixed here; it is a user-interface improvement that may slightly reduce the chance of user verification mistakes.
Lower-priorityfix(core): show label prefix during BLE pairingby Roman Zeyde · 6651be11 · Apr 9, 2026 · 4 filesMessage 88 · StrongInformational 17Details
Commit message · Roman Zeyde
fix(core): show label prefix during BLE pairing
Following https://satoshilabs.slack.com/archives/CL1D61PQF/p1775643967434449?thread_ts=1775632146.486079&cid=CL1D61PQF.
[no changelog]
88/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
AI analysis · Informational 17/100
This commit fixes a small user-interface bug in Trezor's Bluetooth pairing flow. Previously, if the device name was too long for the Bluetooth advertising packet, the user saw the full name on the Trezor screen while the truncated name was actually broadcast. Now the code returns the truncated name and displays that same shortened name to the user, so what they see matches what nearby devices see.
AI review queuedchore(tests,ethereum): add test fixtures for vault deposits.by PrisionMike · 625e6bad · Apr 8, 2026 · 3 filesMessage 72 · AdequateInformational 15Details
Commit message · PrisionMike
chore(tests,ethereum): add test fixtures for vault deposits.
[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
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit only adds new test cases for Ethereum vault deposits. It does not change any production firmware code, so it cannot introduce a security vulnerability in the device itself. The new tests check both valid deposits and cases that should be rejected, such as sending native ETH along with a deposit or a malformed transaction.
- Added Vault deposit flow. - Tests WIP. - changelog will be added after all 4 vault flows are done.
[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
Why it was queued
cryptography-sensitive pathsigning or wallet path
AI analysis · Informational 12/100
This commit adds a new user-facing feature to Trezor hardware wallets: clear signing support for ERC-4626 'vault deposit' transactions on Ethereum. It introduces code that recognizes a specific smart-contract function call, shows the user a friendly confirmation screen with the vault name and deposit amount, and only proceeds if safety checks pass. There is no indication in the commit that this fixes a security bug; it appears to be a normal feature addition.
chore(layout): make `verb_info` optional in `confirm_with_info`
[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 is a routine user-interface cleanup change. It makes one button label parameter optional across several Trezor device layouts and updates the Python helper that calls it. There is no security-relevant behavior change: the same screens are shown, only the internal plumbing for deciding whether to display an extra 'info' button is simplified.
✓ Descriptive subject✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
signing or wallet pathauthentication pathparser or protocol pathdocumentation-only discount
AI analysis · Informational 15/100
This commit is purely a documentation update for the Trezor firmware repository. It reorganizes existing documentation, adds new documentation for the Trezor-Host Protocol (THP), and moves Bitcoin signing and protocol v1 docs to new locations. No executable code, firmware logic, or security-sensitive behavior was changed.
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI analysis · Informational 15/100
This commit fixes a single grammar typo in a code comment. The word 'host' was changed to 'the host' in a protobuf message description. No code behavior, security logic, or functionality was changed.
✓ 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 only adds a human-readable comment to a protobuf message definition. It does not change any code behavior, protocol logic, or security properties.