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 →
23Projects watched
16872Commits captured
16820AI analyses
83High-risk findings · 30d
The watch feed

Changes worth understanding

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

16820 analyses
Highest risk·RSS
Informational 19 AI analysisMessage 50 · Thin
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

gui: Adds option to not load the wallet after migration

This commit adds a user-facing checkbox in the Bitcoin Core desktop wallet that lets someone choose whether to automatically load a wallet after migrating it from an older format. Previously the wallet was always loaded. The change is a us…

No security-relevant signal: change is a feature/usability additionNo memory safety, cryptographic, consensus, or network changesNo privilege boundary crossed
492a715dby Pol Espinasa+20−104 files
No security note in commit
Open full analysis →Source commit ↗
Moderate 60 AI analysisMessage 78 · Adequate
AQ ACINQEclair BitcoinLightning Network

Prevent `channel_id` collisions (#3337)

This commit hardens the Eclair Lightning node against two related problems when opening payment channels: it prevents the same channel ID from being reused by two different channels at the same time, and it aborts channel creation if the v…

State overwrite / collision prevention for channel identifiersAbort-on-first-DB-write-failure to avoid inconsistent persistenceGlobal concurrent map guarding temporary and final channel_id usage
45ea9fbfby Bastien Teinturier+468−19419 files
Vendor flagged security relevance
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 81 · Strong
BC Bitcoin Corelibsecp256k1 BitcoinCryptographic libraries

changelog: add missing entries for #1777 and #1860

This commit only updates the project's changelog file. It adds release-note entries for two previously merged changes and tweaks an existing entry for consistency. No program code was modified, so it cannot introduce or fix a security vuln…

f52eb393by Sebastian Falbesoner+6−11 file
No security note in commit
Open full analysis →Source commit ↗
Low 29 AI analysisMessage 77 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

feat(common,core,python,tests): migrate Soroban authorization to SOROBAN_CREDENTIALS_ADDRESS_V2.

This commit updates Trezor's Stellar/Soroban smart-contract support to match a newer Stellar protocol version (Protocol 27). It renames the credential type from the older SOROBAN_CREDENTIALS_ADDRESS to SOROBAN_CREDENTIALS_ADDRESS_V2 and up…

Protocol version bump for Stellar Soroban authorization (v27)Legacy SOROBAN_CREDENTIALS_ADDRESS (value 1) marked reserved and unsupportedField rename address -> address_v2 across protobuf, core, python, rust
0d2cc2acby Jun Luo+111−7213 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 98 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

feat(core): compose Stellar authorization entry labels as root label + path.

This commit only changes the on-screen text labels shown when a Trezor device asks the user to confirm a Stellar blockchain authorization. It renames labels from formats like 'Authorization 2' and '1-2-1' to 'Authorization #2' and '#2.1.1'…

ad830fa9by Jun Luo+6−51 file
No security note in commit
Open full analysis →Source commit ↗
Low 36 AI analysisMessage 100 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

feat(common,core,python,tests): support signing Stellar Soroban authorization entries.

This commit adds a new Trezor feature that lets users sign Stellar Soroban smart-contract authorization entries. The device now supports a new message type where it derives the user's Stellar address, shows confirmation screens, and produc…

New signing surface added for Stellar Soroban authorization entriesUser confirmation flow implemented before signingAuthorization payload binds signature to network, nonce, expiration ledger, address, and invocation tree
6008cc25by Jun Luo+1641−30325 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 90 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

refactor(core/stellar): move generic Soroban writers to writers.py.

This commit is a straightforward code cleanup: it moves several Stellar Soroban serialization helper functions from an operation-specific file into a shared writers module so both transaction signing and standalone authorization signing ca…

5f24e157by Jun Luo+221−2185 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 90 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

refactor(core/stellar): move generic Soroban layout helpers to layout.py.

This commit is a straightforward code cleanup: it moves helper functions for formatting Stellar Soroban smart-contract values and showing confirmation screens from one file to another shared file. No security behavior changes are visible i…

No security-relevant behavior changeRefactor only: code moved between modulesMinor hardening: narrowed exception handler for timestamp formatting
9ce451bdby Jun Luo+252−2504 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 77 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

test(stellar): add Soroban authorization signing tests.

This commit only adds new automated tests for signing Stellar Soroban authorizations. It does not change any production firmware, wallet logic, or cryptographic code. There is no security vulnerability here.

72511927by Jun Luo+538−04 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 57 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

chore(core/stellar): make gen and fixtures

This commit is a routine maintenance update for the Stellar feature in Trezor firmware. It adds three new user-facing text strings (for device screen prompts), updates translation signatures, refreshes expected test screenshot hashes, and …

No security-relevant code paths changedNo bug fixes or vulnerability mitigations present in diffDependency pinning change is a date normalization, not a downgrade or known-vulnerable version selection
94d39e3cby obrusvit+169−606 files
No security note in commit
Open full analysis →Source commit ↗
Moderate 52 AI analysisMessage 93 · Strong
AQ ACINQEclair BitcoinLightning Network

Apply RBF limits to remote closing transactions (#3331)

This commit adds rate limits and maximum attempt caps for Replace-By-Fee (RBF) closing transactions in the Eclair Lightning node. Previously, a peer could repeatedly propose new closing transactions without strict limits, which could waste…

Resource exhaustion via unbounded RBF attempts is now cappedRemote peer closing transaction rate-limiting addedLocal closing transaction count bounded by BOLT recommendation
687485fcby Bastien Teinturier+94−103 files
Vendor flagged security relevance
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 83 · Strong
EL ElectrumElectrum BitcoinSoftware wallets

test_lnwallet: add unittest for single channel mpp split config

This commit adds a new automated test to the Electrum project. It does not change any production wallet or Lightning code. The test verifies that when Electrum splits a multi-part payment across a single channel, all payment parts actually…

14f7fa0bby f321x+22−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 →