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.

23Projects watched
16913Commits 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
Informational 15 AI analysisMessage 67 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

test(core): fix Stellar payment request tests.

This commit only updates test data and a test assertion for Stellar payment request tests. It does not change any production firmware code, so it has no direct security impact on users.

e9bd96f3by Jun Luo+6−52 files
No security note in commit
Informational 15 AI analysisMessage 100 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

test(stellar): merge test_xdr with test_sign_tx

This commit is a test-code cleanup only. It merges two Stellar-related test functions and adds a consistency check inside the main signing test. No production firmware code, cryptographic handling, or device behavior was changed. There is …

9a1ee9a3by Jakub Janků+16−171 file
No security note in commit
Informational 12 AI analysisMessage 95 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

test(stellar): verify signatures in fixtures

This commit only changes a test file for Stellar cryptocurrency transaction signing. It adds a check that the expected signatures stored in test fixtures are mathematically valid, so that future tests don't accidentally treat a bad signatu…

test-only changefixture integrity verification addedno modification of signing implementation
8ea9cc20by Jakub Janků+7−21 file
No security note in commit
Informational 15 AI analysisMessage 67 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

test(stellar): check parsed op count

This commit only changes a single test file. It adds strict=True to a zip() loop in a Stellar cryptocurrency test so that the test fails if the number of original and parsed operations do not match. There is no change to production firmwar…

c8966440by Jakub Janků+1−11 file
No security note in commit
Low 27 AI analysisMessage 99 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

test: Nudge toward QT_STYLE_OVERRIDE=fusion on macOS

This change only affects Bitcoin Core's own Qt graphical-interface test suite on macOS. It forces the tests to use Qt's 'Fusion' style instead of the native Mac style, because the native Mac style can crash when running in the minimal test…

Null-pointer dereference crash avoided in Qt test codeWorkaround for upstream Qt bug QTBUG-49686Test-only change; no production wallet/network code modified
fa0c8337by MarcoFalke+6−01 file
No security note in commit
Informational 15 AI analysisMessage 57 · Thin
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

refactor: Run clang-format on qt test_main.cpp

This commit only reformats a single Qt test file using clang-format. It moves preprocessor directives (#if, #else, #endif) to the start of lines and adjusts indentation. No code logic, behavior, or functionality was changed.

faa50c08by MarcoFalke+5−51 file
No security note in commit
Informational 15 AI analysisMessage 100 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

test(ethereum): check function signature at source.

This is a test-only refactoring commit. It changes how Ethereum function signatures are represented in firmware source code (from hex strings converted at runtime to raw byte literals) and updates the corresponding unit test to verify thos…

54c20421by PrisionMike+135−1272 files
No security note in commit
Informational 17 AI analysisMessage 68 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

depends, zeromq: Apply upstream patch

This commit adds a patch to Bitcoin Core's build system that fixes a missing C++ header include in the ZeroMQ library. The missing include can cause compilation to fail on some systems because the compiler cannot find 'std::nothrow'. It is…

Missing standard header include in dependencyUpstream build-fix patch backported into vendored buildNo runtime behavior change to Bitcoin Core logic
e446ea09by Hennadii Stepanov+126−12 files
No security note in commit
Low 32 AI analysisMessage 100 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

fix(core): re-implement `draw_simple()` to avoid scoping violations

This commit fixes a UI lifecycle bug in Trezor firmware. The old `draw_simple()` function started a layout but did not properly wait for it to finish or stop it, which could leave stale UI tasks running ('scoping violations'). The new `int…

Fixes UI task lifecycle / scoping violationPrevents stale layout tasks from continuing after prompt should have endedPassphrase prompt flow affected
d772ca89by Roman Zeyde+36−208 files
No security note in commit
Informational 12 AI analysisMessage 77 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

refactor(core): use simpler `interact` in FIDO & ButtonRequest waiting

This commit is a straightforward internal code cleanup. It replaces several direct uses of a lower-level UI helper (`Layout(...).get_result()`) with a simpler wrapper function (`interact_simple`). The behavior described in the comments—spe…

c3895435by Roman Zeyde+14−276 files
No security note in commit
Moderate 64 AI analysisMessage 91 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

units: Fix off-by-one error in satisfied by height

This commit fixes an off-by-one error in how the rust-bitcoin library decides whether a Bitcoin transaction's height-based locktime is satisfied. Because the code both added 1 to the current chain tip height and used a 'less than or equal …

Off-by-one in locktime satisfaction logicIncorrect boundary unit test reinforced the bugSame class of bug previously fixed for time-based locktimes in PR #6384
6707389fby Tobin C. Harding+12−192 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