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 is a routine GitHub Actions workflow fix. It changes which Slack webhook secret is used for nightly test failure notifications and removes a now-unnecessary safety check. There is no security vulnerability in the change itself.
This commit only improves a test report for Trezor's clear-signing feature. It changes how skipped test cases are listed in a nightly summary, showing each skipped case's source file and calldata size instead of just counting them by reaso…
This commit only changes test scripts and documentation for the Trezor firmware clear-signing test suite. It makes the tests run more registry cases—specifically those where the developer definitions do not yet have a display format—so the…
This commit updates French and Portuguese translation strings in the Trezor firmware and refreshes the translation signature metadata. The changes are purely wording adjustments (for example, replacing abbreviations like 'nº' with the full…
This commit changes a code-coverage tracking map inside the Trezor firmware from a claimed capacity of 1,048,576 entries down to 65,536 entries. The commit message says the old capacity was never truly that large because the heapless libra…
No cryptographic or secret-handling code changedNo input parsing, deserialization, or memory allocator changesChange is in a debug/test instrumentation module (coverage)
This commit is a routine update of translated user-interface text strings for the Trezor hardware wallet. It adds new translations (for example, warnings about exporting public keys and Solana blind-signing prompts), updates existing wordi…
This commit only adds new test cases for Ethereum clear-signing array parsing. It does not change any production code, so it cannot introduce a new security vulnerability on its own. The tests verify that malformed arrays (out-of-bounds of…
test-only changeno production code modifiedadds defensive test coverage for ABI decoding edge cases
This commit hardens the Trezor firmware's task scheduler against fault-injection attacks. These attacks use physical techniques like voltage glitches or laser pulses to trick the device into executing code with higher privileges than inten…
Fault-injection hardening (FIH) explicitly mentioned in commit title and code commentsPrivilege-level transition split into multiple guarded stepsAdded runtime invariant check that only the kernel task may run privileged
This commit only removes an unused parameter called `is_dynamic` from test helper functions and from test data in three test files. It does not change any production firmware code, wallet behavior, or security logic. It is a cleanup of the…
This commit updates the data-format definitions used by Trezor devices for Ethereum 'clear signing' (showing human-readable details of smart-contract interactions). It adds support for more numeric types, new path-step structures, and extr…
Schema expansion increases attack surface for future clear-signing parser logic, but no new parser logic is present in this commit.Replacement of NotImplementedError with InvalidFormatDefinition is a defensive change that turns unimplemented paths into a handled error rather than a crash/DoS vector.New optional fields and deprecated old fields (is_dynamic, lookup_address) are backward-compatible changes.
This is a bug-fix patch in the Python Trezor client library. It changes how the software probes whether a connected device uses the older protocol v1. Previously, the probe tried to read and throw away leftover data, but that read could ac…
No security-relevant signal in commit message or diffFix is described as a connectivity/functional bug, not a vulnerabilityNo mention of CVE, researcher credit, or security advisory
This commit is a user-interface improvement, not a security fix. It changes the language-change confirmation prompt on Trezor devices so that it shows a human-readable language name (for example, 'French') instead of a raw code like 'fr-FR…
This commit updates Spanish and French translation strings in the Trezor firmware and refreshes the translation signature file. The changes are purely textual wording adjustments (for example, changing 'Mostrar palab.' to 'Mostrar palabras…
This commit hardens cryptographic code in Trezor firmware against two potential side-channel leaks. First, it simplifies how a secret condition value is checked inside an assert statement so the compiler produces only one branch instead of…
Side-channel hardening in constant-time cryptographic primitivesReplacement of double-evaluation volatile assert with single-branch assertElimination of secret-dependent memory access in elliptic-curve scalar multiplication
This commit adds a new nightly automated testing workflow for Ethereum 'clear signing' on Trezor hardware wallets. It does not change any wallet firmware code that users run; it only adds test scripts, CI configuration, documentation, and …
This commit is a routine code cleanup. It removes a small helper function called keccak_32 from a shared crypto utility file and places an equivalent helper directly inside the only test file that still uses it. There is no change to how t…
This commit removes support for a cryptocurrency called SmartCash from Trezor hardware wallets. It deletes coin definitions, support entries, and a custom cryptographic curve used only by SmartCash. There is no security vulnerability being…
No security-relevant signals detectedPure feature removal / code cleanup
This commit removes all support for the Groestlcoin cryptocurrency from Trezor firmware. It deletes coin definitions, the custom Groestl hash algorithm code, related address/transaction handling, and tests. There is no security vulnerabili…
No security-relevant change: pure feature removalNo new attack surface introducedNo vulnerability patched or created
This commit removes all support for the Tezos cryptocurrency from Trezor firmware, software libraries, and documentation. It is a feature-removal change, not a security fix or vulnerability patch. There is no indication in the commit that …
This update reduces the longest allowed screen-lock timeout on older Trezor devices from about 6 days down to 149 hours (just over 6 days). It makes the legacy firmware behave the same as newer Trezor firmware and prevents users from setti…
Bounds enforcement added for a configurable security-relevant timeoutAlignment of security policy between legacy and core firmware variantsTest coverage added for boundary values above and below new maximum
- Send nightly clear-signing failures via SLACK_HW_TESTS_WEBHOOK, the secret core-hw.yml already uses, instead of a separate SLACK_CLEAR_SIGNING_WEBHOOK that was never set up. - Drop the check that skipped the notification when the secret was missing, matching core-hw.yml.
[no changelog]
90/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
Why it was queued
signing boundarysigning or wallet pathdocumentation-only discount
AI analysis · Informational 15/100
This is a routine GitHub Actions workflow fix. It changes which Slack webhook secret is used for nightly test failure notifications and removes a now-unnecessary safety check. There is no security vulnerability in the change itself.
Lower-priorityci: less verbose membrowse commentby Martin Milata · 662cf399 · Nov 20, 2026 · 2 filesMessage 72 · AdequateTriage 0Details
Commit message · Martin Milata
ci: less verbose membrowse comment
- more compact formatting - not posted if there are no size changes
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 candidatetest(clear_signing): name the skipped casesby PrisionMike · 98deb5b0 · Nov 20, 2026 · 2 filesMessage 90 · StrongInformational 15Details
Commit message · PrisionMike
test(clear_signing): name the skipped cases
- List every skipped case in the summary, with its registry test file and calldata size, not only the count per reason, e.g. which descriptor has calldata over 6144 bytes.
[no changelog]
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
90/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
Why it was queued
signing boundarysigning or wallet path
AI analysis · Informational 15/100
This commit only improves a test report for Trezor's clear-signing feature. It changes how skipped test cases are listed in a nightly summary, showing each skipped case's source file and calldata size instead of just counting them by reason. There is no change to firmware, wallet logic, cryptography, or any user-facing security behavior.
Security candidatetest(clear_signing): run the cases without display formatby PrisionMike · 05c1f4ef · Nov 20, 2026 · 5 filesMessage 95 · StrongInformational 15Details
Commit message · PrisionMike
test(clear_signing): run the cases without display format
- Run the registry cases that the dev definitions have no display format for, of all providers, instead of skipping them. The firmware blind-signs them (or clear-signs them with a built-in format), and the summary lists the blind-signed ones as "blind-signed, no format": the cases that the definitions do not cover.
[no changelog]
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
Why it was queued
signing boundarysigning or wallet path
AI analysis · Informational 15/100
This commit only changes test scripts and documentation for the Trezor firmware clear-signing test suite. It makes the tests run more registry cases—specifically those where the developer definitions do not yet have a display format—so the nightly summary can list them as 'blind-signed, no format.' It does not change the firmware itself, the signing logic, or any user-facing behavior. There is no security fix or vulnerability here.
Lower-prioritychore(core): update fixturesby Michal Kazda · 2cf3e696 · Nov 20, 2026 · 1 fileMessage 47 · ThinTriage 0Details
Commit message · Michal Kazda
chore(core): update fixtures
[no changelog]
47/100 · ThinMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope! No meaningful explanatory body
AI review queuedfix(translations): fix failing tutorial test in FR and small update to PTby Michal Kazda · 29cbc419 · Nov 20, 2026 · 3 filesMessage 72 · AdequateInformational 15Details
Commit message · Michal Kazda
fix(translations): fix failing tutorial test in FR and small update to PT
[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 and Portuguese translation strings in the Trezor firmware and refreshes the translation signature metadata. The changes are purely wording adjustments (for example, replacing abbreviations like 'nº' with the full word 'número' and shortening a French tutorial prompt). There is no code change, no security fix, and no behavior change beyond what text is displayed to users.
Lower-prioritychore(core): continue anyway on all layoutsby Vojtěch Nevřela · 6d3c020f · Nov 20, 2026 · 3 filesMessage 57 · ThinTriage 0Details
Commit message · Vojtěch Nevřela
chore(core): continue anyway on all layouts
[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
translation-only discount
Lower-prioritytest(python): include tests for click v8.3, v8.4, and v8.5by M1nd3r · 204445de · Nov 19, 2026 · 1 fileMessage 72 · AdequateTriage 0Details
Commit message · M1nd3r
test(python): include tests for click v8.3, v8.4, and v8.5
[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
- Reduced to 64 K after heapless update. Note that the capacity was never actually 1 M entries, it would silently overflow with heapless 0.9.2.
[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
memory safety
AI analysis · Informational 10/100
This commit changes a code-coverage tracking map inside the Trezor firmware from a claimed capacity of 1,048,576 entries down to 65,536 entries. The commit message says the old capacity was never truly that large because the heapless library version in use would silently overflow. The change only affects internal test/debug instrumentation and is not a security fix for user funds or device secrets. It is marked with '[no changelog]', meaning the project did not treat it as a user-visible change.
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
AI review queuedchore(translations): sync Crowdin translationsby Thalarion · b2e8b5e6 · Nov 18, 2026 · 7 filesMessage 57 · ThinInformational 15Details
Commit message · Thalarion
chore(translations): sync Crowdin translations
[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 pathtranslation-only discountsecond-pass: security-sensitive path
AI analysis · Informational 15/100
This commit is a routine update of translated user-interface text strings for the Trezor hardware wallet. It adds new translations (for example, warnings about exporting public keys and Solana blind-signing prompts), updates existing wording, and refreshes the cryptographic signature file that verifies the translation files. There are no code changes, no executable logic changes, and no security fixes or vulnerabilities introduced.
Lower-priorityci(core): name main reference builds explicitlyby Michal Kazda · 3e62e02a · Nov 18, 2026 · 1 fileMessage 80 · StrongTriage 0Details
Commit message · Michal Kazda
ci(core): name main reference builds explicitly
- set run-name for push-to-main runs instead of the head commit message - other events keep GitHub's default run name
[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
documentation-only discount
Lower-prioritytest(python): include Python 3.15 in testsby M1nd3r · e537e714 · Nov 18, 2026 · 4 filesMessage 67 · AdequateTriage 0Details
Commit message · M1nd3r
test(python): include Python 3.15 in tests
[no changelog]
67/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Mentions testing or verification! No meaningful explanatory body
Lower-prioritytest(python): add test for discarding stale packetsby M1nd3r · 57b905e5 · Nov 18, 2026 · 1 fileMessage 72 · AdequateTriage 0Details
Commit message · M1nd3r
test(python): add test for discarding stale packets
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-prioritychore(core): update fixturesby Michal Kazda · f8ce4f40 · Nov 18, 2026 · 1 fileMessage 47 · ThinTriage 0Details
Commit message · Michal Kazda
chore(core): update fixtures
[no changelog]
47/100 · ThinMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope! No meaningful explanatory body
Lower-prioritychore(translations): apply new blanking rulesby Michal Kazda · 3cfc86fe · Nov 18, 2026 · 3 filesMessage 72 · AdequateTriage 0Details
Commit message · Michal Kazda
chore(translations): apply new blanking rules
- adden new blanking rules - executed new blanking rules
[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
translation-only discount
Security candidatetest(clear_signing): edge cases for arraysby PrisionMike · dcdf3068 · Nov 18, 2026 · 1 fileMessage 67 · AdequateInformational 12Details
Commit message · PrisionMike
test(clear_signing): edge cases for arrays
[no changelog]
67/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
signing boundarysigning or wallet path
AI analysis · Informational 12/100
This commit only adds new test cases for Ethereum clear-signing array parsing. It does not change any production code, so it cannot introduce a new security vulnerability on its own. The tests verify that malformed arrays (out-of-bounds offsets, truncated data, oversized lengths) are rejected rather than parsed incorrectly.
refactor(core): harden task switching against fault injections
[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
secure hardware boundarydefensive validation
AI analysis · High 70/100
This commit hardens the Trezor firmware's task scheduler against fault-injection attacks. These attacks use physical techniques like voltage glitches or laser pulses to trick the device into executing code with higher privileges than intended. The change ensures the processor starts in a lower-privilege state before deciding whether to elevate the kernel task, and adds a safety check that halts the device if a non-kernel task somehow ends up privileged. It is a defensive hardening patch rather than a fix for a known remotely exploitable bug.