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
17533Commits captured
17131AI analyses
88High-risk findings · 30d
The watch feed

Changes worth understanding

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

17131 analyses
Highest risk·RSS
Informational 15 AI analysisMessage 68 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

fuzz: clang-format LIMITED_WHILE

This commit is purely a code-style cleanup. It adds a space between the macro name LIMITED_WHILE and its opening parenthesis across many fuzz test files, plus a few tiny formatting fixes like removing a redundant semicolon and fixing inden…

fab8eeedby MarcoFalke+91−14265 files
No security note in commit
Informational 15 AI analysisMessage 55 · Thin
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

fuzz: Clang-format LIMITED_WHILE like while

This commit only changes a code-formatting configuration file. It tells the project's automatic formatting tool (clang-format) to treat the custom LIMITED_WHILE macro the same way it treats a normal 'while' loop when laying out code. There…

fa0d777cby MarcoFalke+1−01 file
No security note in commit
Informational 18 AI analysisMessage 60 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

fuzz: Remove unused workaround after fix in libmultiprocess byte-span serializer

This commit removes a temporary safety check in a fuzz test (automated randomized testing code) for Bitcoin Core's inter-process communication. The check avoided sending empty byte arrays because an external library had a bug that triggere…

Removal of a fuzz-test workaround for a UBSan issue in an external serializer libraryNo changes to production code paths, only test/fuzz harness codeComment references a now-resolved libmultiprocess byte-span serializer bug
fa1a9bdeby MarcoFalke+0−21 file
No security note in commit
Informational 15 AI analysisMessage 83 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

fuzz: Use LIMITED_WHILE over for-loop with consumed size integral

This commit is a minor style cleanup inside a fuzz test (a test that feeds random data to software to find bugs). It replaces a loop that reads a number from fuzz input with a standard helper that reads a single true/false byte each iterat…

fa55385aby MarcoFalke+1−31 file
No security note in commit
Informational 15 AI analysisMessage 72 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

test(core): check Optiga presence once per session

This commit is a minor internal test-framework cleanup. It moves a single check for whether the device under test has an Optiga security chip from one place to another, computing it once per test session instead of repeatedly. There is no …

e72f9596by Roman Zeyde+8−32 files
No security note in commit
Informational 15 AI analysisMessage 100 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

test(core): wait for `Cancel` response before sending `Ping`

This is a test-only change to the Python Trezor client library. It fixes a potential deadlock in test synchronization code by waiting for a response to a Cancel message before sending a Ping message. There is no change to device firmware o…

a6bffbcaby Roman Zeyde+15−121 file
No security note in commit
Low 26 AI analysisMessage 85 · Strong
EL ElectrumElectrum BitcoinSoftware wallets

swaps: destroy swap transport on failed initialization

This commit fixes a resource leak in Electrum's submarine-swap feature. When a connection to a swap server failed to start, the program was not properly cleaning up the connection object, so each failed attempt could leave behind leftover …

Resource leak on error pathMissing cleanup of background tasks after failed initializationPotential accumulation of leaked transports/connections per failed swap attempt
c5a38e5aby f321x+4−22 files
No security note in commit
Low 44 AI analysisMessage 85 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

fix(core): don't drop layout objects after `draw_simple()`

This commit fixes a bug in the Trezor hardware wallet's user-interface code. Previously, certain simple on-screen messages were wrapped in a Python `with` block, which caused the underlying layout object to be cleaned up (dropped) as soon …

Use-after-free / premature object drop of UI layout with active event-handling tasksPotential crash or UI freeze during security-sensitive prompts (passphrase entry, wait screens)Incorrect lifetime management across Rust/MicroPython boundary
155fa8d2by Roman Zeyde+15−287 files
No security note in commit
Informational 19 AI analysisMessage 91 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

Squashed 'src/ipc/libmultiprocess/' changes from 28e056576a..e8de5c7b68

This commit updates a helper library (libmultiprocess) used by Bitcoin Core. The only code change replaces a raw memory copy with a safer standard-library copy in a routine that converts byte arrays for inter-process communication. The res…

Replacement of memcpy with std::ranges::copy in byte-buffer serialization pathCommit message references a UBSan warning, suggesting prior undefined-behavior exposure during sanitiser buildsNew regression tests for Data and std::map serialization round-trips
6d5f7539by MarcoFalke+55−306 files
No security note in commit
Informational 15 AI analysisMessage 50 · Thin
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

ci: use uv 11.x

This commit updates the version of a Python packaging tool called 'uv' used inside Bitcoin Core's automated code-checking container image, from version 0.10 to version 0.11. It is a routine dependency bump in the continuous-integration (CI…

058a73a0by fanquake+1−11 file
No security note in commit
Informational 15 AI analysisMessage 57 · Thin
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

ci: use Ubuntu 26.04 for lint container

This commit simply updates the version of Ubuntu used by Bitcoin Core's automated linting (code style checking) container from 24.04 to 26.04. It is a routine CI/infrastructure maintenance change with no security relevance visible in the c…

900a7785by fanquake+1−11 file
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