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
17562Commits captured
17152AI analyses
88High-risk findings · 30d
The watch feed

Changes worth understanding

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

17152 analyses
Highest risk·RSS
Informational 15 AI analysisMessage 87 · Strong
EP Elements ProjectCore Lightning BitcoinLightning Network

CI: install CLN on macos and run selected pytest tests

This commit only changes the project's macOS CI workflow. It replaces a manual setup that started Bitcoin and Core Lightning manually with an automated pytest-based test run after installing the software. There is no change to the actual C…

e04d2f93by daywalker90+10−181 file
No security note in commit
Informational 15 AI analysisMessage 70 · Adequate
EL ElectrumElectrum BitcoinSoftware wallets

contrib/make_download: fix imports

This is a trivial bug fix in a helper script used to build Electrum's download web page. The script was missing an import statement needed to access a Python utility module. Without the import, the script crashed immediately with an Attrib…

58ae11d8by SomberNight+1−01 file
No security note in commit
Informational 17 AI analysisMessage 68 · Adequate
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Replace uses of Encoder2 with prefixed encoders

This commit is a straightforward internal cleanup in the rust-bitcoin library. It replaces verbose pairs of encoders (a length counter plus a raw slice/bytes encoder) with new combined 'prefixed' encoder types that do the same job. There i…

b6c5adb3by Mitchell Bagot+65−14111 files
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 (text listings of public types and methods). It does not change any source code, behavior, or fix any bug. There is no security relevance.

7119794fby Mitchell Bagot+256−03 files
No security note in commit
Informational 15 AI analysisMessage 95 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Add tests to cover the new length prefixed encoders

This commit only adds new unit tests for recently introduced encoder code. It does not change any production logic, fix bugs, or alter behavior. There is no security issue in the commit itself.

68702c8dby Mitchell Bagot+61−11 file
No security note in commit
Informational 15 AI analysisMessage 73 · Adequate
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Add new prefixed encoders for BytesEncoder and SliceEncoder

This commit adds two new helper types, PrefixedBytesEncoder and PrefixedSliceEncoder, to make it easier to encode byte slices and lists of items with a length prefix. It is a straightforward feature/refactoring change with no security rele…

8cf6b291by Mitchell Bagot+69−42 files
No security note in commit
Moderate 51 AI analysisMessage 85 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

fix(core/caesar): remove count limit in confirm_properties

This commit fixes a bug in the Trezor hardware wallet's Caesar UI layout where long lists of key-value properties (for example, transaction details shown on the device screen) could either crash debug builds or be silently cut off in produ…

Silent truncation of user-visible confirmation data in production buildsPanic/crash in debug builds on oversized property listsUI consistency fix aligning Caesar layout with other layouts
b235e018by Jakub Janků+5−192 files
No security note in commit
Low 28 AI analysisMessage 45 · Thin
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

Remove obsolete NU6.3 cfg

This commit removes a compile-time feature flag called NU6.3 from the Zcash code in the Keystone hardware wallet firmware. Previously, Ironwood (a newer Zcash shielded pool) and v6 transaction support were only compiled when the 'zcash_uns…

Feature flag removal enables previously conditional consensus-critical code (v6 transaction sighash, Ironwood bundle signing)No logic changes to cryptographic or parsing routines are visible in the diffNo commit message, changelog, or reference describes a security fix or vulnerability
a99e518eby Adam Tucker+8−1019 files
No security note in commit
Informational 18 AI analysisMessage 57 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

refactor(core): improve monero typing

This is a code cleanup and type-safety refactor for the Monero parts of the Trezor firmware. It adds stricter type hints, asserts that certain values are not missing, and fixes a minor return-value bug in a helper that encrypts data. There…

assert guards added to prevent use of None values in Monero address and transaction handlingchacha_poly.encrypt return signature corrected from 3-tuple to 2-tuple, with caller updatedtype annotations tightened across Monero signing, key image sync, and bulletproof code
54bfd51bby M1nd3r+180−10718 files
No security note in commit
Low 25 AI analysisMessage 85 · Strong
EP Elements ProjectCore Lightning BitcoinLightning Network

connectd: set IPV6_V6ONLY=1 on IPv6 sockets for consistent dual-stack behaviour

This commit fixes a network setup bug in Core Lightning's connection daemon. On some operating systems (macOS, Fedora, Arch, and default Linux kernels), an IPv6 'listen on all addresses' socket was also covering IPv4, which prevented a sep…

Denial-of-service availability fix: on affected systems, the node could not listen on IPv4 when configured for wildcard IPv4+IPv6Memory leak fix in connectd error pathNo evidence of malicious intent in the diff
730e5881by Níckolas Goline+21−32 files
No security note in commit
Informational 15 AI analysisMessage 83 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

tests: replace repeated xfail/suppresion by decorators

This commit is a test-code cleanup only. It replaces repeated snippets in automated tests with reusable decorators and marker aliases. No firmware behavior, cryptography, or user-facing functionality is changed, so it has no security impac…

e91c588bby M1nd3r+22−344 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