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 →
23Projects watched
16824Commits 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
Informational 19 AI analysisMessage 45 · Thin
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

doc: Add doc/release-notes-35836.md

This commit only adds a release note documenting a prior change: the `fundrawtransaction` RPC command no longer silently accepts a boolean value in its second argument and will now report an error instead. It is a documentation-only change…

No executable code changed in this commitRelease note describes stricter RPC argument type checking in a prior changePrior behavior was a silent no-op fallback, not a memory safety or consensus issue
ddddffdaby MarcoFalke+5−01 file
No security note in commit
Open full analysis →Source commit ↗
Low 44 AI analysisMessage 89 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

feat(core/rust): coerce empty slices to null FatPtrs

This commit changes how Trezor firmware passes empty data buffers from Rust code to C code. Previously, an empty Rust slice could produce a pointer that looks like a memory address but points to nothing valid. The patch forces such empty s…

Rust-to-C FFI pointer handling changeEmpty slice now coerced to NULL FatPtrExplicitly motivated by C interop pointer validity checks
c0d53744by matejcik+49−61 file
No security note in commit
Open full analysis →Source commit ↗
Informational 12 AI analysisMessage 77 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

refactor(core/rust): use FatPtr in rust syslog binding

This commit is a small internal cleanup in the Rust code that handles device logging. It replaces manual pointer-and-length handling with a helper called FatPtr, which is designed to safely represent string slices. There is no indication t…

178950a9by matejcik+12−151 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 45 · Thin
LDK Lightning Dev Kitrust-lightning BitcoinCryptographic librariesLightning Network

Update crate repository links to forgejo

This commit simply updates the 'repository' web links in 15 package metadata files from GitHub to a self-hosted Forgejo instance. It does not change any program code, build logic, dependencies, or security behavior. There is no security is…

eb77676dby benthecarman+15−1515 files
No security note in commit
Open full analysis →Source commit ↗
Low 33 AI analysisMessage 76 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

wally: update libwally to v1.5.6

This commit updates the bundled libwally library to version 1.5.6. The practical effect is that calling the JSON-RPC `signpsbt` command on a PSBT that is already signed now succeeds as a harmless no-op, instead of returning an error on Bit…

Dependency update to incorporate upstream bug fixBehavior change from error to no-op on re-signing signed PSBTsTaproot keypath handling change in upstream cryptographic library
37526ca4by daywalker90+7−82 files
No security note in commit
Open full analysis →Source commit ↗
Moderate 59 AI analysisMessage 60 · Adequate
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

only save certificates passing hostname verification as ca validated, and retain not yet valid certificates

This commit tightens how Sparrow Wallet saves and reuses TLS certificates for private servers. Previously, any certificate that passed a basic CA check was saved as 'CA validated' even if it didn't actually match the server's hostname. Tha…

Missing hostname verification before saving CA-trusted certificateBroad exception handling previously caused deletion of saved certificates on any CertificateExceptionCertificate pinning/trust-store logic for private Electrum servers
372ebf2fby Craig Raw+38−61 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 28 · Opaque
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Update API files

This commit only updates generated API snapshot text files to remove two lines that documented a `From<u16>` conversion for a locktime type. No actual Rust source code was changed, so there is no runtime behavior change or security fix in …

6ea25bedby Mitchell Bagot+0−123 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 78 · Adequate
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Remove From<u16> from NumberOfBlocks

This commit removes a convenience way to create a 'number of blocks' value directly from a plain u16 number, replacing all uses with an existing named constructor called from_height. It is a routine API cleanup to make two related types co…

f9b08eb1by Mitchell Bagot+18−235 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 60 · Adequate
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

base58ck: Bump version to 0.5.0

This commit is a routine version bump for the base58ck crate from 0.4.0 to 0.5.0. It only updates version numbers in package manifests, lock files, and adds a changelog entry describing unrelated feature changes. There are no code changes,…

8479b56eby Tobin C. Harding+22−168 files
No security note in commit
Open full analysis →Source commit ↗
Informational 12 AI analysisMessage 70 · Adequate
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Split decode into build_base256

This commit is a routine internal code cleanup in the base58 decoding module. It splits the existing decode logic into a helper function called build_base256 so that a future no-allocation version can reuse it. There is no security fix her…

0a70c578by Mitchell Bagot+41−212 files
No security note in commit
Open full analysis →Source commit ↗
Informational 21 AI analysisMessage 70 · Adequate
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

base58: Add decode_check_to_array

This commit adds a new no-allocator base58 decoder for short fixed-size data in the rust-bitcoin base58 crate. It is a feature addition, not a fix for a known vulnerability. The change exposes a new public function and error type and restr…

New checksum-verifying decoder added to no-alloc code pathError type gating changed: several error types now compiled without alloc as pub(crate)Input length capped at 128 characters to bound stack buffer
ae6ea361by Mitchell Bagot+184−282 files
No security note in commit
Open full analysis →Source commit ↗
Informational 14 AI analysisMessage 68 · Adequate
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Add tests for decode_check_to_array

This commit only adds new unit tests for an existing Base58 decoding function and adjusts which tests run when the 'alloc' memory-allocation feature is enabled. It does not change any production code, so it cannot introduce a security vuln…

7e6ab80bby Mitchell Bagot+72−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 →