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
17865Commits captured
17284AI analyses
99High-risk findings · 30d
The watch feed

Changes worth understanding

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

17284 analyses
Highest risk·RSS
Informational 19 AI analysisMessage 57 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

ci: hw: fix T1B1 firmware path

This commit fixes a CI hardware-test script that was pointing to the wrong firmware file path for the original Trezor (T1B1). It also cleans up how the test launches the firmware-update command and checks whether it succeeded. There is no …

Command construction uses shell=True with a user-supplied file path in `run(f"headertool {file}", shell=True, check=True)` and `Popen(trezorctlcmd, shell=True)`Return-code checking was added, improving failure detection in the test harnessNo product firmware or cryptographic code is changed
6d6a1aa3by Martin Milata+16−42 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 72 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

ci: hw: don't run core tests if only T1B1 is chosen

This is a minor GitHub Actions CI workflow tweak. It prevents certain hardware test jobs from running when no 'core' device models are selected (for example, when only the older T1B1 model is chosen). It does not change any firmware code, …

211c4dbaby Martin Milata+2−11 file
No security note in commit
Open full analysis →Source commit ↗
Low 26 AI analysisMessage 62 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

refactor(core): close other workflows when starting `ProgressLayout`

This commit moves the responsibility for closing other on-screen workflows into the ProgressLayout class itself, rather than having each individual feature call a separate 'close others' function. It is a code cleanup (refactor) and does n…

workflow.close_others() moved into ProgressLayout.start()no new authorization or validation logic introducedno change to message parsing, cryptography, or memory handling
ada6a447by Roman Zeyde+4−84 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 45 · Thin
LL Lightning LabsLND BitcoinLightning Network

mod: use tagged tlv and tor modules

This commit is a routine dependency housekeeping change. It switches two internal Go modules (tlv and tor) from using local source code replacements to using published tagged versions. There is no code change in this repository and no secu…

0b30a4faby yyforyongyu+6−62 files
No security note in commit
Open full analysis →Source commit ↗
Low 43 AI analysisMessage 76 · Adequate
EL ElectrumElectrum BitcoinSoftware wallets

lnurl: fail lnurl-pay on successAction field

This commit makes Electrum refuse LNURL-pay payments when the payment service includes a 'successAction' response. The change is a temporary safety measure: Electrum does not yet know how to display these follow-up actions to the user, so …

Defensive fail-closed behavior for unimplemented protocol featurePrevents silent omission of LUD-09 successAction responsesCould be interpreted as mitigating social-engineering or payment-confirmation risks where a successAction is used to mislead users
2223cc02by f321x+3−01 file
No security note in commit
Open full analysis →Source commit ↗
Moderate 57 AI analysisMessage 58 · Thin
LL Lightning LabsLND BitcoinLightning Network

witnessbeacon: avoid interceptor deadlock

This patch fixes a deadlock and a stale-data replay problem in LND's 'witness beacon,' the component that notifies external interceptors about HTLCs that might need a preimage. The deadlock occurred because a lock was held while calling in…

Deadlock between preimage beacon mutex and htlcswitch interceptor event loopPotential stale on-chain HTLC replay to reconnecting interceptor after resolver teardownMissing cleanup of on-chain intercept handle on subscription cancellation or interceptor failure
98da7b4aby ziggie+84−183 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 65 · Adequate
LL Lightning LabsLND BitcoinLightning Network

routerrpc: add clarifying docs for the intercepted forward

This commit only adds documentation comments to the router RPC API. It explains that HTLC interception requests may be replayed after reconnect and clarifies what happens when an HTLC moves on-chain. No code behavior was changed.

8909c2fbby ziggie+32−63 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 57 · Thin
LL Lightning LabsLND BitcoinLightning Network

docs: add v0.21.1 release note

This commit only adds a release note describing a bug fix that was already merged in a previous pull request. The actual code change happened elsewhere, so this commit itself does not introduce, fix, or alter any executable software. It is…

9c5f32a2by ziggie+10−01 file
No security note in commit
Open full analysis →Source commit ↗
Moderate 59 AI analysisMessage 90 · Strong
LL Lightning LabsLND BitcoinLightning Network

htlcswitch: track held HTLC source

This commit rewrites how LND tracks HTLCs that are paused by an external interceptor, distinguishing between normal off-chain forwards and ones that have moved to on-chain contract resolution. It fixes a likely bug where a previously off-c…

Prevents settlement of on-chain HTLCs through stale off-chain link mailbox pathPrevents premature auto-fail of on-chain HTLCs at off-chain auto-fail heightPrevents loss of on-chain settlement opportunity when external interceptor disconnects
eb1193f8by ziggie+1067−1927 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 72 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

test(core): don't run FIDO2 tests on BTC-only builds

This commit only changes a test file so that FIDO2/WebAuthn tests are skipped on Bitcoin-only firmware builds. It does not change any production code, wallet logic, or security behavior. There is no vulnerability or security fix here.

f386bdf8by Roman Zeyde+9−31 file
No security note in commit
Open full analysis →Source commit ↗
Moderate 57 AI analysisMessage 78 · Adequate
LL Lightning LabsLND BitcoinLightning Network

itest: cover on-chain interceptor settlement

This commit adds new integration tests for the Lightning Network Daemon (LND). The tests check what happens when a payment is deliberately held by an external interceptor and the underlying channel is force-closed on-chain. The commit mess…

On-chain HTLC settlement failure after force-close and restartHeld HTLC entry eviction due to missing auto-fail height for on-chain packetsDuplicate held-entry path may block on-chain contest resolver settlement
9b31ba83by ziggie+174−02 files
Vendor flagged security relevance
Open full analysis →Source commit ↗
Low 27 AI analysisMessage 73 · Adequate
EL ElectrumElectrum BitcoinSoftware wallets

qt: prevent setting locktime on channel funding tx

This commit removes the ability for users to manually set a transaction locktime when creating a Lightning channel funding transaction in Electrum's Qt desktop GUI. A locktime can delay when a transaction becomes valid or spendable. For ch…

UI hardening: removes a potentially dangerous user-configurable option for a specific transaction typeContext-aware restriction based on TxEditorContext.CHANNEL_FUNDINGCommit message describes change as preventing a 'potential footgun' rather than a vulnerability
535609ddby f321x+3−21 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 →