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
18285Commits captured
17497AI analyses
106High-risk findings · 30d
The watch feed

Changes worth understanding

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

17497 analyses
Highest risk·RSS
Informational 15 AI analysisMessage 62 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

chore(core): update "About Tropic" text in tutorial

This commit simply changes one sentence of on-screen tutorial text from calling the TROPIC01 chip 'a next-gen open-source secure element chip' to 'a next-gen secure element chip' (removing the words 'open-source'). It also updates the auto…

3a54a09bby Roman Zeyde+648−6484 files
No security note in commit
Open full analysis →Source commit ↗
Informational 23 AI analysisMessage 58 · Thin
LDK Lightning Dev Kitrust-lightning BitcoinCryptographic librariesLightning Network

Report LSPS5 fallback persistence

This is a tiny one-line fix in a Lightning Service Provider feature (LSPS5). Previously, when the code had to force-save peer state for a client that was about to be removed, it saved the data but forgot to report that it had done so. The …

Incorrect boolean return value for persistence statusState-management bookkeeping fix in prunable client lifecycleNo cryptographic, signature, or channel-funding logic changed
d7571912by Elias Rohrer+1−01 file
No security note in commit
Open full analysis →Source commit ↗
Low 35 AI analysisMessage 58 · Thin
LDK Lightning Dev Kitrust-lightning BitcoinCryptographic librariesLightning Network

Report LSPS2 fallback persistence

This one-line change fixes a bookkeeping bug in the LSPS2 (Lightning Service Provider Specification 2) service code. Previously, when the code had to force-save a peer's state before removing that peer, it performed the save but forgot to …

State-tracking inconsistency between actual persistence and reported persistence flagPotential for downstream logic to act on stale/incorrect persistence statusFix located in LSPS2 service provider state-pruning code path
a1cda953by Elias Rohrer+1−01 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 58 · Thin
LDK Lightning Dev Kitrust-lightning BitcoinCryptographic librariesLightning Network

Document LiquidityManager persist result

This commit only fixes two typos in documentation comments ('sevice' to 'service') and slightly rewords the description of what the return value means. No code behavior changes, no security relevance.

12815f38by Elias Rohrer+2−21 file
No security note in commit
Open full analysis →Source commit ↗
High 74 AI analysisMessage 90 · Strong
LDK Lightning Dev Kitrust-lightning BitcoinCryptographic librariesLightning Network

Verify Electrum transaction responses before use

This commit fixes a security hole in how a Bitcoin Lightning wallet talks to Electrum servers. Previously, the wallet asked a server for a specific transaction by its ID, but it did not check that the returned transaction actually matched …

Commit title and message explicitly describe a security-relevant verification failureFix adds txid recomputation and equality check against requested txidFix is applied at multiple call sites where `transaction_get` results are consumed
1d131506by Elias Rohrer+30−01 file
Vendor flagged security relevance
Open full analysis →Source commit ↗
Moderate 59 AI analysisMessage 80 · Strong
LDK Lightning Dev Kitrust-lightning BitcoinCryptographic librariesLightning Network

Check Esplora Merkle leaf risk by base size

This commit fixes a guard condition in LDK's Esplora transaction-sync code. The code tries to skip 64-byte transactions because such transactions can be abused in a known Bitcoin Merkle-tree weakness. The bug was that it measured total tra…

Bypass of explicit security guardWitness vs non-witness size confusionMerkle leaf weakness protection
bc05d9d9by Elias Rohrer+2−21 file
Vendor flagged security relevance
Open full analysis →Source commit ↗
Moderate 62 AI analysisMessage 80 · Strong
LDK Lightning Dev Kitrust-lightning BitcoinCryptographic librariesLightning Network

Check Electrum Merkle leaf risk by base size

This commit fixes a bug in how rust-lightning's Electrum transaction sync checks for a known Bitcoin Merkle-tree weakness. The old code rejected transactions whose total byte size was exactly 64, but an attacker could pad a transaction wit…

Fixes incorrect size check that could be bypassed with witness paddingAddresses known Bitcoin Merkle leaf-node weakness (bitslog 2018)Changes total_size to base_size for txid-relevant serialization
4636d6c9by Elias Rohrer+31−152 files
Vendor flagged security relevance
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 95 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

test: SOCKS5 proxy: expect that connection may be reset during handshake

This commit only changes a test helper script used during Bitcoin Core's automated testing. It makes the built-in SOCKS5 test proxy log expected connection resets as debug messages instead of printing full error backtraces. There is no cha…

9a8ef9b0by Vasil Dimov+10−21 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 95 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

test: SOCKS5 proxy: expect that connection may be reset when forwarding

This commit only changes Bitcoin Core's internal test framework. It makes the SOCKS5 proxy helper used in tests quieter when a test socket is closed unexpectedly, turning an ERROR log into a DEBUG log. There is no change to production Bitc…

eb320836by Vasil Dimov+52−122 files
No security note in commit
Open full analysis →Source commit ↗
Informational 12 AI analysisMessage 90 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Add regression test for from_base64 bug

This commit only adds a new regression test. It does not change any production code. The test checks that a function called from_base64 correctly rejects base64 inputs that decode to fewer or more than 65 bytes. Because no actual fix is in…

Regression test references a prior bug in message-signature base64 decodingTest verifies length validation of decoded base64 inputNo production code change in this commit
188f9f30by Mitchell Bagot+23−01 file
No security note in commit
Open full analysis →Source commit ↗
Moderate 62 AI analysisMessage 68 · Adequate
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Fix base64 panic in from_base64

This commit fixes a bug in the rust-bitcoin library where a specific function used to verify Bitcoin signed messages could crash the program. The crash could be triggered by feeding it a carefully crafted 88-character base64 string that de…

Panic/crash on malicious input (denial-of-service vector)Incorrect length validation of base64-decoded signaturePotential silent acceptance of malformed 64-byte signatures
33968200by Mitchell Bagot+9−31 file
No security note in commit
Open full analysis →Source commit ↗
Low 37 AI analysisMessage 70 · Adequate
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Fix: When a server has too many apps, the Policies page timeout or crash (#7406)

This commit fixes a performance problem on the BTCPay Server 'Policies' settings page. Previously, the page tried to load a dropdown list of every app on the server, which could time out or crash when there were many apps. The fix replaces…

Change from bounded select list to free-form text input for app identifiersAdded server-side validation (TryGetValue + ModelState.AddModelError) for RootAppId and DomainToAppMapping AppId valuesRemoved potentially expensive server-side query that loaded all apps into view state
e6085835by Nicolas Dorier+21−414 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 →