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
16904Commits captured
16837AI analyses
83High-risk findings · 30d
The watch feed

Changes worth understanding

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

16837 analyses
Highest risk·RSS
Low 30 AI analysisMessage 76 · Adequate
AQ ACINQEclair BitcoinLightning Network

Accept Bolt12 invoices with reply path (#3325)

This commit loosens Eclair's validation of BOLT12 invoice onion messages so that invoices may now include a reply path. Previously, Eclair rejected invoices that carried a reply path, which caused compatibility problems with LDK nodes. The…

Loosened TLV validation for BOLT12 Invoice messages now permits ReplyPath presenceAdded explicit rejection of unknown records (even odd ones) in final payloadAdded explicit requirement for ReplyPath when an InvoiceRequest is present
79519244by Bastien Teinturier+14−62 files
No security note in commit
Open full analysis →Source commit ↗
Informational 12 AI analysisMessage 50 · Thin
EL ElectrumElectrum BitcoinSoftware wallets

test_lnpeer: add unittest for mpp fee budget check

This commit only adds a new automated test to Electrum's Lightning code. It checks that when a payment is split into multiple parts (MPP), the fee budget is correctly shared across all parts so total fees cannot exceed the budget. There is…

Tests fee-budget enforcement for multipart Lightning paymentsNo production-code changes; purely test coverage
42cb99d0by f321x+36−01 file
No security note in commit
Open full analysis →Source commit ↗
Moderate 63 AI analysisMessage 78 · Adequate
EL ElectrumElectrum BitcoinSoftware wallets

LNWallet: fix fee budget check regression

This commit fixes a bug in Electrum's Lightning Network payment routing. When splitting a payment into multiple parts, the app was checking each partial route's fees against the entire payment's fee budget instead of that part's fair share…

Fee-budget logic regression in payment routingMulti-part Lightning payment fee overpayment possibleIncorrect comparison of full amount/budget against partial route
fc407c39by f321x+2−21 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 62 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

chore(core/eckhart): enable `instructions__view_all_data` string

This commit simply fills in a missing on-screen instruction text for the Eckhart hardware model. It changes an empty translation string to read 'View all data in the menu.' There is no security-relevant code change.

3d9e7c42by Roman Zeyde+1115−11153 files
No security note in commit
Open full analysis →Source commit ↗
Informational 18 AI analysisMessage 77 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

fix(core/eckhart): viewing all data can be done via menu

This commit changes how users access the 'view all data' option on the Eckhart hardware wallet screen. Previously there was a dedicated left button in the bottom action bar; now that button is removed and users are told via an on-screen hi…

UI flow simplification: removes a non-standard Cancelled->Info state transitionNo privilege, authentication, or cryptographic logic changedNo buffer/memory handling changed
4f57cbc0by Roman Zeyde+17−152 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 57 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

chore(core): update UI fixtures

This commit only updates expected screenshot fingerprints (called 'fixtures') used by Trezor's automated UI tests. No actual firmware code, transaction logic, or security behavior was changed. The hash updates are routine test artifacts th…

577ccce6by Roman Zeyde+294−2941 file
No security note in commit
Open full analysis →Source commit ↗
Informational 17 AI analysisMessage 57 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

feat(clear_signing): externalise provider names

This commit adds a new optional 'provider_name' field to the data structure used for Ethereum 'clear signing' on Trezor devices. When a provider name is supplied, the device will show that name instead of the usual recipient address lookup…

New untrusted string field (provider_name) rendered in transaction UIProvider name replaces address-book lookup, potentially hiding true recipientNo visible input validation, length limits, or allowlist in the diff
0a882a4aby PrisionMike+90−236 files
No security note in commit
Open full analysis →Source commit ↗
Informational 19 AI analysisMessage 57 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

feat(clear_signing): update defs with providers

This commit updates the Trezor Ethereum 'clear signing' feature so that when a known DeFi contract (like 1inch or Uniswap) is recognized, the device screen shows the provider's human-readable name (e.g., '1inch Aggregation Router V6') inst…

UI label change only: no transaction validation logic alteredNo new external inputs parsed; provider_name is hardcoded in definitionsNo memory-unsafe operations or buffer size changes
8698d011by PrisionMike+42−104 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 93 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

build(deps): bump github/codeql-action/upload-sarif

This is a routine automated update by Dependabot that bumps the version of a GitHub-owned action used to upload security scan results. It changes one pinned commit hash in a CI workflow file and does not alter any project code, cryptograph…

69e50bb3by dependabot[bot]+1−11 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 93 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

build(deps): bump taiki-e/install-action from 2.79.3 to 2.79.12

This is a routine automated update by Dependabot that bumps a GitHub Actions helper (taiki-e/install-action) used in testing workflows from version 2.79.3 to 2.79.12. It only changes which version of the action is used to install Rust test…

d953dcccby dependabot[bot]+2−22 files
No security note in commit
Open full analysis →Source commit ↗
Moderate 59 AI analysisMessage 82 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

fix(crypto): add missing checks for negative VLA size

This commit fixes two functions in Trezor's base58 code that build temporary memory buffers using a user-supplied length. Before the fix, a negative length value was not rejected. On systems where negative signed integers are treated as ve…

Missing negative-length validation before variable-length array allocationPotential stack-based buffer overflow or allocation failure from signed/unsigned conversionExternal security reporter credited (Amr)
3f193183by M1nd3r+2−21 file
Vendor flagged security relevance
Open full analysis →Source commit ↗
Informational 18 AI analysisMessage 77 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

chore(ci): applying zizmor findings to UI flows workflow [no changelog]

This commit tightens two GitHub Actions workflow files that run translation-related UI tests. It moves broad workflow-level AWS login permission down to only the specific jobs that need it, stops Git from keeping reusable login credentials…

Workflow permission scope reduction (id-token: write moved to job level)actions/checkout persist-credentials: false addedUser-controlled workflow input (inputs.languages) moved to environment variable before shell interpolation
2752c296by Michal Kazda+19−92 files
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 →