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

Changes worth understanding

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

16841 analyses
Highest risk·RSS
Low 30 AI analysisMessage 80 · Strong
LL Lightning LabsLND BitcoinLightning Network

docs: add payment migration release note

This commit only adds a release note describing a previously fixed bug in LND's payment migration. The actual code change happened in an earlier pull request. The bug involved old payment routes that stored a 'blinded total amount' without…

Release note references a 'payment migration failure' caused by malformed historical route dataInvalid field combination (blinded total without encrypted recipient data) is now rejected by SendToRouteV2Potential availability/reliability impact during node upgrade/migration
17ee638eby ziggie+7−01 file
No security note in commit
Open full analysis →Source commit ↗
Moderate 59 AI analysisMessage 68 · Adequate
LL Lightning LabsLND BitcoinLightning Network

routerrpc: require encrypted blinded hop data

This commit tightens validation in LND's router RPC so that callers cannot supply a 'blinded total amount' for a payment hop unless they also provide the encrypted recipient data that marks the hop as blinded. It also restricts that total …

Input validation gap in caller-provided route deserializationBlinded payment fields partially validated (blinding point required encrypted data, but total amount did not)State/database consistency risk: partial blinded hop data could be persisted
ffc62509by ziggie+122−02 files
Vendor flagged security relevance
Open full analysis →Source commit ↗
Informational 19 AI analysisMessage 77 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

Fix: SIGINT was ignored by the cln docker container

This commit fixes a Docker startup script so that when a user or system sends a shutdown signal (SIGINT/SIGTERM) to the container, Core Lightning actually receives it and shuts down cleanly. Previously the signal was ignored, which could f…

Signal handling / graceful shutdown fixDocker PID 1 signal propagation issuePotential unclean shutdown leading to state corruption
02e06fc6by Nicolas Dorier+6−11 file
No security note in commit
Open full analysis →Source commit ↗
Informational 21 AI analysisMessage 90 · Strong
LDK Lightning Dev Kitrust-lightning BitcoinCryptographic librariesLightning Network

Increase probabilistic scorer defaults 5x

This commit changes default numerical tuning knobs in the Lightning Dev Kit's payment router. It makes the router prefer shorter, more reliable payment paths by increasing several penalty values fivefold. The change is presented as a perfo…

No security framing in commit message or diffNo vulnerability pattern (overflow, injection, auth bypass, etc.) presentChange is a tunable default value adjustment with documented rationale
687b851bby benthecarman+30−271 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 0 · Opaque
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

fix typo

This commit fixes a spelling mistake in a code comment, changing 'succesful' to 'successful'. It does not change any actual program behavior or fix any security issue.

abc0a4f2by Craig Raw+1−11 file
No security note in commit
Open full analysis →Source commit ↗
Informational 21 AI analysisMessage 78 · Adequate
LD LedgerLedger Bitcoin app BitcoinHardware wallets

Display total amount of external inputs when reliable

This commit changes what information the Ledger Bitcoin app shows on its screen when signing a transaction that includes 'external inputs'—coins the user did not provide and whose amounts the device cannot independently verify. Previously …

UI/UX hardening: additional contextual data shown for transactions with unverified external inputsNo change to cryptographic checks, sighash validation, or input verificationExternal inputs warning is preserved; new data is displayed only when the input set is closed (no ANYONECANPAY)
26f631c5by Salvatore Ingala+126−174 files
No security note in commit
Open full analysis →Source commit ↗
Informational 21 AI analysisMessage 28 · Opaque
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

fix ide agent support

This commit changes the build configuration for running Sparrow from an IDE (integrated development environment). It adds a JVM argument that exposes an internal Java module called 'jdk.unsupported', which contains non-standard classes lik…

Exposes internal Java module jdk.unsupportedAdds sun.misc namespace availability to development runtimeBuild-only change with no application code modification
6b30e6a3by Craig Raw+5−01 file
No security note in commit
Open full analysis →Source commit ↗
High 70 AI analysisMessage 35 · Opaque
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

tighten schema validation

This commit adds stronger safety checks when Sparrow Wallet opens its encrypted wallet database files. It tries to detect and block tampered wallet files that contain unusual database objects such as linked tables, triggers, aliases, synon…

Adds pre-migration validation of H2 MVStore metadata payload for dangerous DDL patternsBlocks CREATE FORCE LINKED TABLE / TRIGGER / ALIAS in wallet file metadataRejects linked tables, synonyms, generated columns, custom domains, and unexpected column defaults
a5f705f1by Craig Raw+146−41 file
No security note in commit
Open full analysis →Source commit ↗
Informational 16 AI analysisMessage 75 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

qt, test: Enable tests on macOS with `minimal` QPA plugin

This commit removes workarounds that skipped three Bitcoin Core Qt test suites on macOS when using the 'minimal' Qt platform plugin. The previous commit fixed the underlying crash cause, so these tests can now run. It is a test-infrastruct…

No security-relevant code change in the diff itselfReferences a prior crash fix, but this commit only removes test skipsNo input handling, cryptography, networking, consensus, or wallet logic modified
fd59d68cby Hennadii Stepanov+0−343 files
No security note in commit
Open full analysis →Source commit ↗
Low 26 AI analysisMessage 78 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

qt: Avoid implicit `NSApplication` instantiation

This commit fixes a macOS-specific behavior in Bitcoin Core's Qt interface. Previously, two pieces of code called [NSApplication sharedApplication], which has the side effect of creating the macOS application object if it didn't already ex…

Implicit object instantiation side effect removedDefensive nil check added before Objective-C message sendmacOS-only Qt platform code changed
c8b2aeb2by Hennadii Stepanov+4−21 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 50 · Thin
LD LedgerLedger Bitcoin app BitcoinHardware wallets

Update txmaker to allow creating transactions with external inputs

This commit only changes a test helper script (txmaker.py) used to build fake Bitcoin transactions for automated tests. It adds the ability to mark some inputs as 'external' (not owned by the wallet being tested) so the test suite can exer…

7da434b6by Salvatore Ingala+35−31 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 50 · Thin
LD LedgerLedger Bitcoin app BitcoinHardware wallets

Add to playground presets for sighash flags, and for external inputs

This commit only adds new developer-testing presets and a declarative helper for the project's internal 'playground' dev tool. It does not change the Ledger Bitcoin app firmware, wallet logic, or any code that end users rely on. There is n…

8bf62f9aby Salvatore Ingala+280−404 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 →