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
17865Commits captured
17284AI analyses
99High-risk findings · 30d
The watch feed

Changes worth understanding

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

17284 analyses
Highest risk·RSS
Informational 12 AI analysisMessage 78 · Adequate
LL Lightning LabsLND BitcoinLightning Network

bolt12: add InvoiceRequest message struct and TLV codec

This commit adds a new data structure and serialization code for BOLT 12 invoice requests in the LND Lightning node. It is purely an implementation of a protocol message format and includes a round-trip test. There is no indication in the …

6bb9c7e8by bitromortac+282−02 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 68 · Adequate
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Replace dyn fmt::Write with fmt::Formatter

This commit is a routine performance and code-quality refactor. It replaces dynamically-dispatched formatter parameters with concrete Rust formatter types so the compiler can inline the code. There is no security-relevant change: no new in…

22da6c4fby Mitchell Bagot+18−133 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 38 · Opaque
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

add 2.5.0 changelog

This commit only adds text to two changelog files describing a new firmware version (2.5.0). It does not change any executable code, configuration, or security controls. The changelog mentions improvements to dice-roll entropy validation a…

281163f3by bianminyan+57−02 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 40 · Thin
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

chore: bump beta version

This commit only changes a single number in a version header, increasing the beta version from 1 to 2. There is no code change that affects security, functionality, or behavior of the firmware.

5bd12887by soralit+1−11 file
No security note in commit
Open full analysis →Source commit ↗
Informational 21 AI analysisMessage 81 · Strong
LL Lightning LabsLND BitcoinLightning Network

github: bump gateway code-review to v0.4.4 (#10926)

This commit updates a GitHub Actions workflow that runs an automated code-review bot called 'gateway'. It bumps the bot's version from v0.4.3 to v0.4.4 and removes a hardcoded numeric 'installation_id'. The new version figures out the corr…

Hardcoded installation_id removed, reducing risk of using a wrong-organization GitHub App installationAction and runtime pinned to immutable commit SHAs (supply-chain best practice maintained)No changes to LND runtime, wallet, channel, or network code
5e1e827fby Suheb+7−41 file
No security note in commit
Open full analysis →Source commit ↗
Moderate 54 AI analysisMessage 100 · Strong
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

fix(zcash): sign shielded PCZTs without RoleSigner to fit the device stack

This commit fixes a crash in the Keystone hardware wallet when signing certain advanced Zcash transactions. The previous code used a heavy upstream signing helper that needed too much memory, causing the device to reset during an Orchard-t…

Stack overflow / device reset in signing task due to excessive stack usage by upstream RoleSignerReplacement of heavy upstream signer with lean in-repo low_level_signer to fit device stack budgetAddition of consensus-critical NU6.3 v6 Orchard/Ironwood sighash domains in pczt_ext
11592ebcby Adam Tucker+603−2173 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 50 · Thin
BC Bitcoin Corelibsecp256k1 BitcoinCryptographic libraries

scalar: correct `_scalar_get_bits_{limb32,var}` input condition docs

This commit only fixes two mistakes in the documentation comments above two internal helper functions. It changes the stated allowed ranges for the number of bits that can be read and the allowed sum of offset plus count. No actual code lo…

6a599a44by Sebastian Falbesoner+2−21 file
No security note in commit
Open full analysis →Source commit ↗
Informational 18 AI analysisMessage 45 · Thin
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

script: qa: Improve Key::Fingerprint type safety

This commit is a code-quality refactor, not a security fix. It replaces raw 4-byte fingerprint arrays with a named std::array type (KeyFingerprint) and adds helper methods to copy fingerprints safely. The behavior of fingerprint handling i…

No security-relevant behavior changeRefactor only: raw arrays replaced with std::arrayNo new validation, bounds checks, or cryptographic changes
c9a70f93by David Gumberg+56−5211 files
No security note in commit
Open full analysis →Source commit ↗
Informational 18 AI analysisMessage 88 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

nanobench: fix perf counter buffer init

This is a small bug fix in Bitcoin Core's internal benchmarking header (nanobench). The code intended to create three empty placeholder slots in some performance-counter buffers, but accidentally created a single slot containing the number…

off-by-one / initialization bug in low-level performance counter bufferpotential out-of-bounds read if default-constructed object is used before resizefix is defensive/correctness rather than reactive to an exploit
b6b1d065by Lőrinc+3−31 file
No security note in commit
Open full analysis →Source commit ↗
Moderate 57 AI analysisMessage 73 · Adequate
LDK Lightning Dev Kitrust-lightning BitcoinCryptographic librariesLightning Network

Lower strictness of pending monitor update while awaiting tx_signatures

This commit fixes a logic bug in the Lightning Dev Kit's channel splicing code. Previously, the code wrongly assumed that no unrelated monitor update could be pending when a splice `tx_signatures` message arrived while the channel was quie…

Assertion relaxation in state-machine handling of splice `tx_signatures`Race condition between unrelated HTLC preimage monitor update and splice signature exchangePotential panic or protocol stall due to overly strict debug assertion
b8a76c17by Wilmer Paulino+174−42 files
No security note in commit
Open full analysis →Source commit ↗
Low 45 AI analysisMessage 73 · Adequate
LDK Lightning Dev Kitrust-lightning BitcoinCryptographic librariesLightning Network

Remove expectance of interactive-tx commitment_signed during reestablish

This commit removes a small piece of bookkeeping in the Lightning channel code that tracked whether a peer's commitment signature was still expected during a channel re-establishment. The change says this extra signal is unnecessary becaus…

Change affects state tracking for commitment_signed receipt during channel reestablishChange removes a disconnect-expectancy signal in interactive-tx flowCommit message frames change as cleanup, not as a security fix
fab95959by Wilmer Paulino+0−41 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 68 · Adequate
LL Lightning LabsLND BitcoinLightning Network

htlcswitch: fix outgoing cltv spelling

This commit is a simple spelling cleanup. It renames a field called 'OutgoingCTLV' to the correctly spelled 'OutgoingCLTV' throughout the codebase and fixes related typos in comments. CLTV stands for 'CheckLockTimeVerify,' a Bitcoin time-l…

4518bc72by ziggie+29−2714 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 →