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
17534Commits captured
17131AI analyses
88High-risk findings · 30d
The watch feed

Changes worth understanding

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

17131 analyses
Highest risk·RSS
Informational 15 AI analysisMessage 68 · Adequate
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

consensus-encoding: Bump version to 1.1.0

This commit is a routine version bump for the bitcoin-consensus-encoding crate from 1.0.0 to 1.1.0. It only updates the package version, changelog, and lock files. There are no code changes in this commit, and nothing in the commit itself …

a94e3ca7by Tobin C. Harding+53−384 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 36 · Opaque
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Add agent skills (#7454)

This commit reorganizes internal documentation for AI coding assistants. It moves existing developer guidance from one file into separate 'skill' files and adds new style guides for frontend naming and test writing. No application code, co…

66fb6426by Nicolas Dorier+158−456 files
No security note in commit
Open full analysis →Source commit ↗
Informational 20 AI analysisMessage 65 · Adequate
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Add SearchFiltersPMO to avoid repeat (#7453)

This commit is mostly a code cleanup and test-helper refactor. It introduces a shared test helper for search filters, switches many HTML IDs to CSS classes for easier testing, fixes a duplicate date-range filter bug, and changes a Telegram…

No security-relevant code paths modified (auth, authz, crypto, input validation, output encoding)Refactoring-only: CSS class additions and test helper extractionMinor behavior change: SearchString.RemoveDups('daterange') prevents duplicate date-range filters
64af6e29by Nicolas Dorier+236−15015 files
No security note in commit
Open full analysis →Source commit ↗
Informational 19 AI analysisMessage 57 · Thin
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

fix: warn before prove ownership wipe

This commit only changes on-screen text shown during the 'Prove Device Ownership' step of a password reset. The new wording warns the user that entering the wrong PIN/password too many times will wipe the device. It does not change any sec…

UI text change onlyAdds explicit wipe warning to ownership-proof stepNo logic or threshold changes for PIN/password attempts
a7d6a931by aaron+8−82 files
No security note in commit
Open full analysis →Source commit ↗
Moderate 64 AI analysisMessage 73 · Adequate
BT btcsuitebtcd BitcoinNode implementations

psbt: avoid blocking reads and unbounded allocations in NewFromRawBytes

This commit fixes two problems in the way btcd reads Partially Signed Bitcoin Transactions (PSBTs). First, the parser could hang forever when reading from a network connection or pipe because it tried to read one extra byte to check for le…

Denial-of-service via blocking read on open stream (potential infinite hang)Denial-of-service via unbounded memory allocation on base64 input before validationStrict parsing hardening for PSBT base64 decoding
2ddf73f3by Olaoluwa Osuntokun+87−283 files
Vendor flagged security relevance
Open full analysis →Source commit ↗
Low 34 AI analysisMessage 73 · Adequate
BT btcsuitebtcd BitcoinNode implementations

blockchain: tolerate trailing bytes when loading stored blocks

This commit changes btcd so that when it reads old blocks from its own database, it ignores any extra bytes tacked onto the end of the stored block data instead of refusing to start. Older versions of btcd sometimes saved blocks with extra…

Relaxation of strict deserialization for locally stored blocksTrailing bytes are logged, ignored, and excluded from cached serializationBlock size metric recomputed from cleaned serialization
a3bed5e3by Olaoluwa Osuntokun+117−132 files
No security note in commit
Open full analysis →Source commit ↗
Low 41 AI analysisMessage 73 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

lightningd: cancel watching original funding when we switch to the new one via splice.

This commit fixes a crash in Core Lightning that can happen when a user splices a channel that hasn't been publicly announced yet. Splicing is an experimental feature that changes a channel's funding transaction. The bug caused the program…

Assertion/crash in funding_depth_cb due to stale funding tx watchSplicing on non-announcable channels triggers inconsistencyChangelog-EXPERIMENTAL labels this as a crash fix
3226d686by Rusty Russell+20−02 files
No security note in commit
Open full analysis →Source commit ↗
Informational 18 AI analysisMessage 90 · Strong
EP Elements ProjectCore Lightning BitcoinLightning Network

common: add randbytes() wrapper to override cryptographic entropy: $CLN_DEV_ENTROPY_SEED

This commit adds a developer-only feature that lets programmers override the randomness source used by Core Lightning during testing, via an environment variable. It is explicitly gated behind 'developer mode' and is not intended for produ…

New cryptographic-randomness override mechanism, but explicitly developer-mode onlyEnvironment-variable seeding could reduce entropy if accidentally enabled in productionNo production code changes visible in the diff
1c925e0aby Rusty Russell+29−05 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 65 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

global: replace randombytes_buf() with randbytes() wrapper.

This commit only adds a new header include (<common/randbytes.h>) to 24 test files. It does not change any production code, cryptographic operations, or runtime behavior. The change is a test-infrastructure refactor to support deterministi…

72fd8b5cby Rusty Russell+24−024 files
No security note in commit
Open full analysis →Source commit ↗
Informational 19 AI analysisMessage 95 · Strong
EP Elements ProjectCore Lightning BitcoinLightning Network

common: seed deterministic RNG from basename of argv0, not full path

This change fixes a test-flakiness bug in a developer-only random-number override used during testing. It makes the random stream depend only on the program name, not the full file path, so tests produce the same results on different compu…

No security-relevant signal: change is in a developer override for deterministic testing RNGNo memory safety, authentication, authorization, or cryptographic weakness introducedNo incident or vulnerability disclosure referenced
4ca60ba6by ShahanaFarooqui+11−21 file
No security note in commit
Open full analysis →Source commit ↗
Low 37 AI analysisMessage 83 · Strong
EP Elements ProjectCore Lightning BitcoinLightning Network

common: don't consume deterministic randbytes stream for trace ids

This change fixes a subtle bug in Core Lightning's tracing code. When running with a special developer-only deterministic randomness override (CLN_DEV_ENTROPY_SEED), trace IDs were being drawn from the same predictable random stream used f…

Deterministic RNG stream contamination by observability codeTransaction output divergence between instrumented and non-instrumented buildsDeveloper-only entropy override affecting reproducibility of transaction generation
23b4b38aby ShahanaFarooqui+18−31 file
No security note in commit
Open full analysis →Source commit ↗
Informational 19 AI analysisMessage 73 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

common: don't trigger siphash_seed() init from span hashing either.

This is a small bug-fix commit in Core Lightning's tracing code. It fixes a situation where enabling tracing accidentally changed the sequence of random numbers used elsewhere in the program, causing test outputs to differ between builds w…

No direct memory safety issueNo input validation bypassNo authentication or authorization change
e54fe678by ShahanaFarooqui+6−01 file
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 →