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
Informational 17 AI analysisMessage 83 · Strong
EP Elements ProjectCore Lightning BitcoinLightning Network

pytest: test to reproduce failed to retransmit funding transaction

This commit only adds a new pytest test case that reproduces a minor startup logging bug. Core Lightning was unnecessarily trying to re-broadcast already-confirmed channel funding transactions every time it restarted. Bitcoin rejected the …

Spurious rebroadcast of funding transactions on restartIncorrect channel depth check at startup due to DB load orderingRegression test added; no daemon code patched in this commit
6aae3d48by enaples+16−01 file
No security note in commit
Open full analysis →Source commit ↗
Low 25 AI analysisMessage 73 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

lightningd: don't try to re-xmit funding tx for already-confirmed channels.

This commit fixes a harmless but noisy bug in Core Lightning. On every restart, the node was trying to re-broadcast the funding transaction for channels that were already confirmed long ago. Bitcoin rejected these with a routine 'already k…

Spurious re-broadcast of funding transactions on node restartReliance on a field (channel->depth) that is uninitialized at the point of useRoutine bitcoind error -27 ('Transaction outputs already in utxo set') surfaced as UNUSUAL log
d7b0f1faby enaples+8−42 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 100 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

test: raise reindex mining RPC timeout

This is a harmless test-only change. It doubles the RPC timeout in one functional test so that a slow test step (mining a long chain) does not fail due to client-side timeout during parallel debug-mode test runs. It does not change any pro…

9e6546c5by Lőrinc+1−01 file
No security note in commit
Open full analysis →Source commit ↗
Informational 16 AI analysisMessage 77 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

fix(solana): use template for indexed cosigners [no changelog]

This commit fixes a minor user-interface wording issue in Trezor's Solana app. Previously, the device built the cosigner label by manually combining the word 'Cosigner' with a number, which could cause problems for translations. Now it use…

UI label construction changed from runtime string concatenation to a translation templateNo changes to signing logic, address validation, or transaction parsingNo vendor disclosure of security relevance in commit message or diff
4c25a6fdby Michal Kazda+43−57 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 45 · Thin
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

2026-06-21 automated rustfmt nightly

This is an automated code-formatting commit. It only reorders import and module declarations to match the latest rustfmt nightly style. No logic, behavior, or security-sensitive code was changed.

70a946b9by Fmt Bot+3−32 files
No security note in commit
Open full analysis →Source commit ↗
Moderate 59 AI analysisMessage 62 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

fix(core): Avoid out-of-bounds read in utils.consteq().

This commit fixes a bug in a low-level security helper inside Trezor hardware wallets. The helper, called consteq(), compares a secret value against a public value in a way meant to take the same amount of time regardless of the secret's c…

Out-of-bounds read in secret-comparison helperTiming-attack-resistant comparison routineConstant-time length-mismatch handling added
8f19041dby Andrew Kozlik+27−93 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 65 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

ci: use warp docker buildkit cache

This commit fixes a CI (Continuous Integration) configuration mistake. It restores the intended Docker cache provider for Bitcoin Core's own GitHub workflows, using 'warp' for the official bitcoin/bitcoin repository and 'gha' for forks. Th…

b552f171by will+3−31 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 30 · Opaque
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

rpc: add placeholder annotation for deprecated params

This commit is a documentation-only metadata change. It adds a new 'placeholder' flag to the internal description of several old, ignored RPC parameters so the help system can label them as kept only for backward compatibility. No code beh…

f5116c58by will+10−44 files
No security note in commit
Open full analysis →Source commit ↗
Informational 19 AI analysisMessage 45 · Thin
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

rpc: expose RPC metadata for introspection

This commit adds small plumbing so that Bitcoin Core's RPC command metadata (descriptions, argument details, result formats) can be inspected by other code. It does not change any user-facing RPC behavior by itself; it merely exposes inter…

No memory safety issues visible in the diffNo authentication or authorization changesNo new externally reachable endpoints
26c221a9by will+6−03 files
No security note in commit
Open full analysis →Source commit ↗
Informational 22 AI analysisMessage 85 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

rpc: render Type::ANY in help text instead of aborting

This is a small bug-fix in Bitcoin Core's RPC help system. A special placeholder result type called Type::ANY previously caused the help() command to crash with an 'unreachable' assertion when it appeared inside a nested result description…

Crash/assertion in RPC help generation (NONFATAL_UNREACHABLE)Denial-of-service vector limited to help() RPC outputNo consensus, networking, or wallet code affected
6a1a66c1by will+2−11 file
No security note in commit
Open full analysis →Source commit ↗
Low 26 AI analysisMessage 80 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

rpc: erase empty map entry in removeCommand

This commit fixes a bookkeeping bug in Bitcoin Core's RPC command registry. When a command was fully removed (for example, when a wallet is unloaded), the command's name was still left behind in an internal list. That caused tools like `ge…

Stale/inconsistent internal state in RPC command tableInformation-discrepancy bug: listCommands/getopenrpcinfo report non-existent RPCsPotential for client confusion or failed RPC calls after dynamic module unload
06de34a0by will+3−01 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 68 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

rpc: add missing string_view include to server.h

This is a routine code-cleanup change: it adds a missing #include <string_view> to a header file so it no longer depends on other headers to provide the std::string_view type. It does not change any program behavior or fix a security bug.

d4d64ae7by will+1−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 →