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.
build(core): avoid unused variable warning in rng_fill_buffer_strong
When neither USE_OPTIGA nor USE_TROPIC, rng_fill_buffer_strong is just rng_fill_buffer with extra steps. Make that explicit in code; otherwise the `dst` variable is never read from and we get a warning under clang.
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
Why it was queued
entropy or randomnessseed or entropy path
AI analysis · Informational 15/100
This is a minor build cleanup. A developer added a compile-time branch so that when neither the Optiga nor Tropic security chips are used, the 'strong' random-number wrapper simply calls the normal random-number function and returns. The only reason for the change is to silence a compiler warning about an unused variable. There is no functional security change.
build(core): replace -fsingle-precision-constant with explicit casts
The option -fsingle-precision-constant is unsupported in clang. Instead, I'm adding -Wdouble-promotion (no hits in the codebase) and -Wfloat-conversion (fixing the warning sites).
-fsingle-precision-constant ensures that all double literals without 'f' suffix are treated as floats. But we don't care about literals per se, we care about silent double promotions for calculations. The new set of warnings is portable and more closely matches the intent.
85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Security candidatefeat(ethereum): allow approve and transfer to send ethby PrisionMike · e785f6c6 · Jul 2, 2026 · 8 filesMessage 62 · AdequateModerate 64Details
Commit message · PrisionMike
feat(ethereum): allow approve and transfer to send eth
[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 pathsigning or wallet path
AI analysis · Moderate 64/100
This commit changes how Trezor devices display Ethereum transactions when someone sends ERC-20 token approval or transfer calls that also include native ETH. Previously, the device might not clearly show the attached ETH, so a user could unknowingly approve sending tokens plus real ETH. The patch makes the device surface that native ETH amount on the confirmation screen. It is a defensive fix that improves transparency rather than introducing a vulnerability.
✓ 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 pathtranslation-only discountsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit only updates translated text strings in the Trezor firmware. It changes wording in Czech, German, Spanish, French, and Portuguese translation files, plus the translation signature metadata. There are no code changes, no security fixes, and no behavior changes.
AI review queuedchore(translations): sync Crowdin fixing French failing testsby Michal Kazda · 1c84feca · Jul 2, 2026 · 3 filesMessage 72 · AdequateInformational 15Details
Commit message · Michal Kazda
chore(translations): sync Crowdin fixing French failing tests
[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 pathtranslation-only discountsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit updates translation files for Czech and French, plus the corresponding signed metadata. It changes wording on device screens (for example, how a 'hold to confirm' button is labeled and how a backup-fragment title is formatted) and refreshes the cryptographic fingerprint that protects those translations from tampering. There is no code change and no security vulnerability is present in the diff.
AI review queuedchore(translations): sync Crowdin fixing more French failing testsby Michal Kazda · 13b41359 · Jul 2, 2026 · 2 filesMessage 72 · AdequateInformational 15Details
Commit message · Michal Kazda
chore(translations): sync Crowdin fixing more French failing tests
[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 pathtranslation-only discountsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit updates French translation strings in the Trezor firmware and refreshes the corresponding translation signature metadata. The changes are purely cosmetic wording adjustments for on-screen text (for example, changing one French phrasing of a backup-recovery prompt to match another variant). There is no code behavior change, no cryptographic change, and no security fix.
✓ 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 pathtranslation-only discountsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit is a routine update of translated user-interface text for Trezor hardware wallets. It changes wording in Czech, German, Spanish, French, and Portuguese translation files, plus the translation signature metadata. There is no code change, no security fix, and no functional behavior change.
feat(clear_signing, ethereum) add new provider names.
[no changelog]
50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing boundarysigning or wallet path
AI analysis · Informational 15/100
This commit is a routine feature update for Trezor's Ethereum 'clear signing' feature. It adds human-readable names for more DeFi and staking providers (like Lido, Morpho, Kiln) and makes the address lookup aware of which blockchain network (chain ID) an address belongs to. There is no security vulnerability or bug fix here.
AI review queuedfeat(core): set tropic configurationby Martin Pastyřík · 4a93242c · Jul 2, 2026 · 28 filesMessage 80 · StrongLow 32Details
Commit message · Martin Pastyřík
feat(core): set tropic configuration
Set the configuration of Tropic to the value excpected by the firmware.
The current version of tropic configuration is stored in slot 6 of Tropic R memory data. During the setting process, slot 7 is temporarily used to store a backup of the configuration version.
Also refactor tropic configuration from prodtest into firmware and enable sensors setting in model_server.
[no changelog]
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
second-pass: unusually broad change
AI analysis · Low 32/100
This commit moves the configuration settings for the Tropic secure chip out of the production-test tool and into the main firmware. At boot, the device now checks whether the Tropic chip's configuration matches the version expected by the firmware, and can update or repair it if needed. It also adds a version number stored in a Tropic memory slot and uses a backup slot during updates. The change is a feature/refactoring patch; there is no direct evidence in the commit that it fixes a known security vulnerability, but misconfiguration of a security chip is a security-sensitive operation.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
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
Lower-priorityfeat(core/prodtest): Reboot Tropic in tropic-set-sensors.by Andrew Kozlik · 9bad5744 · Jul 2, 2026 · 4 filesMessage 62 · AdequateTriage 0Details
Commit message · Andrew Kozlik
feat(core/prodtest): Reboot Tropic in tropic-set-sensors.
62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Mentions testing or verification! No meaningful explanatory body
- so that the text fits on one line in Bolt layout
[no changelog]
84/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Explains rationale or failure mode
fix(core): raise `wire.Error` from `EvoluIndexManagement` handler
Otherwise, it is sent to the host as a `FirmwareError`, which is usually used for unexpected errors (e.g. out-of-memory errors).
See also https://docs.trezor.io/trezor-firmware/core/misc/exceptions.html.
[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
feat(core): add chunkify support for Solana SignTx
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 pathsigning or wallet path
AI analysis · Informational 18/100
This commit adds an optional user-interface feature for Solana transactions on Trezor hardware wallets. When enabled, long Solana addresses are shown on the device screen in smaller groups of characters (chunks of 4) instead of one long string, making them easier for users to read and verify. There is no indication this change fixes a security vulnerability; it is a usability improvement.
AI review queuedfeat(core): sign rotation index into Evolu sign registrationby Martin Pastyřík · 4db3a69d · Jul 1, 2026 · 8 filesMessage 77 · AdequateInformational 24Details
Commit message · Martin Pastyřík
feat(core): sign rotation index into Evolu sign registration
This enables the Quota Manager to distinguish the indices and store the current index.
[no changelog]
77/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 24/100
This commit updates the Trezor firmware's Evolu (delegated identity) registration signing feature so that the device now includes a 'rotation index' in the signed registration request. The rotation index tells the Quota Manager which version of the device's delegated identity key was used. The signature format was also bumped from V1 to V2 by adding the rotation index into the signed data. This is a feature enhancement, not a fix for an obvious security vulnerability, but it touches cryptographic signing and identity-key rotation, which are security-sensitive areas.