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
16917Commits 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 91 · Strong
EP Elements ProjectCore Lightning BitcoinLightning Network

tests: compare medians in test_no_delay instead of means

This commit only changes a single test file. It swaps a flaky statistical comparison (mean with standard-error margin) for a more stable one (median with a fixed 20 ms margin) in a timing test about TCP Nagle delays. There is no change to …

365428bbby Ken Sedgwick+20−301 file
No security note in commit
Open full analysis →Source commit ↗
Informational 13 AI analysisMessage 72 · Adequate
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

test(zcash): restore transparent-output PCZT coverage

This commit only adds a new automated test for the Zcash cryptocurrency code. It restores test coverage to make sure that an Orchard (privacy-focused) transaction with a regular transparent output is still accepted by the validation logic.…

4bdf2148by Adam Tucker+44−01 file
No security note in commit
Open full analysis →Source commit ↗
Low 37 AI analysisMessage 57 · Thin
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

fix(zcash): allow transparent-only V6 PCZTs

This commit changes how Keystone's Zcash transaction handling treats version 6 (V6) PCZTs. Previously, all V6 Zcash transactions were rejected in the non-cypherpunk (transparent-only) code path. The patch now allows V6 transactions as long…

Guard relaxation: V6 PCZTs no longer blanket-rejected in transparent-only buildsBoundary enforcement remains for shielded Sapling/Orchard/Ironwood contentUnknown transaction versions still rejected
ba4ecf28by Adam Tucker+127−954 files
No security note in commit
Open full analysis →Source commit ↗
Moderate 59 AI analysisMessage 62 · Adequate
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

fix(zcash): validate empty shielded bundle balances

This commit adds a validation check for Zcash PCZT (Partially Created Zcash Transaction) parsing in the Keystone hardware wallet firmware. It ensures that if an Orchard or Ironwood shielded bundle contains no actions, its declared value su…

Input validation added for empty shielded bundle value_sumPotential balance-consistency issue in Zcash PCZT handlingTest case demonstrates malformed PCZT rejection
5e05a21aby Adam Tucker+99−01 file
No security note in commit
Open full analysis →Source commit ↗
Informational 10 AI analysisMessage 40 · Thin
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

chore: update ci

This commit is described as a routine CI (Continuous Integration) update with only one line changed in one file. No diff content is available, and there are no verified references suggesting any security relevance. It appears to be a munda…

7f2c4423by soralit+1−11 file
No security note in commit
Open full analysis →Source commit ↗
Moderate 57 AI analysisMessage 57 · Thin
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

fix(zcash): require an owned singleton input

This commit changes how the Keystone hardware wallet validates Zcash PCZT (partially-created transaction) files before signing. Previously, under a 'batch' policy it required at least one shielded input belonging to the wallet. After the c…

Change in transaction ownership validation before signingNew condition combines empty shielded actions with absence of transparent inputs to reject PCZTTest renamed to expect rejection at check phase for foreign seed
4277d422by Adam Tucker+49−262 files
No security note in commit
Open full analysis →Source commit ↗
Informational 14 AI analysisMessage 62 · Adequate
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

refactor(zcash): simplify unsupported PCZT helpers

This is a simple code cleanup: three internal helper functions in the Zcash PCZT handling code are renamed to remove the word 'legacy' from their names. The actual behavior and security checks stay exactly the same. There is no functional …

0f0dc78aby Adam Tucker+6−63 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 57 · Thin
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

refactor(zcash): display shielded pool names

This commit is a small code cleanup in the Zcash transaction handling code. It replaces a custom `label()` method on the `ShieldedPool` type with Rust's standard `Display` trait, so the pool name prints the same way in error messages. Ther…

83ac1e21by Adam Tucker+16−194 files
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 text files to reflect that a Rust trait now requires an internal 'sealed' marker. It is a documentation or API-snapshot update with no code changes and no security relevance.

fd897c4cby Mitchell Bagot+2−22 files
No security note in commit
Open full analysis →Source commit ↗
Informational 18 AI analysisMessage 48 · Thin
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Seal PushBytesErrorReport

This commit seals a Rust trait called PushBytesErrorReport so that only two specific internal types can implement it. Sealing prevents outside code from implementing the trait, which reduces the chance that a future change accidentally bre…

Trait sealing to prevent external implementationsDefensive API-hardening patternNo memory-safety or cryptographic logic changed
26ec3fc2by Mitchell Bagot+7−11 file
No security note in commit
Open full analysis →Source commit ↗
Informational 12 AI analysisMessage 95 · Strong
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Add test case to prevent regressions to Witness FromIterator

This commit only adds a new automated test. It does not change any production code. The test checks that building a Witness from a very long iterator (over 4 million empty byte slices) does not accidentally drop elements. It is a regressio…

Regression test for prior Witness::from_iter length handlingNo production code changes
a6751a59by Mitchell Bagot+11−01 file
No security note in commit
Open full analysis →Source commit ↗
Moderate 52 AI analysisMessage 83 · Strong
BT btcsuitebtcd BitcoinNode implementations

address: reject v2-v16 segwit addresses encoded with bech32

This commit fixes a bug in how btcd decodes certain Bitcoin SegWit addresses. Under the BIP-350 standard, newer witness versions (versions 2 through 16) must use a newer checksum called bech32m, but btcd was only enforcing that rule for ve…

BIP-350 standards non-compliance in SegWit address decodingAcceptance of bech32-encoded v2-v16 witness programs that should require bech32mReference test vectors added as regression tests
27bbee94by Lrifton92+68−52 files
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 →