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
17688Commits captured
17209AI analyses
96High-risk findings · 30d
The watch feed

Changes worth understanding

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

17209 analyses
Highest risk·RSS
Informational 12 AI analysisMessage 55 · Thin
EP Elements Projectlibwally-core BitcoinCryptographic librariesSoftware wallets

tests: add more test_clear tests

This commit only adds new test cases to an existing test file. It does not change any production code, fix a bug, or alter behavior. The tests check whether sensitive secret bytes are cleared from the call stack after using certain cryptog…

Adds stack-clearing regression tests for secret-handling functionsUses a distinct sentinel value to avoid false positives from BIP39 testsTargets sensitive operations: BIP32 seed derivation, EC private key verification, ECDSA signing, and HMAC-SHA256
9d05ca17by pythcoiner+67−01 file
No security note in commit
Open full analysis →Source commit ↗
Low 47 AI analysisMessage 73 · Adequate
EP Elements Projectlibwally-core BitcoinCryptographic librariesSoftware wallets

internal: mark internal functions as hidden visibility when possible

This change is a hardening patch for a cryptocurrency wallet library. It tells the compiler to keep certain internal helper functions private to the library, so calls to them stay inside the library instead of going through an external loo…

Hardening against secret material leakage via stack spillsCompiler/linker visibility hardeningPLT/GOT indirection reduction
2d36c91dby Jon Griffiths+78−555 files
Vendor flagged security relevance
Open full analysis →Source commit ↗
Informational 18 AI analysisMessage 58 · Thin
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Properly format Custom Range in date range selector (#7439)

This commit fixes how a custom date range is displayed and submitted in BTCPay Server's web interface. It changes the way the browser's timezone is sent back to the server and how date/time inputs are pre-filled. There is no clear security…

No explicit security relevance stated in commit title or messageChanges input handling and form submission for date/time filtersRemoves a named form input (TimeZone) and replaces it with a submit button carrying a structured command
6c9d715fby Nicolas Dorier+82−327 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 62 · Adequate
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

refactor(zcash): rename redacted PCZT signing helper

This commit is a simple rename of an internal function from `sign_pczt_to_pczt` to `sign_and_redact_pczt` in the Zcash Rust code. No behavior, logic, or security properties changed; it only makes the function name more descriptive. There i…

01bd8e2bby Adam Tucker+4−42 files
No security note in commit
Open full analysis →Source commit ↗
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 ↗
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 →