CommitWatch RSS
TZ
← All projectsTrezor

Trezor firmware

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

BitcoinHardware walletsNormal
Source repository ↗
Repository coverage

2661 commits in the local evidence base

Every captured commit receives deterministic security triage and a separate communication-quality score. Security candidates and broader second-pass signals receive full-patch Ollama analysis.

916security candidates311second-pass queue1354AI analyses
336commits · 30 days
588commits · 60 days
1363commits · 180 days
2650commits · 365 days
Backfill bands
Aug 5 → Feb 61298 seen115 candidatesComplete
Feb 6 → Jun 6775 seen58 candidatesComplete
Jun 6 → Jul 6217 seen13 candidatesComplete
Jul 6 → Aug 5360 seen54 candidatesComplete
Commit communication

Does the history explain itself?

Message quality measures whether a commit identifies its scope, purpose, rationale, testing, and supporting references. It does not change the security-severity score.

66/100 average clarity
473Strong · 80–100
1321Adequate · 60–79
862Thin · 40–59
5Opaque · 0–39
Read the scoring rubric →
Developer activity

Who is changing the project?

Public Git author strings; identities are not independently verified.

DeveloperCommitsCandidatesAnalyzedHigh riskMessage avg.
PrisionMike945982273
Andrew Kozlik712436265
Roman Zeyde572177253171
tychovrahe292104125161
Jakub Janků22917182
Martin Pastyřík23811173
cepetr19682103059
Ioan Bizău23076140059
obrusvit21376107064
M1nd3r20671105071
Lukas Bielesch846771067
Martin Milata1744677063
Analysis record

Published AI watches

Last scanned 48 minutes ago

Informational 18 AI analysisMessage 57 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

chore(core): remove sha1 from regular FW

This commit removes the SHA-1 hashing function from the regular Trezor firmware. SHA-1 is an old, weak hash algorithm that is no longer considered secure for sensitive uses. The change deletes the code that exposes SHA-1 to apps running on…

Removal of a deprecated cryptographic primitive (SHA-1) from the firmware API surfaceReduction of attack surface and prevention of future misuse of a collision-vulnerable hashNo direct vulnerability patch or memory-safety bug is present in the diff
16d15774by M1nd3r+0−2006 files
No security note in commit
Open full analysis →Source commit ↗
Low 27 AI analysisMessage 62 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

refactor(crypto): pass static public key to `noise_xxpsk3_*_init()`

This commit changes how a cryptographic library sets up secure connections. Previously, the code automatically calculated the public key from the private key. Now, the caller must provide the public key directly. This is a code-quality ref…

Cryptographic key handling changed: public key is now supplied rather than derivedPotential reduction of key-mismatch risk if caller provides correct public keyNew null-pointer check added for static_public_key
1b3128a4by Ondřej Vejpustek+20−92 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 57 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

refactor(crypto): change order of parameters

This commit simply reorders the arguments of an internal function called dh() and updates every place that calls it. The actual math and security behavior are unchanged; it is a code cleanup with no security effect.

33a119eeby Ondřej Vejpustek+15−151 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 47 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

refactor(crypto): prefix enums

This commit simply renames two groups of internal status labels (called enums) in the Trezor firmware's cryptographic code. The old names like WAITING_FOR_REQUEST1 were shared between two different parts of the code, so the developer gave …

f1c74046by Ondřej Vejpustek+26−222 files
No security note in commit
Open full analysis →Source commit ↗
Low 37 AI analysisMessage 57 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

fix(crypto): prevent calling `memzero(NULL, ...)`

This commit fixes three places in the Trezor firmware's cryptographic code where a memory-clearing function could be called with a NULL pointer. In practice, passing NULL to memzero is harmless on Trezor's platform (it does nothing), but i…

NULL pointer passed to memory-zeroing helper in cryptographic codeUndefined behavior in C standard library contractDefensive hardening in Noise protocol implementation
0394e934by Ondřej Vejpustek+11−51 file
No security note in commit
Open full analysis →Source commit ↗
Informational 18 AI analysisMessage 62 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

refactor(crypto): return remote static key from `noise_xxpsk3_*_handle_*()`

This commit is a code cleanup (refactor) for the cryptographic handshake code used in Trezor devices. It changes how the other party's long-term public key is returned to the caller: instead of storing it inside an internal state structure…

Removal of long-term public key storage from internal handshake stateCaller-supplied output buffer for remote static public key reduces internal secret retentionError-path memzero of returned key material on failure
3ead1aa6by Ondřej Vejpustek+79−423 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 62 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

refactor(xtask): rename ProjectProfile to ProjectConfig

This commit is a simple rename from 'ProjectProfile' to 'ProjectConfig' in two Rust source files. It only changes variable names, struct names, and error messages. There is no change to program logic, security behavior, or how data is hand…

581b37bcby cepetr+18−182 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 47 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

refactor(xtask): introduce ResolvedBuildArgs

This commit is a straightforward internal code refactor in Trezor's build tooling. It introduces a new ResolvedBuildArgs structure that centralizes default values for command-line build options before they are used. There is no change to u…

c24d1be8by cepetr+99−295 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 57 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

refactor(xtask): make build args tristate

This commit is a straightforward internal refactor of the Trezor firmware build tool's command-line argument handling. It changes many on/off flags from plain booleans to optional booleans so they can explicitly be set to true, false, or l…

271e249aby cepetr+57−561 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 57 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

refactor(xtask): introduce build options

This commit is a straightforward internal code reorganization in Trezor's build tooling. It moves build-option definitions from one Rust source file to a new module and adds the ability to load those options from a configuration file. Ther…

75085e2aby cepetr+275−2007 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 57 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

feat(xtask): introduce build presets

This commit is a developer tooling change for the Trezor firmware build system. It introduces 'build presets'—named configuration bundles stored in TOML files—so developers can select common build settings with a single command-line flag i…

eefe8f7fby cepetr+397−419 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 62 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

feat(xtask): upgrade manifest.yaml for tf-tools 0.3.0

This commit is a routine update to a build-system manifest file used by Trezor's internal tooling. It reorganizes and re-labels feature flags (for example, moving options between 'Features', 'Debugging', and 'Signing' groups and simplifyin…

57b28b89by cepetr+86−1351 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 62 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

feat(core): add tf-tools 0.3.1+ configuration file

This commit adds a single configuration file for a Trezor developer tool (a VS Code extension). It only points the tool to existing folders in the repository and contains no executable code, no secrets, and no changes to firmware behavior.…

e554f618by cepetr+8−01 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 62 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

refactor(xtask): rename ResolvedBuild to ResolvedBuildFeatures

This commit is a simple internal code cleanup: it renames a Rust data structure called ResolvedBuild to ResolvedBuildFeatures and updates the places that use it. There are no functional changes, no security fixes, and no changes to how the…

aaa2780bby cepetr+5−52 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 57 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

fix(core): fix up clippy warnings in storage.rs

This is a tiny code cleanup commit that replaces two calls to `ptr::null()` with Rust's `unwrap_or_default()` to silence automated Clippy lint warnings. It does not change what value is produced (still a null pointer when no salt is provid…

62354461by cepetr+2−21 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 47 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

refactor(xtask): simplify dependencies

This commit is a straightforward internal code cleanup in Trezor's build tooling. It moves a data structure and two helper methods from one Rust source file to another and updates callers accordingly. There is no change to user-facing beha…

6268349fby cepetr+9−193 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 47 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

docs: add xtask documentation

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

4879dababy cepetr+296−03 files
No security note in commit
Open full analysis →Source commit ↗
Informational 17 AI analysisMessage 57 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

feat(xtask): introduce project-toml build-options

This commit is a build-system refactoring for Trezor firmware. It moves the mapping of command-line build options to Rust/cargo features out of hard-coded Rust logic and into per-project TOML files. It also adds a small change so debug bui…

Build-option mapping now lives in project.toml files, increasing the attack surface for supply-chain/build-configuration tamperingMakefile change automatically enables debug-link for PYOPT=0 debug buildsValidation added to reject storage_insecure_testing_mode in production builds
d44de007by cepetr+681−40817 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 57 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

ci(core): fix nightly ARM emulator filename

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

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

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

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

06cab32bby Martin Milata+1−11 file
No security note in commit
Open full analysis →Source commit ↗
Repository ledger

Explore captured commits

Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.

Lower-priorityci: hw: zizmor lintsby Martin Milata · 4ca304f1 · Jun 9, 2026 · 1 fileMessage 40 · ThinTriage 0Details
Commit message · Martin Milata

ci: hw: zizmor lints

40/100 · ThinMessage clarity
✓ Subject identifies a change✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
documentation-only discount
Lower-priorityci: hw: adjust T3W1 setup for THPby Martin Milata · 86bad529 · Jun 9, 2026 · 4 filesMessage 57 · ThinTriage 0Details
Commit message · Martin Milata

ci: hw: adjust T3W1 setup for THP

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Lower-priorityrefactor(core): display driver suspend API improvementby bleska · 9548570b · Jun 9, 2026 · 3 filesMessage 85 · StrongTriage 0Details
Commit message · bleska

refactor(core): display driver suspend API improvement

Remove `bool touch_wakeup_enabled` from `display_suspend()` and
`display_resume()`. The parameter was too specific to touch-panel
hardware and leaked touch wakeup policy into the display driver.

The branching between light-suspend and full deinit is moved to
`suspend_io.c`, which is the appropriate level of abstraction.
`display_resume()` now handles both cases internally: light-resume
when the driver is still initialized, and full reinit when it was
fully deinitialized during suspend.

[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
Lower-priorityci(core): move `build_prodtest_emu` to `core_emu` jobby Roman Zeyde · 349bd5c4 · Jun 8, 2026 · 1 fileMessage 77 · AdequateTriage 0Details
Commit message · Roman Zeyde

ci(core): move `build_prodtest_emu` to `core_emu` job

It's not related to `core_firmware` job.

[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
documentation-only discount
Lower-priorityci(core): use `core/Makefile` to run upgrade testsby Roman Zeyde · 9f366350 · Jun 8, 2026 · 2 filesMessage 99 · StrongTriage 0Details
Commit message · Roman Zeyde

ci(core): use `core/Makefile` to run upgrade tests

Otherwise, `TESTOPTS` are not propagated.

[no changelog]

99/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Explains rationale or failure mode✓ Mentions testing or verification
Lower-prioritychore(trezor-client): bump version to 0.1.6by Tomas Martykan · 40adf089 · Jun 8, 2026 · 2 filesMessage 57 · ThinTriage 0Details
Commit message · Tomas Martykan

chore(trezor-client): bump version to 0.1.6

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Lower-priorityci(core): move cargo audit and cargo vet to separate jobby Martin Milata · cb48befa · Jun 8, 2026 · 1 fileMessage 62 · AdequateTriage 0Details
Commit message · Martin Milata

ci(core): move cargo audit and cargo vet to separate job

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
documentation-only discount
Lower-prioritychore(core): remove unused translation toolsby obrusvit · e76597a7 · Jun 8, 2026 · 7 filesMessage 72 · AdequateTriage 0Details
Commit message · obrusvit

chore(core): remove unused translation tools

- these scripts are unmaintained and unused

[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 candidaterefactor(core): enforce layout scoping for more Rust layoutsby Roman Zeyde · bc28535c · Jun 8, 2026 · 13 filesMessage 85 · StrongLow 26Details
Commit message · Roman Zeyde

refactor(core): enforce layout scoping for more Rust layouts

Following https://github.com/trezor/trezor-firmware/pull/6812.

[no changelog]

85/100 · StrongMessage clarity
✓ Specific, 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
Why it was queued
cryptography-sensitive pathboot or update path
AI analysis · Low 26/100

This commit is a follow-up code cleanup that wraps more on-screen user-interface helpers in a new 'layout context' pattern. It changes type annotations from LayoutObj to LayoutContext and converts several synchronous-looking wrapper functions into async functions that use Python 'with' blocks. There is no direct evidence in the commit of a fixable security bug; it appears to be a defensive refactoring to make UI resource lifetimes more predictable across Trezor firmware models.

Lower-prioritychore: add internal auditsby obrusvit · 49858e7d · Jun 8, 2026 · 3 filesMessage 62 · AdequateTriage 0Details
Commit message · obrusvit

chore: add internal audits

- ported the "Reviewed: Yes" rows from Notion

[no changelog]

62/100 · AdequateMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope✓ Provides an explanatory body
Lower-prioritychore: utilize cargo-vetby obrusvit · aad3a128 · Jun 8, 2026 · 6 filesMessage 75 · AdequateTriage 0Details
Commit message · obrusvit

chore: utilize cargo-vet

- tool and CI setup
- no review imports yet
- vendored crates (pareen, qrcodegen, tjpdec) are treated as imported
crates
- `cargo-vet` command should pass in this commit because all
dependencies are exempted

[no changelog]

75/100 · AdequateMessage clarity
✓ Subject identifies a change✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Explains rationale or failure mode
Lower-prioritychore: add import sources to cargo vetby obrusvit · 2afe0115 · Jun 8, 2026 · 2 filesMessage 88 · StrongTriage 0Details
Commit message · obrusvit

chore: add import sources to cargo vet

- picking Google, Mozilla and ZCash, Bytecode alliance and ISRG
- status: 30 audited, 2 partially audited, 68 exempted crates

Commands to achieve the results:
cargo vet import google
https://raw.githubusercontent.com/google/rust-crate-audits/main/audits.toml
cargo vet import mozilla
https://raw.githubusercontent.com/mozilla/supply-chain/main/audits.toml
cargo vet import bytecodealliance
https://raw.githubusercontent.com/bytecodealliance/wasmtime/main/supply-chain/audits.toml
cargo vet import isrg
https://raw.githubusercontent.com/divviup/libprio-rs/main/supply-chain/audits.toml
cargo vet import zcash
https://raw.githubusercontent.com/zcash/rust-ecosystem/main/supply-chain/audits.toml
cargo vet
cargo vet prune

[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
Lower-prioritychore: trust regexby obrusvit · a7f7d780 · Jun 8, 2026 · 3 filesMessage 40 · ThinTriage 0Details
Commit message · obrusvit

chore: trust regex

- cargo vet trust regex

[no changelog]

40/100 · ThinMessage clarity
✓ Subject identifies a change✓ Uses a recognizable type or scope! No meaningful explanatory body
Lower-prioritychore: add notes for incomplete internal auditsby Martin Milata · 7cc8bf5f · Jun 8, 2026 · 1 fileMessage 72 · AdequateTriage 0Details
Commit message · Martin Milata

chore: add notes for incomplete internal audits

- added partial reviews from Notion as exemption notes

[no changelog]

72/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
Lower-priorityci: remove cargolock_check prebuild workflowby obrusvit · 143637e2 · Jun 8, 2026 · 1 fileMessage 92 · StrongTriage 0Details
Commit message · obrusvit

ci: remove cargolock_check prebuild workflow

- no longer needed because we now use cargo-vet
- the reviews are now tracked in audits.toml in this repo and not in an
external Notion page

[no changelog]

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
documentation-only discount
Security candidatefix(core): fix firmware build with extapp supportby cepetr · c2c6833e · Jun 8, 2026 · 6 filesMessage 57 · ThinInformational 18Details
Commit message · cepetr

fix(core): fix firmware build with extapp support

[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
cryptography-sensitive path
AI analysis · Informational 18/100

This commit fixes a firmware build problem when a feature called 'extapp support' is enabled. It changes which source files are compiled and adjusts code guards so that certain applet-related code is only included when both applets and kernel mode are active. There is no direct evidence this fixes a security vulnerability; it appears to be a build-system correction.

Lower-prioritychore(python): `DebugLinkLayout` is no longer sentby Roman Zeyde · 8610a088 · Jun 8, 2026 · 1 fileMessage 77 · AdequateTriage 0Details
Commit message · Roman Zeyde

chore(python): `DebugLinkLayout` is no longer sent

It was deprecated in 0e8dcbb498bac95997e70aa8c3ea4d522779c7c2.

[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
Lower-prioritychore(python): stop sending `DebugLinkResetDebugEvents`by Roman Zeyde · f39ba648 · Jun 8, 2026 · 1 fileMessage 77 · AdequateTriage 0Details
Commit message · Roman Zeyde

chore(python): stop sending `DebugLinkResetDebugEvents`

It was deprecated in 0e8dcbb498bac95997e70aa8c3ea4d522779c7c2.

[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
Security candidatechore(python): stop sending `DebugLinkWatchLayout`by Roman Zeyde · 510d0a92 · Jun 8, 2026 · 14 filesMessage 77 · AdequateInformational 15Details
Commit message · Roman Zeyde

chore(python): stop sending `DebugLinkWatchLayout`

It was deprecated in 0e8dcbb498bac95997e70aa8c3ea4d522779c7c2.

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

This commit removes calls to an old, already-deprecated debug-only feature named DebugLinkWatchLayout from the Python test library and test scripts. It is a cleanup change affecting only testing and developer tooling, not the firmware that runs on the Trezor device or any user-facing security behavior.

Lower-prioritychore(core): support more Bitcoin test networksby Roman Zeyde · 0d232c16 · Jun 8, 2026 · 1 fileMessage 82 · StrongTriage 0Details
Commit message · Roman Zeyde

chore(core): support more Bitcoin test networks

Note: following d2e47ca87b68d571e04286ba807aad98245eebc8, we use "Testnet" for `testnet4`.

[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
AI review queuedchore(rust): remove unneeded `script_type` from Trezor::get_public_key()by Roman Zeyde · a87197ed · Jun 8, 2026 · 4 filesMessage 62 · AdequateInformational 18Details
Commit message · Roman Zeyde

chore(rust): remove unneeded `script_type` from Trezor::get_public_key()

[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 · Informational 18/100

This is a small cleanup change in the Rust Trezor client library. It removes an unused `script_type` parameter from the `get_public_key()` function and its callers. The parameter was being set in the request to the Trezor device, but the device does not actually need or use it for this operation. There is no security vulnerability here—just code simplification.

Lower-priorityfeat(core): introduce secret_reset functionby tychovrahe · d9812452 · Jun 8, 2026 · 4 filesMessage 57 · ThinTriage 0Details
Commit message · tychovrahe

feat(core): introduce secret_reset function

[no changelog]

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Security candidatefix(core/bootloader_ci): fix jumping to fw from CI bootloaderby tychovrahe · dc92e68c · Jun 8, 2026 · 1 fileMessage 62 · AdequateLow 31Details
Commit message · tychovrahe

fix(core/bootloader_ci): fix jumping to fw from CI bootloader

[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
update trustboot or update path
AI analysis · Low 31/100

This commit fixes the CI (continuous integration) bootloader so it correctly hands control over to the main firmware after running. It adds missing security-monitor verification, calls a secret-handoff routine before jumping, and passes startup arguments to the next stage. The change appears to be a bug fix for an internal test/CI bootloader rather than a fix for an exploitable security flaw in production devices.

Lower-prioritychore(core): use backup ram in BLE driver conditionallyby tychovrahe · 0351cd3d · Jun 8, 2026 · 1 fileMessage 62 · AdequateTriage 0Details
Commit message · tychovrahe

chore(core): use backup ram in BLE driver conditionally

[no changelog]

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Security candidaterefactor(core): extract pin configuration from NRF driver to board definitionby tychovrahe · 93ab3c69 · Jun 8, 2026 · 6 filesMessage 62 · AdequateInformational 15Details
Commit message · tychovrahe

refactor(core): extract pin configuration from NRF driver to board definition

[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
access control
AI analysis · Informational 15/100

This commit is a straightforward code cleanup: it moves hard-coded pin, clock, and interrupt settings for the Nordic (NRF) radio chip out of the driver code and into board-specific header files. The actual electrical connections and behavior stay the same for the existing boards (revA, revB, revC). It also fixes one minor interrupt-clearing macro name to match the current HAL convention. There is no user-facing change and no security fix.