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
18168Commits captured
17444AI analyses
103High-risk findings · 30d
The watch feed

Changes worth understanding

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

17444 analyses
Highest risk·RSS
Low 47 AI analysisMessage 85 · Strong
LL Lightning LabsLND BitcoinLightning Network

discovery: fix panic in DNS fallback SRV lookup

This commit fixes a bug in LND's DNS seed bootstrap code that could crash the node. The code assumed every record in a DNS response was an SRV record, so a non-SRV record (like a normal A or CNAME record) would cause a panic. The fix safel…

Unconditional type assertion panic in DNS fallback pathMissing bounds check on LookupHost result before array indexingMissing network deadline on manually dialed DNS TCP connection
2a3642c6by Erick Cestari+252−52 files
Vendor flagged security relevance
Open full analysis →Source commit ↗
Moderate 60 AI analysisMessage 78 · Adequate
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Clear pushnum cache on signature operations in sigop count

This commit fixes a bug in how the library counts 'signature operations' (sigops) in Bitcoin scripts. A small cache that remembers recently pushed numbers was not being cleared after signature-checking opcodes. This could cause a later mul…

Consensus-critical code path modified (transaction/script sigop counting)Mismatch with Bitcoin Core consensus logic explicitly cited in commit messageStale-cache bug could produce incorrect sigop counts
7c8db561by Abeeujah+12−02 files
No security note in commit
Open full analysis →Source commit ↗
Informational 18 AI analysisMessage 73 · Adequate
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Adjust PartialMerkleTree arbitrary to satisfy decode checks

This commit fixes a test-only code generator for a Bitcoin network data structure so that the generated examples respect the same padding rule used by the real decoder. It only affects fuzz/property tests and does not change production par…

Invariant mismatch between decoder and arbitrary generatorTest-only arbitrary feature code changeNo production parsing or consensus code modified
23c05e7aby Mitchell Bagot+5−11 file
No security note in commit
Open full analysis →Source commit ↗
Informational 24 AI analysisMessage 68 · Adequate
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Prevent panic in UserAgent arbitrary

This commit fixes a panic (crash) in a test-only feature called 'arbitrary' that generates random fake user-agent strings for fuzz testing. The panic happened because the random generator could produce characters or lengths that the UserAg…

Denial-of-service-like panic in test/fuzz generation pathInput sanitisation bypass in derived/test trait implementationLength and character validation mismatch between Arbitrary and constructor
eee88730by Mitchell Bagot+13−11 file
No security note in commit
Open full analysis →Source commit ↗
Informational 16 AI analysisMessage 68 · Adequate
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Adjust AddrV2 arbitrary to satisfy decode checks

This commit fixes a mismatch in test-only code between how fake network addresses are randomly generated and how the real decoder validates them. It does not change any production parsing or network logic, so it cannot be exploited by an a…

Test-only Arbitrary impl aligned with decoder invariantsNo change to production decode/encode/network logicPrevents generation of invalid-but-craftable address variants during fuzz/property tests
15b56636by Mitchell Bagot+18−211 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 45 · Thin
LD LedgerLedger Bitcoin app BitcoinHardware wallets

[auto-update] Update Ragger snapshots

This commit only updates five test snapshot images used by the Ragger automated testing framework. These are expected screen captures for a test named 'test_sighash_none_rejected_by_default' across different Ledger device models. There are…

df859c3bby github-actions[bot]+0−05 files
No security note in commit
Open full analysis →Source commit ↗
Informational 12 AI analysisMessage 60 · Adequate
LD LedgerLedger Bitcoin app BitcoinHardware wallets

SIGHASH gating: status screen on disabled rejection - tests

This commit only adds a new automated test that checks the on-device error screen shown when a user tries to sign a Bitcoin transaction with a non-standard SIGHASH type while the non-standard SIGHASH setting is disabled. It does not change…

Test-only changeVerifies existing rejection of non-standard SIGHASH when setting disabledNo modification to signing/gating code
ef9d1eccby Ilya Artemov+19−11 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 50 · Thin
LD LedgerLedger Bitcoin app BitcoinHardware wallets

SIGHASH gating: status screen on disabled rejection

This commit is a user-experience improvement, not a security fix. When a Bitcoin transaction uses a non-standard sighash and the user has not enabled the 'Allow non-standard sighash' setting, the app already rejected the transaction. Now i…

0e35a24dby Ilya Artemov+28−04 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 45 · Thin
LD LedgerLedger Bitcoin app BitcoinHardware wallets

SIGHASH gating: update Ragger snapshots

This commit only updates test screenshot snapshots for the Ledger Bitcoin app. It does not change any application code, so it cannot directly fix or introduce a security vulnerability. The snapshots show what the device screen looks like d…

Only binary image files changed in tests/snapshotsNo source code, Makefile, linker script, or CI configuration changesFilenames indicate the change is test collateral for a SIGHASH gating feature
84e9bc7cby github-actions[bot]+0−0177 files
No security note in commit
Open full analysis →Source commit ↗
Moderate 57 AI analysisMessage 18 · Opaque
CK CoinkiteCOLDCARD firmware BitcoinHardware wallets

bugfix: p2pk

This commit fixes a bug in the COLDCARD hardware wallet that prevented it from correctly signing Bitcoin transactions that spend from 'pay-to-public-key' (P2PK) outputs. P2PK is an older, uncommon output type where coins are locked directl…

Bugfix explicitly described in release notes as 'P2PK signing was broken'P2PK scriptPubKey parsing now supports both compressed and uncompressed public keysPubkey comparison logic corrected for uncompressed P2PK keys
0d04e5e1by scgbckbone+268−328 files
Vendor flagged security relevance
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 35 · Opaque
LD LedgerLedger Bitcoin app BitcoinHardware wallets

SIGHASH gating: tests_mainnet

This commit only updates a test script that navigates the Ledger device's on-screen dashboard. It adds extra button presses to account for a new 'App settings' menu item that appears before 'App info'. There is no change to the actual Bitc…

b67c7982by Ilya Artemov+4−01 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 45 · Thin
LD LedgerLedger Bitcoin app BitcoinHardware wallets

SIGHASH gating: functional tests

This commit only adds automated functional tests for a new device setting that controls whether non-standard Bitcoin signature hash (sighash) types are allowed. It does not change the app code that runs on the Ledger device, so it cannot i…

Tests for gating of non-standard sighash typesDefault-deny behavior verified for SIGHASH_NONE, SIGHASH_SINGLE, ANYONECANPAY variantsNo modification to device-side signing logic in this commit
cb60be9aby Ilya Artemov+385−03 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 →