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.

24Projects watched
17784Commits captured
17252AI analyses
98High-risk findings · 30d
The watch feed

Changes worth understanding

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

17252 analyses
Highest risk·RSS
Informational 18 AI analysisMessage 41 · Thin
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Close FromHexError

This commit is a routine API design change, not a security fix. It renames an internal error enum and wraps it in a private struct so the library can keep the error type flexible before its first stable release. No vulnerability is patched…

No security-relevant keywords in commit title or messageNo bounds checks, input validation, or cryptographic logic changedNo memory-safety, panic, or unsafe-code modifications
f0e8e7bcby Mitchell Bagot+66−324 files
No security note in commit
Informational 15 AI analysisMessage 73 · Adequate
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Add ExactSizeEncoder impl for Option<T: ExactSizeEncoder>

This commit adds a small, harmless feature to a Rust Bitcoin encoding library. It lets an optional encoder report its length when it has a value, and report zero length when it is empty. There is no security issue here.

574415eaby Mitchell Bagot+17−05 files
No security note in commit
Informational 15 AI analysisMessage 60 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

fuzz: add coins_view_stacked fuzz harness to test concurrent leveldb reads

This commit adds a new automated test (a fuzzing harness) for Bitcoin Core's coin database view. It does not change any production code, user-facing behavior, or network protocol. It only adds a test that exercises reading the LevelDB-back…

0e109371by Andrew Toth+22−01 file
No security note in commit
Informational 15 AI analysisMessage 28 · Opaque
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

doc: add release notes

This commit only adds a release note describing a performance improvement for block validation. It contains no code changes, no bug fixes, and no security-related content.

dc1c17c0by Andrew Toth+8−01 file
No security note in commit
Low 29 AI analysisMessage 80 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

coins: add ready flag to InputToFetch

This is a preparatory code change for future multi-threaded coin fetching in Bitcoin Core. It adds a synchronization flag (std::atomic_flag) around a shared data field so that worker threads can safely signal when they have finished writin…

Concurrency synchronization added for shared coin fieldUse of release/acquire atomic semantics to prevent data racesPreparation for multi-threaded ProcessInput execution
fdf28303by Andrew Toth+15−01 file
No security note in commit
Informational 16 AI analysisMessage 68 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

coins: fetch inputs in parallel

This commit changes how Bitcoin Core fetches transaction input data (the 'coins' spent by transactions in a block). Instead of doing all lookups one-by-one on the main thread, it now submits the work to a thread pool. The change is describ…

New concurrent shared state (m_inputs, m_input_head, m_input_tail, m_futures) across multiple worker threads and the main threadFallback path on thread-pool submission failure clears shared state and logs a warningAddition of destructor and Flush override that must correctly synchronize with running workers
ab2a3792by Andrew Toth+48−52 files
No security note in commit
Informational 15 AI analysisMessage 65 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

doc: update CoinsViewOverlay docstring to describe parallel fetching

This commit only updates a code comment (docstring) in a header file. It explains how a new parallel coin-fetching mechanism works. No actual code logic was changed, so it cannot introduce or fix a security vulnerability on its own.

d69a3b20by Andrew Toth+54−51 file
No security note in commit
Informational 15 AI analysisMessage 87 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

test: add unit tests for CoinsViewOverlay::StartFetching

This commit only adds and updates unit tests for an existing Bitcoin Core component called CoinsViewOverlay. It does not change any production code that runs on the live Bitcoin network, so it cannot directly introduce a security vulnerabi…

760fb22dby Andrew Toth+135−31 file
No security note in commit
Informational 14 AI analysisMessage 75 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

fuzz: update harnesses to cover CoinsViewOverlay::StartFetching

This commit only changes Bitcoin Core's internal fuzz tests—specialized randomized test programs used during development to catch bugs. It adds test coverage for a new caching helper called CoinsViewOverlay::StartFetching. There is no chan…

No production code changesOnly fuzz-test harnesses modifiedAdded test coverage for CoinsViewOverlay::StartFetching
ce610a6fby Andrew Toth+107−122 files
No security note in commit
Informational 12 AI analysisMessage 73 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

validation: collect block inputs in CoinsViewOverlay before ConnectBlock

This commit is a performance optimization for Bitcoin Core's block validation. It pre-fetches the previous transaction outputs (the 'coins' being spent) for all inputs in a block before the main validation work begins, and it does so in pa…

ede11b83by Andrew Toth+101−34 files
No security note in 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