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
17782Commits captured
17251AI analyses
98High-risk findings · 30d
The watch feed

Changes worth understanding

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

17251 analyses
Highest risk·RSS
Informational 15 AI analysisMessage 62 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

build(core): add missing string argument to _Static_assert

This is a one-line build fix for a software-only emulator path. The C _Static_assert macro requires a message string as its second argument on some compilers/toolchains. The change adds an empty string so the code compiles. It does not alt…

757a0238by matejcik+1−11 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 72 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

chore(core): ignore some ancillary directories

This commit simply adds two directory names to the project's .gitignore file so that files created by a Visual Studio Code extension are not accidentally committed to the repository. It does not change any executable code, cryptographic lo…

bc5f0914by matejcik+2−01 file
No security note in commit
Open full analysis →Source commit ↗
Moderate 59 AI analysisMessage 100 · Strong
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

feat(se): Move 2 W1 — SE generation detection, gen-isolated backend, gen-1 page-8 gate

This is a large firmware commit for the Keystone 3 hardware wallet that restructures how the secure element (SE) chip is used. It introduces a generation-aware backend so the firmware can support two different SE configurations (gen-1, the…

Generation-aware SE backend with fail-closed NULL backend for UNPROVISIONED/INVALID chipsLegacy page-8 PIN-hash wipe gated to gen-1 only to avoid erasing gen-2 R_wrappedPer-account lifecycle status pages for atomic crash recovery of create/change-PIN/delete
57a92dcdby aaron+2163−16736 files
Vendor flagged security relevance
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 83 · Strong
EP Elements ProjectCore Lightning BitcoinLightning Network

connectd/tests: fix test_announce_and_connect_via_dns on macOS

This commit is a test-only fix for macOS. It skips a test that fails because macOS lacks a specific local hostname entry, and it adds a code comment explaining a networking flag. There is no security issue or vulnerability here.

40f2ce6aby Níckolas Goline+6−02 files
No security note in commit
Open full analysis →Source commit ↗
Low 26 AI analysisMessage 83 · Strong
LDK Lightning Dev Kitrust-lightning BitcoinCryptographic librariesLightning Network

fuzz: sync reloaded monitors from their own best block

This commit fixes a bug in LDK's internal fuzz testing harness (not production code). When the test reloaded saved channel data, it incorrectly synchronized all channel monitors from the oldest monitor's block height. Monitors that were al…

Reorg-induced loss of force-close claim transactions in fuzz harnessIncorrect per-monitor startup synchronization in test codeDuplicate block replay treated as chain reorganization
3d9a10d2by Joost Jager+77−461 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 78 · Adequate
LDK Lightning Dev Kitrust-lightning BitcoinCryptographic librariesLightning Network

fuzz: factor chanmon broadcast relay helper

This is a minor code cleanup inside a fuzzing test harness. It extracts a small loop that collects broadcast transactions from all simulated nodes into a new helper function, then calls that helper from an existing cleanup loop. The actual…

48b2db75by Joost Jager+9−51 file
No security note in commit
Open full analysis →Source commit ↗
Informational 14 AI analysisMessage 78 · Adequate
LDK Lightning Dev Kitrust-lightning BitcoinCryptographic librariesLightning Network

fuzz: settle chanmon force-closes on chain

This commit changes only a fuzzing test harness (chanmon_consistency.rs). It improves how simulated force-closed channels are settled on the fake blockchain during fuzz tests, so the test can catch stuck cleanup states. There is no change …

No production code modifiedFuzz harness onlyNo mention of CVE, security bug, or vulnerability
05abdc5aby Joost Jager+75−121 file
No security note in commit
Open full analysis →Source commit ↗
Low 25 AI analysisMessage 60 · Adequate
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

fix regression from jdk25 update causing silent skips when importing jsonl wallet label lines

This commit fixes a bug where importing wallet labels from a JSONL file could silently skip some lines after a Java runtime update. The fix adds a required empty constructor for a label class and corrects how key derivation data is copied …

Silent data loss / import skip on deserialization failureMutable object reference reuse in key derivation copyingRegression tied to JDK/Gson runtime compatibility
f697aa61by Craig Raw+7−11 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 68 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

doc: add an AI contribution policy

This commit is purely administrative: it adds a written policy telling contributors how they may use AI tools (like ChatGPT) when filing bug reports, feature requests, and pull requests. It does not change any Bitcoin software code, networ…

31abaa26by will+57−46 files
No security note in commit
Open full analysis →Source commit ↗
Moderate 64 AI analysisMessage 62 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

feat(ethereum): allow approve and transfer to send eth

This commit changes how Trezor devices display Ethereum transactions when someone sends ERC-20 token approval or transfer calls that also include native ETH. Previously, the device might not clearly show the attached ETH, so a user could u…

UI display of previously hidden native ETH value in ERC-20 approve/transferNew test fixtures explicitly for 'with_eth' combinationsCommentary in code states 'so it can't be signed unseen'
e785f6c6by PrisionMike+558−678 files
No security note in commit
Open full analysis →Source commit ↗
Informational 19 AI analysisMessage 58 · Thin
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

wallet: Add CWallet::ExportWatchOnly

This commit adds a new Bitcoin Core feature that lets a user export a copy of their wallet containing only public information (watch-only). It creates a separate wallet file with descriptors, address book, transactions, and locked coins, b…

Feature addition for watch-only wallet exportPrivate keys explicitly excluded via WALLET_FLAG_DISABLE_PRIVATE_KEYS and export_private=falseExported descriptors validated to contain no private keys (CHECK_NONFATAL dummy_keys.keys.size() == 0)
444878efby Ava Chow+188−13 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 45 · Thin
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

wallet, rpc: Add exportwatchonlywallet RPC

This commit adds a new wallet command called exportwatchonlywallet. It lets a user save a copy of their wallet that contains only public information—public descriptors, transactions, and address book data—without private keys. The change i…

d053e3e5by Ava Chow+45−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 →