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
18178Commits captured
17450AI analyses
103High-risk findings · 30d
The watch feed

Changes worth understanding

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

17450 analyses
Highest risk·RSS
Moderate 58 AI analysisMessage 88 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

p2p: Drop unsolicited CMPCTBLOCK from non-HB peer

This Bitcoin Core change tightens the rules for a fast block-relay feature called compact blocks (BIP 152). Previously, any peer could send a compact block announcement without being asked. Now, if a peer sends one without being marked as …

Unsolicited network message now droppedPartial mitigation of reported mempool privacy leak (#28272)DoS/bandwidth-waste mitigation mentioned by committer
83135917by David Gumberg+31−33 files
Vendor flagged security relevance
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 67 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

test: p2p: Nodes ignore unsolicited CMPCTBLOCK's

This commit only adds a new functional test to Bitcoin Core. It verifies that nodes ignore unsolicited compact block (CMPCTBLOCK) messages from peers that are not in high-bandwidth mode, while still accepting them from high-bandwidth peers…

Behavioral test coverage for P2P compact block acceptance policyRefactoring of test helper to use explicit peer index instead of last peerNo modification of src/ production code
e845e263by David Gumberg+60−71 file
No security note in commit
Open full analysis →Source commit ↗
Informational 12 AI analysisMessage 95 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

test: (Un)solicited invalid cb -> get disconnected.

This commit only changes a test file. It expands an existing test to verify that Bitcoin Core correctly disconnects peers that send badly formed compact block messages, whether those peers are high-bandwidth or low-bandwidth. It does not c…

Test-only changeAdds coverage for peer disconnection on malformed compact block messagesComment explicitly states messages are not consensus-invalid
92cea63cby David Gumberg+24−71 file
No security note in commit
Open full analysis →Source commit ↗
Moderate 60 AI analysisMessage 81 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

p2p: make blocksonly nodes ignore CMPCTBLOCK messages

This change fixes a privacy leak in Bitcoin Core's 'blocksonly' mode. Blocksonly nodes intentionally avoid keeping a mempool of unconfirmed transactions. Previously, they would still try to process compact block (CMPCTBLOCK) messages from …

Privacy / deanonymization fix: blocksonly node's GETBLOCKTXN response could reveal own transactionsNetwork-layer behavior change: ignore CMPCTBLOCK when -blocksonly is enabledNew functional test covering both solicited and unsolicited compact blocks on blocksonly nodes
bf9884f4by David Gumberg+51−12 files
Vendor flagged security relevance
Open full analysis →Source commit ↗
Low 47 AI analysisMessage 83 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

p2p: Ignore CMPCTBLOCK from peer that hasn't sent SENDCMPCT

This Bitcoin Core update tightens the rules for compact block messages. Before the change, a peer could send a compressed block (CMPCTBLOCK) even if it had never advertised support for compact blocks via the SENDCMPCT handshake. The fix ma…

New input-validation gate before deserialization of peer messagePeer-state flag (m_provides_cmpctblocks) now enforced for CMPCTBLOCKFunctional tests extended to cover unsolicited and solicited CMPCTBLOCK from non-announcing peers
9c5dd292by David Gumberg+25−14 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 55 · Thin
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

qa: Avoid UTXO reuse between test functions

This is a minor fix inside Bitcoin Core's own test suite. It changes how test UTXOs are consumed so that different test functions don't accidentally reuse the same fake coin. It does not affect the live Bitcoin network, wallets, or node so…

55e3a57fby Hodlinator+7−91 file
No security note in commit
Open full analysis →Source commit ↗
Low 29 AI analysisMessage 73 · Adequate
BS BlockstreamBlockstream Jade BitcoinHardware wallets

descriptor: add support for liquid confidential descriptors

This commit adds support for Liquid confidential descriptors to the Blockstream Jade hardware wallet. It is a feature addition, not a fix for a known vulnerability. The code introduces new validation rules that reject non-SLIP77 blinding k…

Feature-gated Liquid confidential descriptor supportNew validation rejecting non-SLIP77 blinding keys on LiquidNew validation rejecting confidential descriptors on Bitcoin mainchain
0e009e4fby Daniel Newton+160−419 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 55 · Thin
BS BlockstreamBlockstream Jade BitcoinHardware wallets

tests: add liquid descriptor to debug_selfcheck()

This commit only adds a new test case to the device's self-check suite. It exercises Liquid Bitcoin descriptor parsing and checks that blinding keys and script outputs are produced correctly. There is no change to production code, no bug f…

f1da3ebaby Daniel Newton+92−01 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 75 · Adequate
BS BlockstreamBlockstream Jade BitcoinHardware wallets

tests: update main test suite with descriptor parsing changes

This commit only updates the project's test file (test_jade.py). It adjusts test cases and adds new tests for how Bitcoin/Liquid wallet descriptors are parsed and validated, including new rules around SLIP-77 blinding keys on Liquid. There…

Test-only change with no production code modificationsNew test coverage for descriptor parsing network rulesSLIP-77 blinding-key requirement enforced for Liquid descriptors
be0c5fd3by Daniel Newton+73−181 file
No security note in commit
Open full analysis →Source commit ↗
Informational 5 AI analysisMessage 50 · Thin
BS BlockstreamBlockstream Jade BitcoinHardware wallets

wally: update to latest master to pick up liquid descriptor support

This commit updates an internal dependency (libwally-core) to a newer version so that Blockstream Jade can support Liquid descriptors. No actual code changes are shown, and the commit message describes only a feature addition, not a securi…

baeedee5by Daniel Newton+1−11 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 68 · Adequate
BT btcsuitebtcd BitcoinNode implementations

version: bump to v0.26.0-beta for final release

This commit simply changes a version label from 'beta.rc1' to 'beta' in preparation for a final release. It is a routine release-management change with no security relevance.

abec1101by Olaoluwa Osuntokun+1−11 file
No security note in commit
Open full analysis →Source commit ↗
Low 29 AI analysisMessage 65 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

Revert "fix(trezor-client): send empty passphrase for standard wallets"

This commit undoes a previous change in the Trezor client Rust library. The original change made the software send an empty passphrase when using standard (non-hidden) wallets. The revert restores older behavior where, if the device is not…

Reverts a prior 'fix' related to passphrase handling for standard walletsChanges the message sent to the hardware device during passphrase entry flowPassphrase handling is a sensitive seed-derivation step
1ca9f9e0by Roman Zeyde+3−41 file
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 →