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
18285Commits captured
17497AI analyses
106High-risk findings · 30d
The watch feed

Changes worth understanding

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

17497 analyses
Highest risk·RSS
Informational 18 AI analysisMessage 73 · Adequate
FD FoundationPassport firmware BitcoinHardware wallets

Add Coconut Wallet single-sig Connect Wallet option

This commit adds support for a new Bitcoin wallet app called Coconut Wallet to the Passport hardware device. It lets users export their single-signature wallet setup to Coconut Wallet via an animated QR code, using the same data format alr…

9d60781dby Jack+31−04 files
No security note in commit
Open full analysis →Source commit ↗
Low 38 AI analysisMessage 73 · Adequate
LDK Lightning Dev Kitrust-lightning BitcoinCryptographic librariesLightning Network

Correct deserialization of `u16::MAX` byte-Features

This commit fixes a mismatch in how Lightning feature flags are read from the wire. Previously, a feature set whose serialized byte length was exactly 65,535 bytes (u16::MAX) could be deserialized incorrectly because the code used a generi…

Deserialization length mismatch between read and write pathsPotential incorrect parsing of maximally-sized length-prefixed feature vectorsReported by external party (Project Loupe)
87c8c326by Matt Corallo+4−11 file
No security note in commit
Open full analysis →Source commit ↗
Low 35 AI analysisMessage 65 · Adequate
LDK Lightning Dev Kitrust-lightning BitcoinCryptographic librariesLightning Network

Refuse to set features at index higher than `u16::MAX` bytes

This commit adds a safety check in the code that handles Lightning network feature flags. Feature flags are small on/off settings used when two nodes connect. The change prevents the code from accepting a feature flag position so high that…

Bounds check added to prevent unbounded vector growthRejects feature bits that cannot be serialized per BOLT length constraintsReported by external party (Project Loupe)
4cd3a8a6by Matt Corallo+3−01 file
Vendor flagged security relevance
Open full analysis →Source commit ↗
High 76 AI analysisMessage 73 · Adequate
LDK Lightning Dev Kitrust-lightning BitcoinCryptographic librariesLightning Network

Don't panic when a composite sub-handler returns `Ok(None)`

This commit fixes a bug where a remote peer could crash a Lightning node by sending a specially chosen custom message. The crash happened because a message-routing helper assumed a sub-component would always recognize any message type matc…

Remote-triggered panic (denial of service) in message-processing threadViolation of `CustomMessageReader` contract assumption in composite handlerPeer-controlled input (`message_type`) used as index/pattern match without graceful fallback
77ac339bby Jeffrey Czyz+71−11 file
Vendor flagged security relevance
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 62 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

ci: updated docs to reflect removal of REPO_USE_WARP_RUNNERS flag

This is a one-line documentation update in the CI README. It simply updates instructions for how to use third-party WarpBuild runners in a fork after a configuration variable was removed. There is no code change and no security relevance.

744d4950by Max Edwards+1−11 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 62 · Adequate
KX KruxKrux BitcoinHardware wallets

refactor: dedupe flipped-orientation check in touch.py via is_flipped_orientation

This commit is a simple code cleanup: it replaces two copies of the same display-orientation check with a single shared helper method. There is no security-relevant change in behavior; the logic before and after is functionally identical.

a0924c7cby kkdao+4−82 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 90 · Strong
KX KruxKrux BitcoinHardware wallets

feat: replace `poetry` to `uv` as venv manager

This commit swaps the project's Python virtual-environment and dependency-lock tooling from Poetry to uv. It deletes the old Poetry lockfile (poetry.lock), updates pyproject.toml to use uv-compatible metadata, and adds a new uv lockfile (u…

a8eca7c8by qlrd+1065−18823 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 72 · Adequate
KX KruxKrux BitcoinHardware wallets

ci: mirror the `uv run poe pre-commit` in CI jobs

This commit only changes how the project's automated build and test pipelines install Python tools. It swaps the Poetry package manager for the `uv` tool in GitHub Actions workflow files. There is no change to the actual Krux application c…

f981da0cby qlrd+44−462 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 57 · Thin
KX KruxKrux BitcoinHardware wallets

chore: update `poetry` to `uv` commands.

This commit is a routine developer tooling change. It replaces the 'poetry' command with the 'uv' command in documentation and a screenshot-generation script, and adds a single trailing comma in one Python file. There is no change to the a…

5752a688by qlrd+36−373 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 57 · Thin
KX KruxKrux BitcoinHardware wallets

docs: update `poetry` to `uv commands

This commit only updates developer documentation, replacing instructions that mentioned the Poetry Python tool with instructions for the uv Python tool. No code, dependencies, or security behavior changed.

55c72c34by qlrd+43−514 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 82 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

test: add fuzz test for private broadcast

This commit only adds a new automated fuzz test for an existing Bitcoin Core feature called private transaction broadcast. It does not change any production code that runs on the network, so it cannot by itself introduce a security vulnera…

2ee4fafaby kevkevinpal+212−53 files
No security note in commit
Open full analysis →Source commit ↗
Low 47 AI analysisMessage 73 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

private broadcast: enforce sending to unique node ids

This change adds a safety check inside Bitcoin Core's private transaction-broadcast feature. It prevents the same node from being chosen more than once to receive different transactions, because doing so could let that node figure out whic…

privacy leak mitigation in transaction broadcastdefensive invariant enforcement with Assume(false)prevents node-id reuse during private broadcast rounds
08b7c61fby Vasil Dimov+8−12 files
Vendor flagged security relevance
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 →