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
16841Commits captured
7504AI analyses
60High-risk findings · 30d
The watch feed

Changes worth understanding

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

7504 analyses
Highest risk·RSS
Low 42 AI analysisMessage 62 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

fix(rust/trezor-thp): do not retransmit before whole message is sent

This commit fixes a bug in the Trezor hardware wallet's THP (Trezor Host Protocol) Rust code. Previously, the device could start retransmitting a message before it had finished sending all the fragments (pieces) of the current message. The…

Protocol state machine correctionPrevents premature retransmission of incomplete message fragmentsCould mitigate denial-of-service or protocol desynchronization during host-device communication
f4962a95by Martin Milata+8−11 file
No security note in commit
Informational 12 AI analysisMessage 72 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

test(rust/trezor-thp): do not retransmit before whole message is sent

This commit only adds a new automated test for the Trezor hardware protocol (THP) channel code. It checks that retransmitting a partially sent message does not cause duplicate or extra packets. There is no change to production code, no bug…

c822c5acby Martin Milata+74−01 file
No security note in commit
Low 46 AI analysisMessage 57 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

fix(rust/trezor-thp): packet length edge cases

This commit fixes how a Trezor hardware wallet's Rust code handles incoming USB-like packets. Previously, the code resized its receive buffer based on a size value returned after a packet was already accepted, which could lead to incorrect…

Buffer sizing logic changed from post-accept resize to pre-accept size checkPacket length parsed from control byte/header before buffer useReceive buffer now resized only when incoming length exceeds current capacity
d81f5684by Martin Milata+13−212 files
No security note in commit
Informational 15 AI analysisMessage 35 · Opaque
BC Bitcoin Corelibsecp256k1 BitcoinCryptographic libraries

release-process: Refactor

This commit is a simple reorganization of the project's release-process documentation. It renames some sections, splits steps into clearer subsections, and adds minor wording clarifications (for example, reminding maintainers to manually r…

34f00ca9by Tim Ruffing+13−81 file
No security note in commit
Informational 15 AI analysisMessage 53 · Thin
BC Bitcoin Corelibsecp256k1 BitcoinCryptographic libraries

release-process: Add signing of tarball

This commit updates the project's release instructions to add a new step: creating a GPG-signed source-code tarball when making a release. It is a documentation-only change that improves release integrity and does not modify any code or fi…

Documentation-only change to release processAdds GPG signing of release tarballsReferences expected signing key in SECURITY.md
fae22e77by Tim Ruffing+14−41 file
No security note in commit
Informational 15 AI analysisMessage 35 · Opaque
BC Bitcoin Corelibsecp256k1 BitcoinCryptographic libraries

release-process: Fix nits

This commit only makes minor wording edits to the project's release-process documentation. It changes a few phrases from 'PR is merged' to 'PR has been merged', adds 'a' before 'PR', and adds a new step reminding maintainers to merge relea…

4a73b1aeby Tim Ruffing+4−31 file
No security note in commit
Informational 15 AI analysisMessage 45 · Thin
BC Bitcoin Corelibsecp256k1 BitcoinCryptographic libraries

release-process: Add "cleaning up"

This commit simply adds a short 'Cleaning up' section to the project's release-process documentation. It describes administrative tasks like closing a GitHub milestone and removing a label after a release. There is no code change and no se…

b0a0ae82by Tim Ruffing+6−01 file
No security note in commit
Informational 15 AI analysisMessage 50 · Thin
BC Bitcoin Corelibsecp256k1 BitcoinCryptographic libraries

release-process: Add attaching output of check-abi.sh to PR

This is a documentation-only change to the project's release checklist. It adds a step telling release maintainers to attach the output of an ABI compatibility checking tool to release pull requests. There is no code change, no cryptograph…

12d9cfd8by Tim Ruffing+2−11 file
No security note in commit
Informational 15 AI analysisMessage 83 · Strong
EP Elements ProjectCore Lightning BitcoinLightning Network

tests: fix test_low_fd_limit failing on RLIM_INFINITY platforms

This commit fixes a test that was failing on macOS and other systems where the operating system reports no practical upper bound on the number of open files (called RLIM_INFINITY). The test was passing values larger than a 32-bit unsigned …

ae53e877by Níckolas Goline+11−22 files
No security note in commit
Moderate 62 AI analysisMessage 45 · Thin
LD LedgerLedger Bitcoin app BitcoinHardware wallets

Additional integrity checks for Merkle proofs

This commit adds extra safety checks when the Ledger Bitcoin app verifies Merkle proofs, which are cryptographic evidence used to confirm that a piece of data belongs to a larger set. The changes ensure that the proof length matches the ex…

Merkle proof length validation against leaf depthEnforcement of Merkle leaf prefix byte 0x00Prevention of streaming invalid preimage data before callback invocation
c44c9b8bby Salvatore Ingala+32−44 files
Vendor flagged security relevance
Informational 15 AI analysisMessage 55 · Thin
LD LedgerLedger Bitcoin app BitcoinHardware wallets

Add unit tests for get_merkle_preimage

This commit only adds new unit tests for existing code. It does not change any production behavior, fix a bug, or introduce new functionality. The tests verify that certain security checks (proof length and domain separator checks) already…

Test-only commit with no production code changesTests verify existing Merkle proof length validation rejects internal-node-as-leaf and overlong proofsTests verify existing leaf preimage domain-separator check rejects internal-node preimages and non-zero prefixes
05445baeby Salvatore Ingala+334−03 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