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
16888Commits captured
16830AI analyses
83High-risk findings · 30d
The watch feed

Changes worth understanding

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

16830 analyses
Highest risk·RSS
Low 31 AI analysisMessage 85 · Strong
EP Elements ProjectCore Lightning BitcoinLightning Network

wallet: make datastore helpers self-wrap a wallet transaction

This change fixes a crash bug in Core Lightning's wallet datastore helpers. Previously, four datastore functions required the caller to already be inside a database transaction, and would fatally crash if called outside one. The patch make…

Fixes fatal assertion/crash in database statement preparationResolves transaction-context mismatch in wallet datastore helperswatchman plugin persistence path was affected
ae1a3347by Sangbida Chaudhuri+23−11 file
No security note in commit
Open full analysis →Source commit ↗
Low 33 AI analysisMessage 73 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

lightningd: only run watchman under --experimental-bwatch

This commit gates a new experimental chain-watching subsystem called 'bwatch' behind an explicit --experimental-bwatch flag. Previously, the watchman helper was always created, which could have caused both the old chain watcher and the new…

Race condition between legacy chain watcher and new bwatch watcher prevented by gating watchman creation behind an opt-in flagwatchman_* entry points made NULL-safe so disabled code paths are explicit no-opsJSON RPC command now returns a controlled error instead of dereferencing a NULL watchman
92402cf6by Sangbida Chaudhuri+52−52 files
No security note in commit
Open full analysis →Source commit ↗
Low 44 AI analysisMessage 78 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

wallet: register scriptpubkey watches at startup

This change makes Core Lightning register long-lasting 'watches' for all wallet deposit addresses when the node starts up, so the new bwatch plugin can spot incoming payments from the first block it scans. It also removes a now-redundant p…

Change is part of an experimental chain-watcher (bwatch) featureAdds startup registration of scriptPubKey watches for all derived wallet keysRemoves a redundant unconfirmed-change watch, relying on the new blanket coverage
4a951d65by Sangbida Chaudhuri+89−114 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 83 · Strong
EP Elements ProjectCore Lightning BitcoinLightning Network

tests: update test_wallet.py raw-SQL queries for our_outputs

This commit only updates internal test code to query a new database table (our_outputs) instead of an old one (outputs). It does not change the actual wallet or node software that users run, so it cannot directly affect security.

d14ee378by Sangbida Chaudhuri+31−281 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 80 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

chore(core): update common/models.json

This commit simply adds a new Trezor hardware wallet model (Trezor Safe 7, internal code T3W1) to a JSON list of known device models and their color options. There is no code change that affects security, cryptography, or how the device op…

7227d950by Martin Milata+13−11 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 90 · Strong
KX KruxKrux BitcoinHardware wallets

perf(test): stub gc.collect during tests

This commit only changes test infrastructure. It replaces the garbage collector's collect() function with a no-op during automated tests so the test suite runs faster. It does not change any code that runs on real Krux devices or affect ho…

29e4d43bby odudex+13−12 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 95 · Strong
KX KruxKrux BitcoinHardware wallets

test: build embit's C libsecp256k1 for tests

This commit only changes how automated tests are run. It builds a C cryptography library during testing so the test environment matches the real firmware more closely. There is no change to the actual Krux firmware or wallet code, and no s…

ac3ea482by odudex+37−03 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 57 · Thin
KX KruxKrux BitcoinHardware wallets

ci: allow perf commit type

This change simply adds 'perf' to the list of allowed commit message types in a GitHub Actions workflow that checks whether commit messages follow a conventional format. It has no effect on the Krux software users run, on private keys, wal…

8e0ac0cbby odudex+1−11 file
No security note in commit
Open full analysis →Source commit ↗
Low 47 AI analysisMessage 81 · Strong
LDK Lightning Dev Kitrust-lightning BitcoinCryptographic librariesLightning Network

blinded_path: only compact introduction nodes via channels enabled both ways

This change fixes a bug in how Lightning blinded paths choose a compact reference to the introduction node. Previously, the code could pick an old channel that was disabled or effectively closed, making the resulting BOLT 12 offer or blind…

Blinded path reachability failureBOLT 12 offer path invalidationDisabled channel selection bug
0c352c55by Vincenzo Palazzo+161−01 file
No security note in commit
Open full analysis →Source commit ↗
Low 31 AI analysisMessage 72 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

feat(clear_signing): support sliced paths.

This commit adds a new feature to Trezor's Ethereum 'clear signing' system that lets wallet definitions extract a slice of bytes from a numeric parameter. For example, a 32-byte number that secretly packs an address into its last 20 bytes …

Feature adds ability to display only a byte slice of a larger numeric field, which can prevent UI spoofing when high bits of a packed value carry flags or a different addressNew validation rejects byte-slicing negative signed integersNo changelog entry and commit message frames change as a feature, not a security fix
017cf136by PrisionMike+244−426 files
No security note in commit
Open full analysis →Source commit ↗
Low 35 AI analysisMessage 62 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

feat(core): confirm ERC-8213 calldata digest if all data is shown

This commit adds a new user-facing safety feature for Trezor hardware wallets when signing Ethereum transactions. If the user chooses to view all the raw transaction data (calldata), the device will now also show a final cryptographic hash…

Adds user-verifiable calldata digest display (ERC-8213) to mitigate tampering of long Ethereum transaction dataHashes calldata with keccak256 seeded by total length, matching the ERC-8213 specification referenced in code commentsAdds a length-consistency check (confirmed_len == total_len) before displaying the digest
10c82eddby Roman Zeyde+194−3222 files
No security note in commit
Open full analysis →Source commit ↗
Informational 17 AI analysisMessage 68 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

gui: Add ExceptionSafeConnect that takes a lambda

This commit adds a helper function in Bitcoin Core's graphical user interface code that safely connects a Qt signal to an anonymous function (lambda). It wraps the function so that if it throws an exception, the error is caught and reporte…

Defensive exception handling added to prevent unhandled exceptions in lambda slotsNull-pointer guard added in PrintSlotException to avoid dereferencing a null receiverNo change to consensus, networking, wallet cryptography, or validation logic
5907a5c7by Ava Chow+37−12 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 →