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
Low 35 AI analysisMessage 100 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

fix: InstructionIndices::nth byte position bug

This commit fixes a bug in a Rust Bitcoin library iterator that reports byte positions of script instructions. The custom `nth` method incorrectly returned the byte offset of the found instruction without updating the iterator's internal p…

Iterator state corruption in a public APIIncorrect byte-index reporting for Bitcoin script instructionsPotential downstream logic errors if indices are used for parsing or validation
e4c49d41by Alexey Gradoboev+0−51 file
No security note in commit
Open full analysis →Source commit ↗
Low 35 AI analysisMessage 100 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

test: adding test for InstructionIndices::nth byte position bug

This commit only adds a new test to the rust-bitcoin library. The test demonstrates that a method called `InstructionIndices::nth` can report incorrect byte positions when used in certain ways. The commit message explicitly says there is '…

Iterator position desynchronization in script instruction parsingIncorrect byte offset reporting could affect code relying on accurate script indicesNo fix included; only regression test added
2f5e9aceby Alexey Gradoboev+37−01 file
No security note in commit
Open full analysis →Source commit ↗
Informational 21 AI analysisMessage 96 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

Squashed 'src/secp256k1/' changes from 7262adb4b4..bd0287d650

This commit is a routine subtree update of the secp256k1 cryptographic library inside Bitcoin Core. It pulls in a batch of upstream secp256k1 changes: build-system cleanups, new tests, documentation fixes, a minor MuSig nonce-generation cl…

MuSig secret-key wipe now happens on both success and failure paths in `secp256k1_musig_nonce_gen_counter`New `_ecmult_gen_ge` helper clears Jacobian intermediate state to reduce potential side-channel leakageForce-inlining of performance-critical field operations (mul/sqr) is a hardening/performance change, not a vulnerability fix
1f3f0a4eby fanquake+257−9025 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 83 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

scripted-diff: Rename SteadyClockContext to FakeSteadyClock

This commit is a simple automated rename of a test-only helper class from SteadyClockContext to FakeSteadyClock. It only changes names in comments and test/fuzz code to make naming consistent. There is no functional change and no security …

855a3feeby Hao Xu+9−95 files
No security note in commit
Open full analysis →Source commit ↗
Moderate 60 AI analysisMessage 78 · Adequate
LDK Lightning Dev Kitrust-lightning BitcoinCryptographic librariesLightning Network

Fail held HTLCs on LSPS2 abandon

This commit fixes a bug in the Lightning Dev Kit's LSPS2 (Just-In-Time channel) service. Previously, when a service provider abandoned a pending JIT channel open, any intercepted HTLCs (pending payment holds) waiting for that channel were …

HTLCs held in payment_queue could remain pending indefinitely after channel_open_abandoned, potentially locking sender fundsMissing cleanup of intercepted HTLC state on JIT channel abandonmentRegression test confirms fail_intercepted_htlc is invoked and HTLC is released
ccc8b55fby Joost Jager+139−162 files
No security note in commit
Open full analysis →Source commit ↗
Low 35 AI analysisMessage 62 · Adequate
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

feat: update dice roll entropy ui

This commit updates the user interface and internal checks for generating wallet seed phrases using dice rolls as a source of randomness. It enforces a minimum number of dice rolls depending on the desired seed strength: at least 50 rolls …

Enforces minimum entropy input length based on target mnemonic strengthAdds server-side/model-layer validation in addition to UI gatingPrevents generation of 256-bit seeds from insufficient dice-roll entropy
7bc4d7d8by soralit+158−168 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 78 · Adequate
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Use core::cmp in units kani verification

This is a tiny, non-security change in test-only code. It swaps one standard-library import for an equivalent core-library import so that a verification tool (Kani) can run in environments without the full standard library. There is no cha…

09897b03by Mitchell Bagot+1−11 file
No security note in commit
Open full analysis →Source commit ↗
Low 26 AI analysisMessage 68 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

Revert "Bolt quote updates and improvements"

This commit is a wholesale revert of an earlier pull request that was accidentally merged without proper review. It removes new splice-handling logic in the channel daemon, stricter bech32 padding checks, and several BOLT 11/12 quote and v…

Reverts unreviewed code that was rejected as spec-deviatingRemoves txid-comparison splice detection heuristic in channel reconnectionRemoves stricter bech32 padding-bit validation
0a8a7afeby Níckolas Goline+26−7912 files
No security note in commit
Open full analysis →Source commit ↗
Low 34 AI analysisMessage 75 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

askrene-getroutes: add test for source==destination

This commit adds a test that checks Core Lightning's routing plugin (askrene) properly rejects a request where the payment source and destination are the same node. The test is marked as expected to fail for now, meaning the bug it checks …

Potential denial-of-service via malformed RPC input (source==destination)Test marked xfail indicates unpatched behaviorCrash of lightningd suggested by test docstring
d0a974d2by Lagrang3+42−01 file
No security note in commit
Open full analysis →Source commit ↗
Moderate 59 AI analysisMessage 68 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

getroutes: don't crash on source==destination

This commit fixes a crash in Core Lightning's routing plugin (cln-askrene). When a user called the getroutes command with the same node as both source and destination, the plugin hit an internal assertion and aborted. The fix adds a simple…

Denial-of-service via malformed RPC input causing plugin abortAssertion failure in routing plugin child processInput validation gap in JSON-RPC command handler
c7e7a5e4by Lagrang3+5−12 files
Vendor flagged security relevance
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 83 · Strong
EP Elements ProjectCore Lightning BitcoinLightning Network

flake: test_no_delay: reduce expected_saving threshold to fix probe variance

This commit only adjusts a threshold inside a single automated test. It makes a timing assertion more lenient so that random network-measurement noise does not cause false test failures. There is no change to production code, no user-facin…

31741645by Níckolas Goline+4−21 file
No security note in commit
Open full analysis →Source commit ↗
Informational 23 AI analysisMessage 67 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

test: announce field must be 0 or 1 in sendcmpct

This commit adds a new test to Bitcoin Core's functional test suite. The test verifies that if a peer sends a 'sendcmpct' message with an invalid 'announce' value (anything other than 0 or 1), the node logs an error and disconnects that pe…

Tests protocol-mandated rejection of malformed P2P message fieldVerifies peer disconnection on invalid boolean-like field valueReferences BIP152 specification requirement
abc33ff0by brunoerg+13−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 →