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
18176Commits captured
17449AI analyses
103High-risk findings · 30d
The watch feed

Changes worth understanding

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

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

refactor(core/build): remove special bolt layout cases

This commit is a straightforward build-system cleanup. It removes special-case layout feature bundles (like layout_bolt_d001 and layout_bolt_d002) and replaces them with separate, explicit display-type features (display_mono, display_rgb56…

8792e14cby tychovrahe+48−13814 files
No security note in commit
Open full analysis →Source commit ↗
Informational 12 AI analysisMessage 45 · Thin
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

http: remove libevent usage from this subsystem

This commit removes the old libevent-based HTTP server code from Bitcoin Core and switches fully to a newer custom HTTP server implementation. It is a large cleanup/refactoring change, not a security patch. There is no indication in the co…

No security-relevant keywords in commit title or messageNo CVE, advisory, or security-fix references in commit messageDiff is purely removal of libevent integration and test updates
8c1eea07by Matthew Zipkin+21−6624 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 58 · Thin
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

logging: deprecate libevent category

This commit removes support for the 'libevent' logging category in Bitcoin Core. It is a routine cleanup: the category is marked as deprecated, attempts to enable it are ignored with a warning, and it is excluded from the special 'all' log…

39e9099dby Matthew Zipkin+31−167 files
No security note in commit
Open full analysis →Source commit ↗
Low 43 AI analysisMessage 35 · Opaque
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

HTTPServer: disconnect clients

This commit finishes the Bitcoin Core HTTP server's ability to actually close client connections. Before, several error paths had 'TODO: disconnect' comments, meaning misbehaving or finished clients could stay connected longer than intende…

Replaces multiple TODO: disconnect stubs with actual disconnection logicAdds HTTP 413 Content Too Large response and disconnect on oversized request bodiesAdds HTTP 400 Bad Request response and disconnect on request parse failures
a69bb9e1by Matthew Zipkin+125−344 files
No security note in commit
Open full analysis →Source commit ↗
Low 27 AI analysisMessage 50 · Thin
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

Allow http workers to send data optimistically as an optimization

This commit changes how Bitcoin Core's built-in HTTP server sends replies. Previously, worker threads always queued response data and told the main I/O loop to send it later. Now, if the send buffer is empty, the worker tries to push data …

Cross-thread state access: a worker thread now calls socket-send logic and sets flags previously managed by the I/O loopAtomic conversion of m_connection_busy indicates awareness of concurrent accessNo explicit security claims, CVE references, or bug-report attribution in commit or supplied references
5ef1b80aby Matthew Zipkin+21−62 files
No security note in commit
Open full analysis →Source commit ↗
Low 46 AI analysisMessage 81 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

HTTPServer: use a queue to pipeline requests from each connected client

This change reorders how Bitcoin Core's built-in web server handles multiple HTTP requests from the same connection. Previously, incoming requests could be handed off to worker threads as soon as they arrived, so a later, fast request migh…

Race condition mitigation: serializes per-client request handling to prevent out-of-order responsesState consistency: commit message explicitly cites risk of 'old state' being returned to later requestsHTTP/1.1 pipelining compliance: references RFC 7230 §6.3.2 response ordering requirement
7ee7df98by Matthew Zipkin+33−42 files
Vendor flagged security relevance
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 73 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

define HTTP request methods at module level outside of class

This commit is a straightforward code cleanup: it moves the list of HTTP request methods (GET, POST, HEAD, PUT, UNKNOWN) out of a class and into a shared module-level type so two different parts of the codebase can use the same definitions…

dd11b5e0by Matthew Zipkin+45−365 files
No security note in commit
Open full analysis →Source commit ↗
Informational 20 AI analysisMessage 65 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

Add helper methods to HTTPRequest to match original API

This commit adds helper methods to Bitcoin Core's HTTP request handling so that newer internal code can mimic the older libevent-based API. The main functional change is a new, more tolerant URL query-parameter parser. It replaces a strict…

Relaxed input validation: malformed percent-encoding no longer raises an error and is returned to callers as raw data.Custom parser replaces mature library parser (libevent), increasing attack surface for URL parsing edge cases.New code uses std::string_view and pointer arithmetic to construct query substrings; bounds appear correct but are now project-maintained.
f946ff5aby Matthew Zipkin+116−123 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 85 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

refactor: split http_request_cb into libevent callback and dispatch

This is a pure code cleanup change. A single function that handles incoming HTTP requests was split into two functions: one that prepares the raw libevent request and wraps it, and another that performs the existing allow-checks and hands …

fec6b6bcby Matthew Zipkin+31−271 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 85 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

refactor: split HTTPBindAddresses into config parse and libevent setup

This commit is a simple code cleanup: it takes one function that did two jobs—reading RPC bind settings and actually opening network sockets—and splits it into two smaller functions. The behavior, settings, and warnings shown to users are …

2ca645c2by Matthew Zipkin+29−251 file
No security note in commit
Open full analysis →Source commit ↗
Low 25 AI analysisMessage 50 · Thin
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

HTTPServer: implement control methods to match legacy API

This commit refactors how Bitcoin Core's built-in HTTP/RPC server is started and stopped. It adds new control functions (InitHTTPServer, StartHTTPServer, InterruptHTTPServer, StopHTTPServer) and makes shutdown more orderly by rejecting new…

New global server pointer and lifecycle functions for HTTP/RPC serverAdded graceful shutdown sequence with 30-second timeout and forced client cleanupAdded request-dispatcher mutex to protect dynamic handler replacement during shutdown
e5f242eeby Matthew Zipkin+178−62 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 →