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.

24Projects watched
17776Commits captured
17247AI analyses
98High-risk findings · 30d
The watch feed

Changes worth understanding

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

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

Add try_push to Buffer trait

This commit adds a new `try_push` method to an internal `Buffer` trait used during Base58 encoding. It is a straightforward, additive change that lets encoding code gracefully handle a full fixed-size buffer in no-allocation builds. There …

aafb6065by Mitchell Bagot+15−01 file
No security note in commit
Informational 18 AI analysisMessage 58 · Thin
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Split format_iter into encode_to_buffer

This commit refactors base58 encoding so the same encoding logic can be reused with a fixed-size, no-allocation buffer (ArrayVec) as well as the existing heap buffer (Vec). It removes several `#[cfg(feature = "alloc")]` guards from shared …

Refactoring only; no direct vulnerability fixRemoves alloc feature gates from shared base58 encoding infrastructureIntroduces fallible encoding path suitable for fixed-size buffers
f85780deby Mitchell Bagot+16−91 file
No security note in commit
Informational 15 AI analysisMessage 51 · Thin
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Remove push from Buffer

This commit is a routine internal cleanup in the rust-bitcoin library's base58 module. It removes an unused 'push' method from a private helper trait called Buffer, because the code now uses a fallible 'try_push' method instead. There is n…

c768df58by Mitchell Bagot+0−51 file
No security note in commit
Informational 15 AI analysisMessage 51 · Thin
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Add Base58CkString type

This commit adds a new type, Base58CkString, for encoding Bitcoin-style base58check strings. It is a routine feature addition that makes encoding work both with and without memory allocation. There is no indication of a security bug or fix.

5adcab52by Mitchell Bagot+141−32 files
No security note in commit
Low 43 AI analysisMessage 83 · Strong
EP Elements ProjectCore Lightning BitcoinLightning Network

lightningd: accept OP_RETURN closer_scriptpubkey in simple-close check

This commit fixes a bug in Core Lightning's experimental simple-close feature. When two Lightning nodes tried to close a channel cooperatively using the new 'simple close' protocol, one peer was allowed by the specification to burn its own…

Denial of service / unwanted force-close: a spec-compliant peer could cause the local node to force-close a channel, incurring on-chain fees and delays.Funds not stolen: the OP_RETURN output is unspendable, so accepting it cannot redirect funds to an attacker.Value-zero check prevents burning real funds: the patch enforces AMOUNT_SAT(0) on the OP_RETURN output.
9b6a80fcby Níckolas Goline+356−52 files
No security note in commit
Informational 0 AI analysisMessage 57 · Thin
KX KruxKrux BitcoinHardware wallets

chore: update cUR and k_quirk

The commit title says it is a routine maintenance update ('chore') for two internal items named cUR and k_quirk in the MaixPy firmware file. No diff content is available, and no verified references were supplied, so there is no visible evi…

f4796afeby odudex+1−11 file
No security note in commit
Low 25 AI analysisMessage 57 · Thin
KX KruxKrux BitcoinHardware wallets

fix: pin gcc base image by digest

This change locks the Docker build to one specific, unchangeable version of the GCC compiler image by adding a cryptographic fingerprint (SHA digest). Without this, an attacker who compromises the GCC image registry could silently replace …

Docker base image changed from mutable tag to digest-pinned referenceSupply-chain / build-integrity hardeningPrevents registry tag-replacement attacks for the gcc:12-bookworm image
ceefbb19by odudex+1−11 file
No security note in commit
Informational 15 AI analysisMessage 68 · Adequate
BS BlockstreamBlockstream Jade BitcoinHardware wallets

repo: remove stray cUR submodule gitlink

This commit removes a leftover Git submodule reference (a 'gitlink') that had no matching configuration entry. It fixes a Git checkout error but does not change any compiled code, cryptographic logic, or device behavior. There is no securi…

88d69aa6by odudex+0−11 file
No security note in commit
Informational 15 AI analysisMessage 50 · Thin
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

kernel: expose witness stack for btck_TransactionInput

This commit adds a new public read-only API to the Bitcoin Core 'kernel' library so that outside programs can inspect the 'witness stack' of a transaction input. The witness stack is part of how modern Bitcoin transactions (SegWit/Taproot)…

No security-relevant signals present in the diff or commit message.Change is purely an API surface expansion for read-only access to existing data.No memory-unsafe patterns introduced: uses existing opaque-handle wrappers, copy/destroy symmetry, and asserts on index bounds.
e6de3a2dby Peter Zafonte+164−14 files
No security note in commit
Informational 15 AI analysisMessage 50 · Thin
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

kernel: expose scriptSig for btck_TransactionInput

This commit adds a new public function to the Bitcoin Core 'bitcoinkernel' library that lets callers read the scriptSig data from a transaction input. A scriptSig is the part of a Bitcoin transaction input that typically contains a signatu…

6667dc4eby Peter Zafonte+29−04 files
No security note in 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