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
18285Commits captured
17497AI analyses
106High-risk findings · 30d
The watch feed

Changes worth understanding

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

17497 analyses
Highest risk·RSS
Moderate 61 AI analysisMessage 85 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Fix buffer bug in encoding::decode_from_read_unbuffered_with

This commit fixes a bug where a Bitcoin data decoder could silently ignore parts of incoming data. The decoder only processed each chunk of data once, but some decoders don't finish a chunk in one go. Leftover bytes were effectively droppe…

Data truncation / silent dropping of unconsumed decoder inputInconsistent handling between `decode_from_read_unbuffered_with` and `decode_from_hex`Potential acceptance of incomplete or malformed consensus-encoded data
3ddab5d8by Mitchell Bagot+5−61 file
No security note in commit
Open full analysis →Source commit ↗
Informational 11 AI analysisMessage 95 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Add regression test for decode_from_read_unbuffered_with bug

This commit only adds a regression test for a previously existing bug in a decoding helper. It does not change any production code, so by itself it cannot introduce a security vulnerability. The test documents a bug where a decoder could l…

No production code changesRegression test onlyHistorical decoder byte-loss bug referenced in commit message
29314bbeby Mitchell Bagot+62−01 file
No security note in commit
Open full analysis →Source commit ↗
Informational 11 AI analysisMessage 95 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Add regression test for decode_from_read_unbuffered_with bug

This commit only adds a new regression test for an already-fixed bug in a Rust Bitcoin IO decoding function. It does not change any production code, so by itself it cannot introduce or fix a security vulnerability. The test documents a sub…

Regression test for prior bug in decode_from_read_unbuffered_withNo production code changesCustom decoder with partial byte consumption and read_limit smaller than remaining need
4b71a5adby Mitchell Bagot+60−01 file
No security note in commit
Open full analysis →Source commit ↗
Moderate 57 AI analysisMessage 45 · Thin
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

change the se config and usage

This firmware update changes how the Keystone hardware wallet stores and checks device passwords. Previously, the device kept a separate password hash page in its secure element (SE) storage. After this update, password verification is don…

Removal of stored password hash page and migration to secret-decryption password verificationAddition of legacy password hash wipe routine on bootSE error codes propagated instead of asserted, improving fault handling
24f68a8eby aaron+279−12514 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 92 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

ci: Use GCC consistently in i686 task

This commit changes a Bitcoin Core continuous integration (CI) test script to use the GCC compiler instead of Clang for a 32-bit Intel (i686) build. It removes the Clang/LLVM packages and compiler flags from the CI environment. There is no…

fae482b4by MarcoFalke+1−31 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 50 · Thin
LL Lightning LabsLND BitcoinLightning Network

dev.Dockerfile: use cache mounts to speed up rebuilding

This change only modifies the developer Dockerfile to use Docker BuildKit cache mounts for Go build caches, making image rebuilds faster. It is a build-performance improvement with no security relevance.

20e65186by ZZiigguurraatt+18−12 files
No security note in commit
Open full analysis →Source commit ↗
Low 35 AI analysisMessage 73 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

argsman: Prevent duplicate option registration across categories

This commit adds a safety check in Bitcoin Core's command-line option parser to prevent the same option name from being registered in more than one category. Previously, an option could accidentally be defined twice under different categor…

Defensive assertion added to prevent ambiguous option resolutionPrevents cross-category duplicate option registrationCould mitigate misconfiguration or option-shadowing issues
32df86f1by Pablo Martin+5−01 file
No security note in commit
Open full analysis →Source commit ↗
Low 32 AI analysisMessage 73 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

mining: add reason and debug output to submitSolution

This commit changes the internal mining interface so that when a miner submits a solved block through the IPC interface, the caller now receives a specific rejection reason (like 'bad-version', 'duplicate', or 'inconclusive') instead of ju…

Interface versioning change to prevent old IPC clients from decoding corrupt result fieldsDeprecated stub throws explicit runtime error instead of silently returning incompatible dataReturn value semantics changed: submitSolution now returns true only for accepted new blocks, not duplicates
cbaa1696by w0xlt+75−305 files
No security note in commit
Open full analysis →Source commit ↗
Informational 18 AI analysisMessage 80 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

refactor: centralize SubmitBlock result handling

This is a small internal cleanup in Bitcoin Core's block submission code. It moves a duplicate-check and success-calculation that existed in two places into a single shared helper function. The visible behavior for the mining RPCs is inten…

Refactor of block submission success criteriaRemoves new_block output parameter from SubmitBlock helperCentralizes accepted/new-block/reason consistency check in one function
ed75d70fby w0xlt+12−203 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 50 · Thin
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

doc: add release note for submitSolution IPC changes

This commit only adds a release note describing a previous change to the inter-process communication (IPC) interface for submitting block solutions. It does not change any code, behavior, or configuration. There is no security issue in thi…

75929b11by woltx+11−01 file
No security note in commit
Open full analysis →Source commit ↗
Informational 24 AI analysisMessage 80 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

mining: clarify SubmitBlock result handling

This Bitcoin Core commit tightens how the mining interface reports whether a submitted block succeeded or failed. Previously, a block could be accepted but not connected to the chain (for example, a valid but lower-work 'stale' block), and…

Adds explicit invariant check between success result and BIP22 rejection reasonClarifies ambiguous block-submission outcomes that could mislead mining clientsDocuments synchronous BlockChecked emission to prevent future unsafe unregistration assumptions
83f3bc00by w0xlt+46−93 files
No security note in commit
Open full analysis →Source commit ↗
Moderate 66 AI analysisMessage 100 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

fix: off-by-one in MedianTimePast::is_satisfied_by

This commit fixes a one-unit boundary error in how rust-bitcoin decides whether a time-based transaction lock has expired. The code previously treated 'lock time equal to median time past' as satisfied, but Bitcoin's BIP-113 rule requires …

Consensus-rule mismatch with Bitcoin Core (BIP-113)Off-by-one boundary error in locktime validationPotential transaction broadcast/mempool rejection
66a8ee70by Alexey Gradoboev+41−51 file
Vendor flagged security relevance
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 →