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
17600Commits captured
17165AI analyses
88High-risk findings · 30d
The watch feed

Changes worth understanding

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

17165 analyses
Highest risk·RSS
Informational 17 AI analysisMessage 50 · Thin
LDK Lightning Dev Kitrust-lightning BitcoinCryptographic librariesLightning Network

Bump esplora-client to 0.13 to switch from `reqwest` to `bitreq`

This commit updates a dependency used to talk to Esplora blockchain servers from version 0.12 to 0.13, switching the underlying HTTP library from reqwest to bitreq. It also removes two CI workarounds that pinned older versions of idna_adap…

Dependency version bump (esplora-client 0.12 -> 0.13)HTTP backend switch (reqwest -> bitreq) in a transitive dependencyRemoval of MSRV pins for idna_adapter and hyper-rustls
5cd499e0by Matt Corallo+1−72 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 83 · Strong
LDK Lightning Dev Kitrust-lightning BitcoinCryptographic librariesLightning Network

Test cross-version serialization of pending splices

This commit only adds new test code. It exercises how a newer version of LDK exchanges saved channel data with the older LDK 0.2 release when a channel has a pending splice. There is no change to production logic, no bug fix, and no securi…

0beadb3bby Jeffrey Czyz+208−01 file
No security note in commit
Open full analysis →Source commit ↗
Low 33 AI analysisMessage 73 · Adequate
LDK Lightning Dev Kitrust-lightning BitcoinCryptographic librariesLightning Network

Queue a splice on a channel with an inherited splice until it locks

This commit fixes a compatibility edge case when users upgrade from an older version of LDK (0.2) while a channel splice is still pending. The older version did not save enough details about the splice, so after upgrading the software coul…

Removal of debug_assert that could panic on upgrade/downgrade dataGraceful handling of missing splice metadata from older LDK persistencePrevention of refusal/crash when re-splicing a channel with an inherited splice
1127a38aby Jeffrey Czyz+77−42 files
No security note in commit
Open full analysis →Source commit ↗
Informational 14 AI analysisMessage 73 · Adequate
LDK Lightning Dev Kitrust-lightning BitcoinCryptographic librariesLightning Network

Compute the minimum splice RBF feerate via PendingFunding

This commit is a pure code cleanup: it moves a small fee-calculation helper for Lightning splice RBF (replace-by-fee) transactions into a struct method and renames it. The actual arithmetic formula and the places that use it stay exactly t…

5137c126by Jeffrey Czyz+38−321 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 45 · Thin
LDK Lightning Dev Kitrust-lightning BitcoinCryptographic librariesLightning Network

Add pending changelog entry for PR 4687

This commit only adds a changelog text file describing a previously merged feature (PR 4687). It does not change any source code, build scripts, tests, or documentation that affects program behavior. There is no security-relevant change to…

0af1ebbbby Jeffrey Czyz+18−01 file
No security note in commit
Open full analysis →Source commit ↗
Informational 20 AI analysisMessage 68 · Adequate
LDK Lightning Dev Kitrust-lightning BitcoinCryptographic librariesLightning Network

Expose pending splice details in ChannelDetails

This commit adds a new read-only API field that lets users query the status of in-progress channel splice operations on demand. It does not change protocol behavior, permissions, or how funds are handled; it only exposes internal state tha…

No new network messages or protocol changesNo new cryptographic operationsNo changes to authorization, fee handling, or transaction signing
cb77c1c3by Jeffrey Czyz+1581−46 files
No security note in commit
Open full analysis →Source commit ↗
Informational 18 AI analysisMessage 80 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

validation: track last flushed block

This commit adds internal bookkeeping so Bitcoin Core can remember the last block whose state was safely written to disk. It does not, by itself, change any security boundary or fix a known bug; it is a small infrastructure change meant to…

New internal state tracking for flush synchronizationNo direct bug fix or vulnerability remediation visible in diffCommit message frames change as preparatory infrastructure, not as a security fix
09c06960by Martin Zumsande+8−03 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 45 · Thin
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

index: Remove return value from Commit()

This is a small internal cleanup change in Bitcoin Core. A helper function called Commit() previously returned true or false to indicate success or failure, but nothing in the code was actually checking that result. The change removes the …

65735728by Martin Zumsande+2−42 files
No security note in commit
Open full analysis →Source commit ↗
Moderate 53 AI analysisMessage 85 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

index: Don't commit ahead of the flushed chainstate

This commit fixes a corruption risk in Bitcoin Core's optional indexes (notably coinstatsindex). Previously, an index could save its progress to disk even though the main chainstate database had not yet flushed that far. If the node then c…

Data corruption on unclean shutdown/reorgIndex state inconsistency with chainstatecoinstatsindex specifically mentioned as affected
3679f1ecby Martin Zumsande+19−93 files
Vendor flagged security relevance
Open full analysis →Source commit ↗
Low 28 AI analysisMessage 73 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

validation: Don't use m_chain.Tip() in FlushStateToDisk

This commit fixes a minor bookkeeping bug in Bitcoin Core. When flushing state to disk during a block disconnection, the code was incorrectly reporting the current chain tip (the block being disconnected) as the flushed block, instead of t…

Incorrect state reporting in a chain-state flush signalPotential inconsistency between on-disk state and signaled locator during reorg/disconnect pathsIndexers relying on ChainStateFlushed could observe a stale or mismatched block locator
e9ed898aby Martin Zumsande+1−21 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 57 · Thin
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

docs(zcash): tighten orchard patch comment

This commit only rewrites a comment in a dependency configuration file. No code, dependency versions, or build settings were changed. It has no security relevance on its own.

1d76df4dby Adam Tucker+1−31 file
No security note in commit
Open full analysis →Source commit ↗
Moderate 57 AI analysisMessage 57 · Thin
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

refactor(zcash): remove checked PCZT digest stamp

This commit removes a security check that verified a Zcash transaction buffer had not been tampered with between the 'check/review' screen and the 'sign' step on a Keystone hardware wallet. Before the change, the device stored a fingerprin…

Removal of a digest-based integrity check on a signing input bufferRenaming of verified_bytes() to checked_bytes() with weakened semanticsCross-language (C/Rust) boundary no longer re-validates buffer contents
cf6b75c8by Adam Tucker+14−362 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 →