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
17782Commits captured
17251AI analyses
98High-risk findings · 30d
The watch feed

Changes worth understanding

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

17251 analyses
Highest risk·RSS
Informational 15 AI analysisMessage 80 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

ci: adapt bench subcommand to cargo-rbmt 0.4.0

This is a routine update to the project's automated testing configuration. It changes how benchmark tests are run in GitHub Actions to match a new version of an internal helper tool (cargo-rbmt 0.4.0). There is no user-facing change and no…

7ffed444by satsfy (Renato Britto)+15−11 file
No security note in commit
Informational 15 AI analysisMessage 95 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

ci: adapt default and no feature bip32 test for rbmt 0.4.0

This is a routine update to the project's automated testing configuration. A tool used to run example tests changed its syntax, so the developer updated one line to keep the same tests running the same way. There is no user-facing change a…

5f933d5cby satsfy (Renato Britto)+1−11 file
No security note in commit
Informational 15 AI analysisMessage 45 · Thin
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Automated update to rustc nightly-2026-06-26

This is a routine automated update that changes one line in the project's configuration file, bumping the recommended nightly Rust compiler version from June 12, 2026 to June 26, 2026. There is no code change, no bug fix, and no security r…

cfa24addby Update Nightly Rustc Bot+1−11 file
No security note in commit
Informational 15 AI analysisMessage 45 · Thin
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Automated update to cargo-rbmt-0.4.1

This is an automated version bump of an internal tooling file (rbmt-version) from one commit hash to another. The diff changes a single line containing a commit identifier. There is no code change to the rust-bitcoin library itself and no …

ae072165by Update RBMT Bot+1−11 file
No security note in commit
Informational 15 AI analysisMessage 76 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

doc: improve offline-signing-tutorial after 32489

This commit only fixes two small mistakes in a documentation file: it removes an outdated note and corrects a JSON example from curly braces to square brackets. There is no code change and no security impact.

68cb7840by Pablo Martin+2−41 file
No security note in commit
Informational 15 AI analysisMessage 50 · Thin
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

doc: Add release notes for 32489 (exportwatchonlywallet RPC)

This commit only adds documentation: a new release-notes file describing a previously merged feature (`exportwatchonlywallet` RPC). There is no code change, no bug fix, and no security-relevant behavior change in this patch.

cddbad32by Pablo Martin+15−01 file
No security note in commit
Informational 17 AI analysisMessage 80 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

fix(core): fix build on strange configurations

This commit fixes a build problem in Trezor's firmware. The code used a very common filename, version.h, which could accidentally pull in the wrong file from another software package during compilation. The fix creates a symlink with a mor…

Header name collision could theoretically cause wrong version metadata to be compiled into firmwareNo input validation, memory safety, or cryptographic change presentNo vendor disclosure of security relevance
ecc709d6by matejcik+2−12 files
No security note in commit
Informational 15 AI analysisMessage 85 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

build(xbuild): explicit support for compile output type

This is a build-system cleanup, not a security fix. It changes how the Trezor firmware build tells the compiler whether to produce object files or preprocessed source files, so that it no longer accidentally passes conflicting flags that n…

55fdcd3aby matejcik+34−93 files
No security note in commit
Informational 15 AI analysisMessage 85 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

build(core): silence clang warning for moductypes.c

This commit only changes a build script to suppress a compiler warning. It does not fix a security bug, change runtime behavior, or alter any device firmware code. The warning was about a string being slightly too long for its container in…

fd7ce43cby matejcik+10−11 file
No security note in commit
Informational 18 AI analysisMessage 85 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

build(core): replace -fsingle-precision-constant with explicit casts

This is a build-system cleanup for the Trezor hardware wallet firmware. The developers replaced a GCC-only compiler flag with portable warning flags and added explicit type casts in a handful of driver files to silence the new warnings. Th…

No security-relevant signals in commit message or diffChanges are build/compiler-warning hygiene, not vulnerability remediationExplicit casts reduce ambiguity but do not change intended arithmetic semantics
03e661ceby matejcik+40−358 files
No security note in commit
Informational 15 AI analysisMessage 97 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

build(core): avoid unused variable warning in rng_fill_buffer_strong

This is a minor build cleanup. A developer added a compile-time branch so that when neither the Optiga nor Tropic security chips are used, the 'strong' random-number wrapper simply calls the normal random-number function and returns. The o…

690a69f3by matejcik+8−01 file
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