CommitWatch RSS
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.

Explore the watch feed ↓See how scoring works →
24Projects watched
17692Commits captured
17209AI analyses
96High-risk findings · 30d
The watch feed

Changes worth understanding

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

17209 analyses
Highest risk·RSS
Informational 23 AI analysisMessage 50 · Thin
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

doc: add release note describing change for forbidden clients

This commit only adds a release note documenting a prior behavior change: Bitcoin Core will now immediately drop remote clients blocked by the -rpcallowip setting, instead of sending them a '403 Forbidden' error page. The commit itself cha…

Behavior change in access-control enforcement for RPC/REST interfaceImmediate disconnection instead of 403 response reduces information leakage to unauthorized clientsNo code change in this commit; security relevance is documentary only
55d3cd51by Matthew Zipkin+6−01 file
No security note in commit
Open full analysis →Source commit ↗
Low 47 AI analysisMessage 91 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

Squashed 'src/ipc/libmultiprocess/' changes from 16bf05dea02..28e056576a3

This commit updates a library Bitcoin Core uses for inter-process communication (libmultiprocess). The main functional change is adding an optional 'max_connections' limit to the ListenConnections() function, so a server can stop accepting…

Adds optional per-listener connection cap to IPC listenerPrevents unbounded acceptance of IPC connections at application levelIncludes regression tests for connection-limit enforcement
707d0dedby Ryan Ofsky+366−196 files
No security note in commit
Open full analysis →Source commit ↗
Moderate 57 AI analysisMessage 62 · Adequate
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

feat(zcash): resolve compact PCZT fields once in preflight

This commit changes how a hardware wallet handles Zcash transaction data before signing. Previously, some compact or abbreviated fields (like encrypted memos and hidden value commitments) were left as placeholders to be filled in later. No…

Normalization of compact/omitted cryptographic fields before signingRemoval of deferred 'FUTURE(omitted-field-recompute)' TODO in two entry pointsPrevention of potential signing-time re-resolution of memo/cv_net fields
2191ef08by Adam Tucker+94−61 file
No security note in commit
Open full analysis →Source commit ↗
Low 29 AI analysisMessage 62 · Adequate
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

chore(zcash): repin pczt stack to the upstream 2557 teststack

This commit updates the Zcash PCZT (Partially Created Zcash Transaction) library stack to a newer upstream test revision. It is a maintenance/dependency bump that adapts the firmware's code to new library APIs, adds error handling around s…

Dependency repin to newer pre-release upstream Zcash stackSerialization now returns Result and errors are propagated instead of panickingOptional PCZT v2 fields (cv_net, anchor, enc_ciphertext) now have fallback handling in sighash computation
a4fe0d5aby Adam Tucker+192−9710 files
No security note in commit
Open full analysis →Source commit ↗
Informational 18 AI analysisMessage 62 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

chore(core): don't log THP cache entries by default

This commit turns off routine debug logging for a cache that stores information about paired Bluetooth-like hosts in Trezor hardware wallets. The change prevents potentially sensitive pairing details from being written to debug logs by def…

Debug logging of pairing cache entries disabled by defaultPotential information disclosure via logs containing paired host names, app names, and MAC addressesNo functional code change; only logging behavior gated by new compile-time flag
ef3610fcby Roman Zeyde+5−41 file
No security note in commit
Open full analysis →Source commit ↗
Low 43 AI analysisMessage 100 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

refactor: Use u64 over size_t for all cache sizes to fix a 32-bit overflow

This commit fixes a bug in Bitcoin Core that only affects 32-bit computers. When the program calculated how much database cache to allocate, it multiplied a large default cache value by 10. On 32-bit systems that multiplication overflowed,…

Integer overflow in cache-size calculation on 32-bit systemsUnsigned multiplication overflow explicitly mentioned in commit message with runtime sanitizer outputType promotion from size_t to uint64_t to prevent platform-dependent width issues
fabafd91by MarcoFalke+37−285 files
Vendor flagged security relevance
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 90 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Replace encode with checksum encoding in tests

This commit only changes test code in the rust-bitcoin base58 module. It replaces calls to an old plain base58 encoder with equivalent base58check-encoded strings and a new checksum-based encoder. There is no change to production code, no …

903b5befby Mitchell Bagot+12−121 file
No security note in commit
Open full analysis →Source commit ↗
Informational 17 AI analysisMessage 73 · Adequate
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Replace external uses of base58 encoding with Base58CkString

This commit is a routine internal code cleanup in the rust-bitcoin project. It swaps old base58 encoding helper functions for a new equivalent type, Base58CkString, in three source files. There is no indication from the commit itself that …

No security-relevant signal in the diff: equivalent API swap onlyNo new dependencies or unsafe blocks introducedNo changes to input validation, parsing, or secret handling
7f5fbd13by Mitchell Bagot+10−103 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 68 · Adequate
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Remove unused old encoding functions

This commit simply deletes unused base58 encoding helper functions from the rust-bitcoin library. There is no security issue: the removed code is not called anywhere, and the public API is being cleaned up after a newer replacement type wa…

de3554c5by Mitchell Bagot+0−681 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 68 · Adequate
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Gate alloc-only decoding errors

This commit is a build-system cleanup, not a security fix. It hides certain error types from builds that do not enable the 'alloc' feature, because those error types are only used by decoding functions that already require 'alloc'. There i…

67925869by Mitchell Bagot+20−01 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 28 · Opaque
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Adjust crate level docs

This commit changes a single sentence in the crate's documentation. It clarifies that the base58 crate requires an allocator specifically for decoding, not for all operations. There is no code change and no security impact.

30a6f1c5by Mitchell Bagot+1−11 file
No security note in commit
Open full analysis →Source 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 →