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

Changes worth understanding

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

17344 analyses
Highest risk·RSS
Informational 15 AI analysisMessage 60 · Adequate
EL ElectrumElectrum BitcoinSoftware wallets

test_storage_upgrade: add test wallet with invoice and request

This commit only adds a new test case and a test wallet file to Electrum's test suite. It does not change any production code, so it cannot introduce a security vulnerability or fix one. The test wallet contains a publicly exposed seed phr…

4774f7adby ThomasV+147−02 files
No security note in commit
Low 32 AI analysisMessage 45 · Thin
CK CoinkiteCOLDCARD firmware BitcoinHardware wallets

Fix QR scanner setup and sleep handling

This commit fixes several bugs in how the COLDCARD Q1 hardware wallet talks to its built-in QR-code scanner. The changes make scanner startup more reliable, prevent stale 'go to sleep' commands from accidentally stopping a scan that just s…

Hardware peripheral reset line held in asserted state (potential wake/power issue)Async sleep command could race with newly started scan (state-management bug)CancelledError from asyncio.wait_for_ms could strand setup task
ad2088d2by scgbckbone+163−693 files
No security note in commit
Low 26 AI analysisMessage 45 · Thin
CK CoinkiteCOLDCARD firmware BitcoinHardware wallets

Keep scanner reinit state instance-local

This tiny code change moves a 'needs reinit' flag from being shared across all QR scanner objects to being kept inside each individual scanner object. In the real device code the flag is removed from the base class; in the simulator it is …

Shared mutable class-level state removedState variable made instance-localPotential race-condition / state-confusion class eliminated
55340577by scgbckbone+1−22 files
No security note in commit
Informational 15 AI analysisMessage 58 · Thin
LDK Lightning Dev Kitrust-lightning BitcoinCryptographic librariesLightning Network

Drop the BufReader wrapper

This commit removes a small, custom one-byte buffering helper that was only needed to make older versions of a dependency (rust-bitcoin) happy. After the dependency changed its requirements, the wrapper became unnecessary. There is no secu…

b582ce15by Abeeujah+1−671 file
No security note in commit
Informational 15 AI analysisMessage 68 · Adequate
LDK Lightning Dev Kitrust-lightning BitcoinCryptographic librariesLightning Network

Deserialize consensus objects using Read type

This is a small cleanup change that removes an unnecessary BufReader wrapper when deserializing Bitcoin consensus objects. The underlying rust-bitcoin library now accepts a simpler 'Read' trait directly, so the code was updated to match. T…

deee085cby Abeeujah+1−21 file
No security note in commit
Moderate 61 AI analysisMessage 50 · Thin
CK CoinkiteCOLDCARD firmware BitcoinHardware wallets

fix bypass_tmp return to master secret with xprv type

This commit fixes a bug in how the COLDCARD wallet creates encrypted backups when a temporary seed is being bypassed. Previously, if the main secret was stored as an extended private key ('xprv') rather than as BIP39 seed words, the backup…

Incorrect secret encoding when bypassing temporary seedPotential master secret exposure or backup corruption due to type mismatchMissing branch for xprv-type master secret in backup path
67a5c6c2by scgbckbone+7−21 file
No security note in commit
Informational 15 AI analysisMessage 0 · Opaque
CK CoinkiteCOLDCARD firmware BitcoinHardware wallets

fix tests

This commit only updates two test files to fix failing tests. It changes test input data and adds an address-format parameter that a helper function now requires. There is no change to the actual COLDCARD firmware or wallet code that users…

eb112eb3by scgbckbone+9−22 files
No security note in commit
Informational 15 AI analysisMessage 76 · Adequate
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

hashes: fix tag name in sha256t_tag macro docs

This is a one-word documentation fix in a Rust macro. The generated documentation for a cryptographic tag structure was accidentally referring to a non-existent variable name, so it displayed broken placeholder text like '[`$hash_name`]' i…

bb887edbby jrakibi+1−11 file
No security note in commit
Informational 12 AI analysisMessage 83 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Add tests to verify 0 return for overflow

This commit only adds new unit tests to verify that a previously changed function, Target::from_compact, returns zero when a Bitcoin 'compact' difficulty value overflows a 256-bit target. It does not change any production code. The tests c…

4ee43312by Mitchell Bagot+17−01 file
No security note in commit
Informational 15 AI analysisMessage 77 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

chore(translations): updates to English strings [no changelog]

This commit is a routine update to the English user-interface text strings in the Trezor firmware. It changes wording such as 'Continue with the next share' to 'Enter next share' and adjusts the line breaks in a few messages. There is no c…

aceafef6by Michal Kazda+7934−79343 files
No security note in commit
Informational 15 AI analysisMessage 47 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

chore(l10n): updated fixtures

This commit only updates expected test-result fingerprints (hashes) in a JSON file used by the project's automated user-interface tests. No actual product code, firmware logic, or user-facing behavior was changed. It is a routine test-main…

c833b836by Michal Kazda+36−361 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