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
17782Commits captured
17251AI analyses
98High-risk findings · 30d
The watch feed

Changes worth understanding

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

17251 analyses
Highest risk·RSS
Informational 23 AI analysisMessage 85 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

wallet: Use Descriptor::CanSelfExpand() in CanGetAddresses()

This is a small Bitcoin Core wallet change that lets the wallet generate addresses from certain descriptors even when it does not have private keys and has already used up its pre-derived address range. It only affects descriptors that can…

Changes address-derivation gating logic in wallet codeExpands conditions under which addresses can be produced without private keysNo explicit security framing, CVE, or advisory language in commit
1e996640by Ava Chow+1−11 file
No security note in commit
Open full analysis →Source commit ↗
Informational 19 AI analysisMessage 58 · Thin
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

descriptor: Add CanSelfExpand()

This commit adds a new helper method called CanSelfExpand() to Bitcoin Core's descriptor system. It lets the code ask whether a wallet descriptor can produce its Bitcoin address(es) on its own, without needing a saved cache or private keys…

New API surface added to descriptor subsystem (CanSelfExpand)No change to existing expansion, signing, or key-derivation logicNo bounds, memory, or cryptographic operations modified
d2ee9227by Ava Chow+57−184 files
No security note in commit
Open full analysis →Source commit ↗
Informational 23 AI analysisMessage 95 · Strong
LDK Lightning Dev Kitrust-lightning BitcoinCryptographic librariesLightning Network

ln: process added trampoline htlcs with CLTV validation in tests

This commit changes how the Lightning node handles a special kind of forwarded payment called a 'trampoline' payment. Previously, trampoline forwards were always rejected. Now, in test builds only, the code allows them through after checki…

Trampoline forwarding previously hard-rejected; now conditionally accepted in test builds with reduced validationCLTV and fee-skim checks added for trampoline forwards, but full channel-level forwarding checks still skippedProduction code path continues to reject trampoline forwards
4329fe92by Carla Kirk-Cohen+28−1262 files
No security note in commit
Open full analysis →Source commit ↗
Low 26 AI analysisMessage 95 · Strong
LDK Lightning Dev Kitrust-lightning BitcoinCryptographic librariesLightning Network

ln: handle DecodedOnionFailure for local trampoline failures

This commit fixes a code path in the Lightning Dev Kit where a specific kind of local payment failure (called a 'TrampolineForward' failure) was not being handled. Previously, the code only expected failures from regular outbound routes an…

Removal of unreachable!() panic path for TrampolineForward HTLC sourceAddition of local trampoline failure decoding in onion error handlingIntentional non-setting of payment_failed_permanently for local failures to allow retry
4f2429eaby Carla Kirk-Cohen+28−171 file
No security note in commit
Open full analysis →Source commit ↗
Low 34 AI analysisMessage 95 · Strong
LDK Lightning Dev Kitrust-lightning BitcoinCryptographic librariesLightning Network

ln: double encrypt errors received from downstream failures

This commit adds missing encryption wrapping for error messages in the Lightning Dev Kit when acting as a 'trampoline' forwarding node. Previously, if a downstream node returned an error that the trampoline could not fully decrypt, the err…

Missing cryptographic wrapping of failure packets in trampoline forwarding pathPotential information leakage or unrecoverable error propagation for trampoline paymentsCommit describes the change as bare-minimum with followup proper error handling planned
c6adebfdby Carla Kirk-Cohen+4−01 file
No security note in commit
Open full analysis →Source commit ↗
Low 25 AI analysisMessage 100 · Strong
LDK Lightning Dev Kitrust-lightning BitcoinCryptographic librariesLightning Network

ln: add trampoline mpp accumulation with rejection on completion

This commit adds partial support in the Lightning Dev Kit node software for receiving and temporarily holding multi-part trampoline payments, then deliberately rejects them once all parts arrive because full outbound forwarding is not yet …

New trampoline forward handling path accumulates MPP parts before rejectingDebug assertion guards first-HTLC failure in MPP mergeTODO comment flags possible MPP inconsistency in next_node_id across trampoline parts
1afd35e6by Carla Kirk-Cohen+240−112 files
No security note in commit
Open full analysis →Source commit ↗
Informational 13 AI analysisMessage 73 · Adequate
LDK Lightning Dev Kitrust-lightning BitcoinCryptographic librariesLightning Network

Make SpliceFundingFailed::contribution non-optional

This commit is a small internal cleanup in the Lightning Dev Kit code. It removes an unnecessary 'Option' wrapper from a data field called `contribution` inside `SpliceFundingFailed`, because that field is always created from a real value.…

13b19c86by Wilmer Paulino+14−162 files
No security note in commit
Open full analysis →Source commit ↗
Low 44 AI analysisMessage 73 · Adequate
LDK Lightning Dev Kitrust-lightning BitcoinCryptographic librariesLightning Network

Check channel is live while handling counterparty tx_init_rbf

This commit adds a safety check in the Lightning Dev Kit's code that handles a message called tx_init_rbf, which is used to propose bumping the fee on a channel's on-chain transaction. Before this change, the code did not verify that the c…

Missing state validation in protocol message handlerShutdown/RBF state machine inconsistencyPeer-triggered error path (WarnAndDisconnect)
43c0fc71by Wilmer Paulino+5−01 file
No security note in commit
Open full analysis →Source commit ↗
Low 37 AI analysisMessage 85 · Strong
LDK Lightning Dev Kitrust-lightning BitcoinCryptographic librariesLightning Network

Prefer tx_abort over disconnection for splice negotiation errors

This commit changes how the Lightning Dev Kit node responds to mistakes or disagreements during splicing (a way to resize a payment channel). Instead of immediately disconnecting from the peer in many cases, it now sends a 'tx_abort' messa…

Change of error response from peer disconnection to tx_abort for splice negotiation failuresNew AbortReason::InvalidContribution variant carrying a descriptive stringPreservation of WarnAndDisconnect for spec-mandated conditions (non-live channel, non-quiescent state, zero contribution)
a5d59927by Wilmer Paulino+99−1034 files
No security note in commit
Open full analysis →Source commit ↗
Low 37 AI analysisMessage 65 · Adequate
LDK Lightning Dev Kitrust-lightning BitcoinCryptographic librariesLightning Network

Prefer tx_abort over disconnection for inability to RBF

This change makes a Lightning node send a 'tx_abort' message instead of disconnecting from a peer when an RBF (fee-bump) request cannot be honored during a splice. The goal is to avoid unnecessary reconnections and keep the channel usable.…

Change from peer disconnection to in-protocol tx_abort for non-fatal RBF rejectionsNew AbortReason::RbfUnavailable variant added to interactivetxs.rsTest expectations changed from HandleError/DisconnectPeerWithWarning to SendTxAbort
ff3d3886by Wilmer Paulino+41−783 files
No security note in commit
Open full analysis →Source commit ↗
Informational 19 AI analysisMessage 68 · Adequate
LDK Lightning Dev Kitrust-lightning BitcoinCryptographic librariesLightning Network

Allow invalid contribution error upon quiescence

This commit updates a fuzz test (a randomized testing harness) to accept one additional warning message when the test framework expects a peer disconnection. The new message, 'contribution no longer valid at quiescence,' is treated as a no…

Fuzz-test-only changeRelates to Lightning splicing/RBF protocol quiescence handlingWarnAndDisconnect event is expected behavior, not a crash or assertion failure
68c1f21aby Wilmer Paulino+2−11 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 80 · Strong
KX KruxKrux BitcoinHardware wallets

fix: add src to poe task PYTHONPATH

This commit adjusts how a Python build tool (poe) finds the project's own source code when running commands. It adds the local 'src' directory to the PYTHONPATH environment variable for poe tasks. There is no indication this is a security …

566a0b93by odudex+3−01 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 →