CommitWatch RSS
Continuous public-repository analysis

Open source.
Not open secrets.

We watch what security-critical projects change—then translate the code into clear, independent intelligence anyone can understand.

Explore the watch feed ↓See how scoring works →
24Projects watched
17490Commits captured
17117AI analyses
88High-risk findings · 30d
The watch feed

Changes worth understanding

AI analysis is published as generated. Community notes appear after human validation.

17117 analyses
Highest risk·RSS
Informational 15 AI analysisMessage 57 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

refactor(tests): refactor `verify_cert_chain()`

This commit is a code cleanup in the test suite. It merges two nearly identical certificate-verification routines into one shared helper and removes duplicated code. There is no change to the actual security checks performed, no change to …

c94d5dcbby Ondřej Vejpustek+30−531 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 67 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

refactor(tests): import HSM keys

This commit only moves existing test-only public keys from a test file into a shared internal module so they can be reused. It does not change any firmware behavior, add new keys, or alter any security logic. There is no apparent security …

5230821bby Ondřej Vejpustek+6−171 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 57 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

feat(tests): add `test_authenticate_device_mcu()`

This commit only adds a new automated test that checks whether Trezor hardware devices can prove their identity using an MCU-based digital signature. It does not change any firmware code that runs on the device, nor does it fix or introduc…

7f562942by Ondřej Vejpustek+64−23 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 62 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

refactor(core): move `compact_size()` from `common.py` to `tools.py`

This commit simply moves a helper function called compact_size from one internal file to another and updates the import statements in files that use it. There is no change to what the function does, no bug fix, and no security impact.

2cb59ce6by Ondřej Vejpustek+29−296 files
No security note in commit
Open full analysis →Source commit ↗
Low 44 AI analysisMessage 67 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

fix(core/python): fix encoding in authentication challenge

This commit fixes how the Trezor Python library builds an authentication challenge. Previously, the code encoded the length of a header and the length of the challenge as a single byte, which only works for values up to 255. The fix uses a…

Fix in authentication/verification code pathChange from fixed single-byte length prefix to variable-length compact_size encodingPotential for incorrect serialization if challenge/header length exceeds 255 bytes
86b5d99cby Ondřej Vejpustek+3−31 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 62 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

refactor(core/python): factor out `get_challenge_message()`

This commit is a simple code cleanup: it moves a small block of code that builds an authentication challenge message into its own reusable function. There is no change to behavior, no bug fix, and no security-related change.

59c6eb74by Ondřej Vejpustek+12−61 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 57 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

refactor(tests): use `get_challenge_message()`

This is a minor code cleanup in the test suite. It replaces a manually constructed challenge message with a helper function that does the same thing. There is no change to the actual Trezor firmware or to how device authentication works in…

8e050722by Ondřej Vejpustek+10−71 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 50 · Thin
LD LedgerLedger Bitcoin app BitcoinHardware wallets

Trustworthy sign_psbt amount/fee display for non-default sighash: snapshots

This commit only updates test screenshot snapshots for the Ledger Bitcoin app. It does not change any application source code, so it cannot directly fix or introduce a security vulnerability in the shipped app. The snapshots reflect new ex…

No source-code changes in the commitOnly test snapshot images (PNG) are modified or addedCommit title references trustworthy amount/fee display for non-default sighash, suggesting a prior functional change exists elsewhere
086967aeby github-actions[bot]+0−0840 files
No security note in commit
Open full analysis →Source commit ↗
Informational 12 AI analysisMessage 60 · Adequate
LD LedgerLedger Bitcoin app BitcoinHardware wallets

Trustworthy sign_psbt amount/fee display for non-default sighash: integration tests

This commit only adds and updates automated integration tests for the Ledger Bitcoin app. It does not change the app's actual signing code. The tests verify that the device now shows clearer, more trustworthy on-screen amount and fee infor…

No C/device firmware code changesTest-only commit adjusting UI navigation expectationsNew tests assert that negative fees are rejected for default sighash but allowed/relabeled for ANYONECANPAY sighash
bb6a6aadby Ilya Artemov+175−325 files
No security note in commit
Open full analysis →Source commit ↗
Informational 12 AI analysisMessage 60 · Adequate
LD LedgerLedger Bitcoin app BitcoinHardware wallets

Trustworthy sign_psbt amount/fee display for non-default sighash: unit-tests

This commit only adds new automated unit tests for functions that decide how transaction amounts and fees are displayed on a Ledger device when signing a Bitcoin transaction with non-standard signature hash (sighash) modes. It does not cha…

Commit title references trustworthy amount/fee display for non-default sighash, a historically sensitive area in hardware-wallet signing UITests cover sighash commitment semantics (SIGHASH_NONE, SIGHASH_SINGLE, SIGHASH_ANYONECANPAY combinations) that directly affect what outputs a signature commits toNo functional code changes in this commit; only unit-test additions
d44e34ddby Ilya Artemov+102−01 file
No security note in commit
Open full analysis →Source commit ↗
Moderate 59 AI analysisMessage 50 · Thin
LD LedgerLedger Bitcoin app BitcoinHardware wallets

Trustworthy sign_psbt amount/fee display for non-default sighash: implementation

This commit changes how the Ledger Bitcoin app shows transaction amounts and fees on the device screen when a user signs a transaction that does not use the normal 'sign everything' rule (a so-called non-default sighash). Previously the ap…

UI trust reduction for non-default sighash prevents misleading fee/amount displaySighash classification helpers centralize ANYONECANPAY/NONE/SINGLE semanticsMixed-sighash detection disables coherent amount display
d4525576by Ilya Artemov+451−6612 files
No security note in commit
Open full analysis →Source commit ↗
Informational 12 AI analysisMessage 68 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

ipc, refactor: Update mp::SpawnProcess call

This is a routine code refactor in Bitcoin Core's inter-process communication (IPC) layer. It updates how child processes are launched so the code can work with a future version of a supporting library that adds Microsoft Windows support. …

2d3f72fdby Ryan Ofsky+28−114 files
No security note in commit
Open full analysis →Source commit ↗
01
Why commit watching?

Security should leave a paper trail.

A quiet fix may be responsible caution—or it may leave users unaware that their assets were ever at risk. CommitWatch preserves the evidence, adds context, and tracks whether vendors disclose, acknowledge, and learn.

Why we built this →