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
17611Commits captured
17169AI analyses
89High-risk findings · 30d
The watch feed

Changes worth understanding

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

17169 analyses
Highest risk·RSS
Low 36 AI analysisMessage 73 · Adequate
LL Lightning LabsLND BitcoinLightning Network

bolt12: validate Invoice messages

This commit adds validation checks for BOLT 12 invoices in the LND Lightning node software. It ensures invoices contain required fields (creation time, amount, payment hash, node ID, payment paths), match their originating invoice requests…

New validation gate added to Invoice.Encode() to reject malformed invoices before serializationReader rejects unknown even invoice TLV types and unknown even feature bitsReader enforces chain compatibility against activeChain
e0f04f17by bitromortac+1642−74 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 72 · Adequate
LL Lightning LabsLND BitcoinLightning Network

docs: add BOLT 12 invoice release notes

This commit only adds documentation to the release notes. It describes a new BOLT 12 invoice feature that was added in a previous code change, and explicitly notes that signature verification is not yet implemented. There is no code change…

1ed6719bby bitromortac+7−01 file
No security note in commit
Open full analysis →Source commit ↗
Informational 16 AI analysisMessage 35 · Opaque
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

depends: add netbsd_LDFLAGS

This commit adds an empty placeholder for NetBSD linker flags in the build system. It is a one-line build configuration change with no functional or security effect visible in the diff.

699c21aeby fanquake+1−01 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 72 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

ci: add netBSD cross CI job

This commit adds a new automated build test for Bitcoin Core that compiles the software for NetBSD (a lesser-used operating system) from an Ubuntu machine. It does not change any Bitcoin code, wallet logic, network behavior, or security se…

c43b7a11by fanquake+52−03 files
No security note in commit
Open full analysis →Source commit ↗
Informational 18 AI analysisMessage 50 · Thin
EL ElectrumElectrum BitcoinSoftware wallets

qml: android on-screen keyboard submit trigger accepted

This commit tweaks the Android on-screen keyboard behavior in Electrum's QML wallet search screen. It sets the Enter key to 'Done' and hides the 'Create Wallet' button while the user is typing a search. There is no clear security problem h…

No security-relevant code paths modifiedUI-only change to on-screen keyboard and button visibilityNo input validation, authentication, or cryptographic logic changed
5fe0a292by Sander van Grieken+3−11 file
No security note in commit
Open full analysis →Source commit ↗
Low 45 AI analysisMessage 62 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

fix(core): embed the bitcoin-only vendor header in bitcoin-only builds

This commit fixes a build-time logic bug in Trezor firmware where the wrong vendor signature header could be embedded in Bitcoin-only firmware builds. The change makes the build system correctly detect Bitcoin-only mode by checking that th…

Build-system logic affecting signed firmware vendor header selectionFeature-flag mismatch between 'bitcoin_only' and absence of 'universal_fw'Potential for incorrect vendor header embedding in firmware artifacts
b517e0a0by Andrew Kozlik+5−11 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 47 · Thin
LL Lightning LabsLND BitcoinLightning Network

docs: update release notes

This commit only adds a release notes document. It does not change any program code. The notes mention that a separate pull request fixed bugs in how LND decodes onion-routed Lightning messages, but this commit itself is purely documentati…

68bc7691by bitromortac+71−01 file
No security note in commit
Open full analysis →Source commit ↗
Low 49 AI analysisMessage 83 · Strong
LL Lightning LabsLND BitcoinLightning Network

lnwire: preserve unknown odd zero-length final hop TLVs

This commit fixes a small but real bug in how LND decodes onion-routed messages (used in Lightning Network offers and blinded paths). Unknown extra data fields with a valid but empty value were accidentally dropped because the code used a …

Loss of protocol data: valid unknown odd zero-length TLVs were dropped during decodeTLV parsing logic conflated 'recognized type' (nil map entry) with 'zero-length value' (empty byte slice)Fix changes skip condition from length check to nil check
bc5cfb5aby bitromortac+30−42 files
No security note in commit
Open full analysis →Source commit ↗
Moderate 60 AI analysisMessage 85 · Strong
LL Lightning LabsLND BitcoinLightning Network

lnwire: reject onion message payloads with unknown even types

This commit fixes a standards-compliance bug in how LND decodes onion-routed messages in the Lightning Network. The relevant protocol rule (BOLT 4) says that if a message contains an unknown even-numbered data field, the receiver must reje…

Protocol compliance fix for BOLT 4 'must understand' even TLV typesPreviously accepted malformed/ambiguous onion message payloadsPotential for protocol confusion or forwarding of invalid onion messages
33c510faby bitromortac+68−62 files
Vendor flagged security relevance
Open full analysis →Source commit ↗
Moderate 60 AI analysisMessage 83 · Strong
LL Lightning LabsLND BitcoinLightning Network

lnwire: reject onion message payloads with multiple final hop fields

This change tightens how LND handles special 'final hop' data in onion-routed Lightning messages. Previously, a message could bundle several final-hop payload types (such as an invoice request, an invoice, and an invoice error) together an…

Protocol-conformance fix enforcing BOLT 4 final-hop payload count rulePrevents ambiguous or conflicting final-hop message interpretationRejects bundled invoice_request/invoice/invoice_error payloads
233e3777by bitromortac+29−222 files
No security note in commit
Open full analysis →Source commit ↗
Informational 12 AI analysisMessage 78 · Adequate
LL Lightning LabsLND BitcoinLightning Network

bolt12: add TUint32 and invoice subtypes

This commit adds new data-encoding helpers for the BOLT 12 Lightning invoice format, including a truncated uint32 type, blinded payment info records, and fallback address records. It is a pure feature-addition patch with no bug fixes or se…

New codec code for untrusted wire data includes length caps and minimal-encoding validationNo CVE, advisory, or vendor security disclosure referenced in commit or supplied materialsNo removal of unsafe code or correction of prior behavior observed
e548d62dby bitromortac+639−03 files
No security note in commit
Open full analysis →Source commit ↗
Low 44 AI analysisMessage 73 · Adequate
LL Lightning LabsLND BitcoinLightning Network

bolt12: inject feature-bit catalogues into Offer and InvoiceRequest validators

This change updates how the LND code checks feature bits in BOLT 12 offers and invoice requests. Previously, the read-side validator treated every even feature bit as unknown and would reject it, because it had no list of known features. N…

Feature-bit validation logic changed from hard-coded nil catalogue to caller-supplied catalogueWrite-side feature enforcement removed entirelyRead-side now accepts even feature bits that the local node knows, rejects only unknown even bits
732b0413by bitromortac+61−182 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 →