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 →
23Projects watched
16913Commits captured
16841AI analyses
83High-risk findings · 30d
The watch feed

Changes worth understanding

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

16841 analyses
Highest risk·RSS
Low 48 AI analysisMessage 65 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

p2p: trigger possible eviction if we support bloom filters and change a peer to tx relay

This Bitcoin Core patch fixes a small logic gap in peer-to-peer connection management. When a node supports bloom filters, a peer could switch itself into transaction-relaying mode at runtime without the node checking whether it already ha…

Adds missing capacity-based eviction trigger after peer capability changeFunctional test verifies connection drop after filterload messageOnly affects nodes running with -peerbloomfilters enabled
3ed7f064by Martin Zumsande+15−02 files
No security note in commit
Open full analysis →Source commit ↗
Informational 12 AI analysisMessage 87 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

test: add test that EvictTxPeerIfFull only evicts tx-relaying peers

This commit only adds a new automated test to Bitcoin Core. It checks that when the node is full of block-only peers (peers that do not relay transactions), an incoming connection is rejected rather than incorrectly kicking out a block-onl…

69ce0dbaby brunoerg+21−01 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 45 · Thin
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

doc: Update docs that refer to -maxconnections

This commit only updates two documentation files to reflect that the default value for the -maxconnections setting changed from 125 to 200. It does not change any code, configuration defaults, or network behavior. There is no security issu…

c1150840by Martin Zumsande+4−32 files
No security note in commit
Open full analysis →Source commit ↗
Low 39 AI analysisMessage 100 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

feat(solana): migrate to off-chain message signing v1

This commit updates Trezor's Solana off-chain message signing feature from an older version (v0) to a newer version (v1). It changes how messages are packaged and sent to the device: instead of the computer app formatting the message and s…

Protocol version migration removes OCMS v0 parsing and envelope handlingFirmware now performs its own serialization of off-chain signing payloads, reducing trust in host-side formattingOld protobuf field 2 (raw OCMS v0 bytes) is reserved/deprecated
d289db4bby Jakub Janků+1378−150824 files
No security note in commit
Open full analysis →Source commit ↗
Informational 21 AI analysisMessage 62 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

fix(nordic): update mcuboot - fixes trezor crypto compatibility

This commit simply updates two configuration files to point the Nordic (nRF) hardware build at newer revisions of Trezor's fork of the MCUboot bootloader. The commit message says it 'fixes trezor crypto compatibility' but gives no details,…

Bootloader dependency update for hardware wallet firmwareCommit message mentions 'crypto compatibility' but no vulnerability or CVENo source-code changes visible in the supplied diff
d6033024by tychovrahe+2−22 files
No security note in commit
Open full analysis →Source commit ↗
Informational 16 AI analysisMessage 45 · Thin
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

guix: disable-lto in *-base-gcc

This commit changes the build setup for Bitcoin Core's Guix reproducible-build toolchain so that the base GCC compilers used to build release binaries are compiled without Link-Time Optimization (LTO). LTO can sometimes make builds behave …

Build toolchain hardeningReproducibility improvementLTO disabled in base GCC packages
7dc87f8eby fanquake+2−01 file
No security note in commit
Open full analysis →Source commit ↗
Informational 18 AI analysisMessage 45 · Thin
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

guix: disable-nls in *-base-gcc

This commit changes the Bitcoin Core build setup for Guix (a reproducible build system) by adding '--disable-nls' when compiling the base GCC compiler used in the build process. NLS stands for Native Language Support, which provides transl…

Build toolchain hardeningReduction of locale-dependent build variabilityNo explicit vulnerability or exploit described
e0b8fbdeby fanquake+2−01 file
No security note in commit
Open full analysis →Source commit ↗
Informational 16 AI analysisMessage 50 · Thin
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

guix: mirror some arguments from linux-gcc to mingw-w64-gcc

This commit adjusts the build settings used to compile the Windows version of Bitcoin Core's toolchain. It copies some hardening and cleanup options from the Linux build configuration to the Windows (MinGW) build configuration, and reorder…

Adds stack-smashing protection default (--enable-default-ssp=yes) to Windows toolchainAdds host bind-now hardening (--enable-host-bind-now=yes) to Windows toolchainDisables unused/extra runtime components (gcov, libgomp, lto, nls, libsanitizer, gprofng) in Windows toolchain
9c258963by fanquake+7−51 file
No security note in commit
Open full analysis →Source commit ↗
Informational 16 AI analysisMessage 81 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

guix: pass --disable-tm-clone-registry to base GCC

This commit changes how Bitcoin Core's reproducible build system compiles its own copy of the GCC compiler. It adds a flag that removes unused support for 'transactional memory' from a low-level compiler helper library. This is a build-har…

Build toolchain hardeningReduction of unused libgcc surface areaNo runtime code change in Bitcoin Core
baa5a2ceby fanquake+1−01 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 45 · Thin
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

guix: modernise style in *-base-gcc

This commit is a cosmetic/style update to the Guix build manifest used to compile Bitcoin Core. It replaces older Scheme quoting syntax with newer 'gexp' syntax but does not change which compiler flags are actually used. There is no securi…

9ed3d6efby fanquake+21−211 file
No security note in commit
Open full analysis →Source commit ↗
Informational 18 AI analysisMessage 50 · Thin
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

fix potential date formatting concurrency issue on backup

This commit fixes a rare threading bug in how Sparrow Wallet names its automatic wallet backups. The old code used a date formatter that is not safe when multiple threads use it at the same time, which could in theory produce a malformed b…

Thread-safety fix for shared date formatterUse of non-thread-safe SimpleDateFormat in backup path replacedNo input from untrusted sources is parsed or formatted
1b8e9b52by Craig Raw+7−71 file
No security note in commit
Open full analysis →Source commit ↗
Informational 18 AI analysisMessage 62 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

refactor(core): make power manager driver selectable

This is a code reorganization in Trezor's firmware that moves the existing power-management implementation from a folder named after the STM32U5 chip to a folder named after the actual power-management chip (Nordic nPM1300). It also makes …

Large file move/rename with near-identical contentBuild-system feature gating added for PMIC and power-manager driversBoard configuration now explicitly selects npm1300 PMIC and power-manager backend
4941ceacby tychovrahe+1637−16159 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 →