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.

24Projects watched
17784Commits captured
17252AI analyses
98High-risk findings · 30d
The watch feed

Changes worth understanding

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

17252 analyses
Highest risk·RSS
Informational 15 AI analysisMessage 68 · Adequate
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Use TxInEncoder for TxIn encoding

This is a small internal code cleanup in the rust-bitcoin library. It changes how transaction input (TxIn) objects are prepared for serialization so they use a dedicated wrapper type (TxInEncoder) instead of a generic three-field encoder. …

Commit message uses language ('fails to properly encapsulate') that can sound security-adjacent, but describes a design/encapsulation issue rather than a concrete vulnerabilityNo change to serialized wire format, field order, or public API visible in the diffNo references to CVEs, advisories, security reports, or researcher attribution in commit or supplied materials
ef12ebeeby Abeeujah+3−31 file
No security note in commit
Informational 16 AI analysisMessage 68 · Adequate
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Use TxOutEncoder for TxOut encoding

This is a small internal code cleanup in the rust-bitcoin library. It changes how transaction output (TxOut) objects are prepared for serialization so they use a dedicated wrapper type (TxOutEncoder) instead of directly combining two lower…

Refactor to use dedicated encoder newtype (TxOutEncoder) for TxOut consensus encodingCommit message uses security-adjacent language ('properly encapsulate inner state', 'encoding behavior')No diff evidence of memory safety bug, consensus mismatch, or injection point
d30b2812by Abeeujah+2−21 file
No security note in commit
Informational 15 AI analysisMessage 68 · Adequate
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Use BlockEncoder for Block encoding

This is a small internal code cleanup in the rust-bitcoin library. It changes how Bitcoin block objects are encoded to use a dedicated BlockEncoder wrapper instead of a generic two-part encoder. The actual bytes produced are unchanged; onl…

7393b06cby Abeeujah+3−31 file
No security note in commit
Informational 15 AI analysisMessage 28 · Opaque
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Update API files

This commit only updates generated API snapshot files that list what types and functions are publicly exposed by the library. The actual code did not change; only the recorded API signatures were updated to reflect new type aliases (shorte…

1fdb9c65by Abeeujah+6−62 files
No security note in commit
Informational 15 AI analysisMessage 65 · Adequate
EL ElectrumElectrum BitcoinSoftware wallets

exchange rate: remove CoinDesk provider

This commit simply removes the CoinDesk exchange-rate provider from Electrum because CoinDesk's old API no longer works and its new API requires a paid authorization token. It is a routine cleanup, not a security fix.

6571e479by f321x+0−1972 files
No security note in commit
Informational 15 AI analysisMessage 70 · Adequate
LDK Lightning Dev Kitrust-lightning BitcoinCryptographic librariesLightning Network

fuzz: inline chanmon finish invariants

This commit is a minor internal refactoring of a fuzz test file. It moves a small helper function's contents directly into the place where it was called, changing a loop over three hard-coded nodes into a generic loop. There is no change t…

c468bb82by Joost Jager+8−121 file
No security note in commit
Informational 15 AI analysisMessage 78 · Adequate
LDK Lightning Dev Kitrust-lightning BitcoinCryptographic librariesLightning Network

fuzz: factor chanmon finish cleanup helper

This commit is a simple code cleanup inside a fuzz testing harness. It moves an existing loop that relays and mines transactions into a new helper function, then calls that helper from the existing 'finish' method. No behavior changes are …

a4d8301fby Joost Jager+25−241 file
No security note in commit
Informational 15 AI analysisMessage 78 · Adequate
LDK Lightning Dev Kitrust-lightning BitcoinCryptographic librariesLightning Network

fuzz: add chanmon holder signer fuzz ops

This commit only adds new fuzz-testing commands to an existing test harness. It lets the fuzzer temporarily block and then re-enable the local node's own signing operations during simulated channel failures. There is no change to productio…

6ae2634eby Joost Jager+26−31 file
No security note in commit
Informational 15 AI analysisMessage 72 · Adequate
ER electrselectrs BitcoinIndexing infrastructureSoftware wallets

docs: fix beta Debian repository links

This commit fixes broken documentation links. It changes three Markdown links from an incorrect anchor name (binaries.md#cnative-os-packages) to the correct one (binaries.md#native-os-packages). There is no code change and no security rele…

31c3fc5bby haoshengzhen+3−32 files
No security note in commit
Informational 15 AI analysisMessage 73 · Adequate
EL ElectrumElectrum BitcoinSoftware wallets

hw_wallet/qt: reuse device message dialog across button requests

This commit is a user-interface performance and polish fix for Electrum's hardware wallet integration. It stops the app from destroying and recreating the same on-screen prompt every time a hardware wallet asks the user to confirm a transa…

898a4c27by Sasha Zykov+15−11 file
No security note in commit
Informational 15 AI analysisMessage 73 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

devtools: add --markdown output to credit for release notes

This commit is a harmless developer tooling improvement. It adds a new --markdown option to a helper script that generates contributor lists for release notes, and updates the release checklist to use it. There is no security relevance.

58f0c16aby Sangbida Chaudhuri+77−142 files
No security note in 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