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.

23Projects watched
16920Commits captured
16841AI analyses
83High-risk findings · 30d
The watch feed

Changes worth understanding

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

16841 analyses
Highest risk·RSS
Informational 15 AI analysisMessage 50 · Thin
BC Bitcoin Corelibsecp256k1 BitcoinCryptographic libraries

silentpayments: drop "shuffle outputs" recommendation from API docs

This commit only changes documentation comments in a header file. It removes a recommendation that callers shuffle transaction outputs before scanning, and instead clarifies that outputs should be passed in their original transaction order…

cea6d114by Sebastian Falbesoner+2−31 file
No security note in commit
Informational 15 AI analysisMessage 60 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

guix: split macOS and win builds

This commit reorganizes how Bitcoin Core's official macOS and Windows release binaries are built using the Guix reproducible-build system. It splits one big build script into smaller, platform-specific scripts for non-GUI and GUI parts. Th…

0b0785daby fanquake+322−1487 files
No security note in commit
Informational 15 AI analysisMessage 50 · Thin
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

guix: split builds into Linux(gui) and macOS/Windows

This commit reorganizes how Bitcoin Core's official release builds are produced using the Guix build system. It splits Linux builds into two separate steps—one for command-line/daemon programs and one for the graphical wallet interface—and…

008a3e29by fanquake+330−1299 files
No security note in commit
Informational 15 AI analysisMessage 58 · Thin
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Rename witness_version errors

This commit is a simple renaming of error types in the rust-bitcoin library. It changes names like FromStrError to ParseWitnessVersionError and TryFromError to InvalidWitnessVersionError to match existing naming conventions. There is no ch…

bfe55b7bby Mitchell Bagot+28−283 files
No security note in commit
Moderate 59 AI analysisMessage 55 · Thin
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

update external tor socks proxy control port authentication

This commit hardens how Sparrow Wallet talks to an external Tor proxy's control port. Previously, when asking Tor for a new identity, the app used an older authentication method that could send the contents of a secret cookie file over the…

Switches Tor ControlPort authentication from legacy COOKIE to SAFECOOKIE HMAC challenge-responseAdds loopback-only restriction for external Tor ControlPort connectionsValidates cookie file length and uses constant-time hash comparison
b3d51bceby Craig Raw+83−81 file
Vendor flagged security relevance
Informational 20 AI analysisMessage 45 · Thin
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

fix the cn and ru words wrap and too long issue

This commit fixes a UI text display problem where Chinese and Russian labels in the on-screen keyboard hint box could wrap awkwardly or become too long. It introduces a helper that only enables text wrapping/scrolling when the label is wid…

No memory safety issues observedNo input validation changesNo cryptographic or authentication code touched
2dfd881dby aaron+15−21 file
No security note in commit
Informational 15 AI analysisMessage 38 · Opaque
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

add 3.0.0 changelog

This commit only adds a changelog entry and bumps the firmware version number from 2.5.0 to 3.0.0. It contains no actual code changes, bug fixes, or security patches. The changelog mentions vague 'security policy' and 'forgot passcode' imp…

15bf55fdby bianminyan+58−23 files
No security note in commit
Low 32 AI analysisMessage 68 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

validation: handle null mempool on delete

This commit fixes a crash bug in Bitcoin Core's chainstate manager. When deleting a temporary chainstate used for AssumeUTXO loading, the code assumed every chainstate had a memory pool (mempool) attached. In the 'kernel' library mode, a C…

Null-pointer dereference in validation code pathCrash/assertion failure during chainstate deletionAssumeUTXO / kernel-specific code path affected
a99b27f1by Lőrinc+10−12 files
No security note in commit
Moderate 57 AI analysisMessage 68 · Adequate
BB BitBoxBitBox02 firmware BitcoinHardware wallets

rust: use static no-op waker

This commit replaces a custom-built notification helper (a 'waker') inside the BitBox02 firmware's Rust code with a built-in, memory-safe no-op version. The old helper used heap memory and reference counting (Arc), which could be freed by …

Eliminates heap-allocated Arc in waker constructionRemoves custom RawWakerVTable with unsafe clone/wake/drop operationsPrevents ISR callbacks from freeing Arc while heap allocator is active
5be42f61by benma's agent+2−523 files
Vendor flagged security relevance
Low 42 AI analysisMessage 78 · Adequate
BC Bitcoin Corelibsecp256k1 BitcoinCryptographic libraries

silentpayments: flush labels before direct match

This commit fixes a bug in Bitcoin's silent payments scanning code. When a wallet scans a transaction for outputs it can spend, a performance shortcut could accidentally skip over a labeled output and report a plain (unlabeled) version ins…

Incorrect output attribution in wallet scanningLoss of label metadata for received fundsRegression test demonstrates labeled output precedence failure
1ae90bdeby Lőrinc+74−02 files
No security note in commit
Informational 14 AI analysisMessage 68 · Adequate
BC Bitcoin Corelibsecp256k1 BitcoinCryptographic libraries

silentpayments: extract label batch checker

This commit is a simple code cleanup: it moves an existing block of label-scanning logic into a separate helper function without changing what the code actually does. There is no security fix or behavior change visible in the diff.

84a02fa9by Lőrinc+41−341 file
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