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 15 AI analysisMessage 83 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

http: enclose libevent-dependent code in a namespace

This commit only moves existing HTTP server code into a new namespace called http_libevent. It does not change any behavior, fix any bug, or alter how the software handles network input. It is a pure code-organization change to make future…

89c54ae4by Matthew Zipkin+25−58 files
No security note in commit
Open full analysis →Source commit ↗
Informational 12 AI analysisMessage 66 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

http: Implement HTTPHeaders class

This commit introduces a new internal helper class for parsing and building HTTP headers in Bitcoin Core. It does not change any existing behavior or fix a known bug; it is purely new infrastructure code with tests. There is no indication …

New HTTP header parsing class with input validationRejects CR, LF, NUL characters in header linesRejects whitespace in header field names
68b5d289by Matthew Zipkin+247−03 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 66 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

http: Implement HTTPResponse class

This commit adds a new helper class for formatting HTTP response headers in Bitcoin Core's internal web server. It does not change any existing behavior or fix any known problem; it is purely new infrastructure code with accompanying tests.

ad50aa4aby Matthew Zipkin+76−04 files
No security note in commit
Open full analysis →Source commit ↗
Low 28 AI analysisMessage 66 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

http: Implement HTTPRequest class

This commit introduces a new HTTP request parser for Bitcoin Core's internal web server. It is a defensive, by-the-book implementation that explicitly rejects malformed request lines, bad HTTP versions, NUL bytes, conflicting Content-Lengt…

New HTTP request parser with strict validation of request line, version, headers, and bodyExplicit rejection of NUL bytes in request line to prevent C-string parser truncation issuesStrict HTTP version enforcement (major must be 1, minor 0-9, exactly one digit each)
9463e987by Matthew Zipkin+317−03 files
No security note in commit
Open full analysis →Source commit ↗
Informational 12 AI analysisMessage 83 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

http: Introduce HTTPServer class and implement binding to listening socket

This commit adds a new internal HTTPServer class to Bitcoin Core that handles low-level network socket binding and listening for the HTTP RPC server. It is a code refactoring/introduction change with no obvious security bug. The new code i…

No security-relevant signal: this is a structural/refactoring commit introducing a new server class.Code is unit-tested with mocked sockets, reducing test-side attack surface.No input parsing, authentication, authorization, cryptography, or consensus logic is modified.
f5bc0189by Matthew Zipkin+178−15 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 78 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

HTTPServer: implement and test AcceptConnection()

This commit adds a new internal method for accepting incoming HTTP connections and includes unit tests for it. It is a routine code refactoring and testing change with no apparent security relevance.

5a3aa1afby Matthew Zipkin+78−05 files
No security note in commit
Open full analysis →Source commit ↗
Informational 12 AI analysisMessage 72 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

test: cover common HTTP attacks and common malformed requests

This commit only adds new automated tests to Bitcoin Core. It does not change the actual server code that handles HTTP requests. The tests verify that the existing HTTP server correctly rejects or handles common web attacks such as path tr…

Adds regression tests for HTTP security boundary conditionsDocuments libevent leniency on duplicate Content-Length and line foldingNo changes to src/httpserver.cpp or any production HTTP handling code
881d4b6cby Matthew Zipkin+210−121 file
No security note in commit
Open full analysis →Source commit ↗
Moderate 57 AI analysisMessage 0 · Opaque
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

fix ar bugs

This commit fixes several bugs in the firmware of the Keystone 3 hardware wallet, mainly around how Arweave (AR) cryptocurrency keys and RSA prime numbers are handled. It replaces direct array indexing with safer lookups, adds checks for m…

Out-of-bounds index fix: ChainType enum no longer used directly as array index for g_chainTable/g_accountPublicInfoSensitive-data cleanup: RSA prime flash region and SE hash are erased when an account is deletedTamper-response expansion: anti_tamper erase loop now covers the new RSA primes hash page
26fffdc3by ww3512687+173−819 files
No security note in commit
Open full analysis →Source commit ↗
Informational 19 AI analysisMessage 72 · Adequate
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

chore: resume Zcash firmware version changes

This commit re-introduces Zcash-related firmware version reporting that had been temporarily reverted. It makes the device include its firmware version when generating Zcash wallet connection data and stamps the same version into every sig…

New build.rs reads src/config/version.h and panics if version macros are missing or non-u8Zcash account sync UR now carries device firmware versionSigned PCZT responses stamped with keystone:fw_version in global.proprietary
4ec3335fby soralit+384−269 files
No security note in commit
Open full analysis →Source commit ↗
Informational 19 AI analysisMessage 57 · Thin
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

chore: revert Zcash firmware version changes

This commit is a straightforward revert that removes a recently-added Zcash firmware-version reporting feature. It strips out code that embedded the Keystone firmware version into Zcash PCZT (partially-created transaction) responses and in…

Removal of compile-time firmware version extraction from src/config/version.h via build.rsRemoval of global.proprietary 'keystone:fw_version' stamp from signed Zcash PCZT responsesRemoval of device_version field from Zcash wallet-connection UR generation
71854807by soralit+26−3849 files
No security note in commit
Open full analysis →Source commit ↗
Informational 18 AI analysisMessage 51 · Thin
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Seal the Tag trait

This commit fixes a design bug in a Rust Bitcoin library. The library claimed a certain internal trait called Tag was 'sealed' (meaning only the library authors could add new types that satisfy it), but it actually was not sealed. The comm…

Trait sealing mismatch between documentation and implementationPrevents arbitrary user-defined types from satisfying the Tag traitDefensive API-hardening change with no direct exploit path visible in the diff
81f65b30by Mitchell Bagot+13−33 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 →