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
17976Commits captured
17340AI analyses
102High-risk findings · 30d
The watch feed

Changes worth understanding

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

17340 analyses
Highest risk·RSS
Informational 19 AI analysisMessage 65 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

wallet: Make CWalletTx "comment" and "to" member variables

This commit is a straightforward internal cleanup in Bitcoin Core's wallet code. It moves two optional user-provided text fields, 'comment' and 'to', out of a generic key/value map and into explicit named member variables on the wallet tra…

No security-relevant behavior change observedRefactor only: same data stored and exposed via same RPC keysBackward-compatible serialization preserved
7ef8a6efby Ava Chow+30−158 files
No security note in commit
Open full analysis →Source commit ↗
Informational 18 AI analysisMessage 65 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

wallet: Make CWalletTx "from" and "message" member variables

This is a small code cleanup in Bitcoin Core's wallet. It moves two very old, rarely-used pieces of transaction metadata—'from' and 'message'—out of a generic key/value map and into explicit named fields. The change preserves the same data…

No security-relevant change: pure refactor of deprecated metadata fieldsHTML escaping of 'from' and 'message' remains unchanged in Qt UIBackward-compatible serialization preserves existing wallet data
2155e913by Ava Chow+30−146 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 73 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

wallet: Pass comment and comment_to to CommitTransaction

This is a routine internal code cleanup in Bitcoin Core's wallet. It changes how optional user comments (like a note on a payment) are passed through the code, moving them from a generic key-value map to explicit function parameters. The a…

00abb174by Ava Chow+20−113 files
No security note in commit
Open full analysis →Source commit ↗
Informational 18 AI analysisMessage 68 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

wallet: Drop mapValue from CommitTransaction

This is a routine internal code cleanup in Bitcoin Core's wallet. It removes an old way of passing extra transaction details (called mapValue) and replaces it with explicit named parameters. The change does not alter what the wallet record…

No security-relevant behavior change: same mapValue keys are still written to the wallet transaction recordRefactor-only signature change: removal of generic mapValue parameter in favor of explicit optional parametersNo validation, cryptography, consensus, or networking code modified
c6ba98dcby Ava Chow+8−128 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 73 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

wallet: Pass replaces_txid to CommitTransaction outside of mapValue

This is a small internal code cleanup in Bitcoin Core's wallet. It changes how a transaction ID is passed when a user bumps a transaction fee, moving the value from a general metadata map into a dedicated function parameter. There is no se…

1a219a37by Ava Chow+15−63 files
No security note in commit
Open full analysis →Source commit ↗
Informational 20 AI analysisMessage 73 · Adequate
LDK Lightning Dev Kitrust-lightning BitcoinCryptographic librariesLightning Network

Avoid heap-allocating background processor futures

This is a routine performance and code-quality improvement. It replaces heap-allocated 'boxed' futures with stack-pinned futures in a background processor loop, removing one memory allocation per loop iteration. There is no security vulner…

3cad6af6by Abeeujah+90−811 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 68 · Adequate
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

consensus_encoding: always enable alloc for serde

This is a small build-configuration cleanup, not a security fix. The change makes the 'alloc' feature automatically enabled whenever the 'serde' feature is enabled, because serializing to non-human-readable formats requires allocating memo…

d6730d68by Nick Johnson+2−23 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 60 · Adequate
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Add recent 0.32.x releases to relevant changelogs

This commit only edits changelog Markdown files. It documents that several prior releases were yanked from crates.io because their required Rust version was raised too aggressively, and it adds notes about newer replacement releases. There…

0c39a2bdby Nick Johnson+79−25 files
No security note in commit
Open full analysis →Source commit ↗
Informational 18 AI analysisMessage 68 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

coins: pass UTXO stats view by reference

This commit is a small code-quality refactor in Bitcoin Core. It changes several UTXO-statistics helpers so they take a database view by reference instead of by pointer. That removes the possibility of passing a null pointer and makes the …

API hardening: pointer-to-reference conversion removes a nullability contractNo memory-safety bug demonstrated in the diffNo consensus, P2P, wallet, or RPC semantic changes visible
3d2f2d8dby Lőrinc+19−246 files
No security note in commit
Open full analysis →Source commit ↗
Informational 13 AI analysisMessage 68 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

coins: drop stale cursor null checks

This is a small cleanup change in Bitcoin Core that removes leftover null checks after a previous refactor made database cursors always return a valid object. There is no security issue in the diff itself.

72db4accby Lőrinc+1−52 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 78 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

coins: drop cursor from base view

This commit is a routine code cleanup. It removes an unused cursor-iteration method from the base coin-view interface and its empty/forwarding/throwing implementations, keeping the method only on the concrete database class that actually s…

35aedb28by Lőrinc+2−163 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 78 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

coins: pass DB view to cursor users

This is a small internal code cleanup in Bitcoin Core. It changes several functions that compute UTXO (unspent transaction output) statistics so they accept a more specific database-view pointer instead of a generic one, because only the c…

c6fbe2f6by Lőrinc+8−74 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 →