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
18168Commits captured
17444AI analyses
103High-risk findings · 30d
The watch feed

Changes worth understanding

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

17444 analyses
Highest risk·RSS
Informational 15 AI analysisMessage 85 · Strong
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

refactor: flatten check_transparent_input with let-else + map_or

This commit is a pure code-style refactor in a Zcash transaction-checking function. It rewrites nested match statements into a flatter let-else and map_or pattern, but the commit message and diff show no change to the actual logic, error m…

e76f36e3by Adam Tucker+31−361 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 73 · Adequate
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

style: import alloc::{format, vec} at the top of check.rs

This commit is purely a code-style cleanup: it replaces repeated `alloc::format!` and `alloc::vec!` calls with a single `use` import at the top of the file. The commit message explicitly states there is no behavior change, and the diff con…

658f5b57by Adam Tucker+10−101 file
No security note in commit
Open full analysis →Source commit ↗
Informational 12 AI analysisMessage 85 · Strong
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

refactor: drop dead seed-fingerprint check from transparent derivation helper

This commit is a code cleanup (refactor) in the Zcash PCZT handling code. It removes an unused internal check and an unused function parameter, renames a helper function, and changes its return type. The commit message explicitly states th…

No security-relevant behavior change in the diffRemoval of dead/unreachable code pathFunction signature simplification (refactor)
d6e8bbdeby Adam Tucker+14−232 files
No security note in commit
Open full analysis →Source commit ↗
Informational 14 AI analysisMessage 85 · Strong
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

refactor: thread ShieldedPool enum instead of stringly pool labels

This is a code cleanup change with no security impact. It replaces free-form text labels like "Orchard" and "Ironwood" with a fixed enum type when checking, parsing, and signing Zcash shielded transaction bundles. The actual behavior and e…

No functional change to validation logicNo change to cryptographic operationsNo change to error messages or user-facing behavior
28380dacby Adam Tucker+57−384 files
No security note in commit
Open full analysis →Source commit ↗
Moderate 60 AI analysisMessage 60 · Adequate
LDK Lightning Dev Kitrust-lightning BitcoinCryptographic librariesLightning Network

Check metadata length for bolt11 invoices

This commit fixes a missing length check when creating BOLT11 Lightning invoices. Before the fix, a user or attacker could supply payment metadata longer than the 639-byte BOLT11 limit, producing an invoice that violates the protocol and m…

Missing input validation on BOLT11 invoice metadata lengthProtocol compliance violation: tagged field exceeds 639-byte BOLT11 limitNew error variant CreationError::PaymentMetadataTooLong introduced
87ea15c3by elnosh+19−31 file
No security note in commit
Open full analysis →Source commit ↗
Moderate 59 AI analysisMessage 68 · Adequate
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

Add Ironwood PCZT support

This commit adds support for a new Zcash transaction format called Ironwood PCZT to the Keystone hardware wallet firmware. It also hardens the wallet against several real attack scenarios: legacy code paths now refuse to handle the new for…

Rejects legacy code paths for v6/Ironwood PCZTs to prevent mis-handlingBlocks internal-OVK change-spoofing attack in parse and check pathsRejects empty Sapling bundle with non-zero value_sum before signing
c28575beby Adam Tucker+2036−2709 files
Vendor flagged security relevance
Open full analysis →Source commit ↗
Low 27 AI analysisMessage 83 · Strong
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

Bump Zcash deps to Ironwood revisions + mechanical API migrations

This commit updates the Zcash-related Rust libraries inside the Keystone 3 firmware to newer versions. It also makes small code changes so the firmware keeps compiling with the new library APIs, removes some old tests that no longer work w…

Dependency bump to major new revisions of Zcash cryptographic cratesSwitch from crates.io releases to Git-pinned forks (valargroup/librustzcash and zcash/orchard)ZIP-244 sighash digest code changes in pczt_ext.rs
4487747fby Adam Tucker+201−43710 files
No security note in commit
Open full analysis →Source commit ↗
Informational 14 AI analysisMessage 83 · Strong
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

Refactor PCZT handling: extract shared helpers (no dependency changes)

This commit is a pure internal code reorganization (refactor) for Zcash PCZT handling. It moves helper functions around, renames some UI rendering code, and adds a shared PCZT parsing helper, but the commit message and diff show no intenti…

bd1298f6by Adam Tucker+229−1524 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 70 · Adequate
LDK Lightning Dev Kitrust-lightning BitcoinCryptographic librariesLightning Network

Fix stable clippy string repeat lint

This commit only changes three lines inside test code to use a different, clippy-preferred way of repeating a string. It does not touch any production logic, network handling, cryptography, or wallet code. There is no security relevance.

999ab2dbby Joost Jager+3−31 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 35 · Opaque
LDK Lightning Dev Kitrust-lightning BitcoinCryptographic librariesLightning Network

Drop duplicate Hasher import

This commit removes a duplicate import of the `Hasher` trait in a Rust source file. It is a code cleanup change with no functional or security effect. The `Hasher` symbol was already imported elsewhere in the same scope, so the duplicate i…

b4f74165by Abeeujah+1−11 file
No security note in commit
Open full analysis →Source commit ↗
Moderate 58 AI analysisMessage 62 · Adequate
LL Lightning LabsLND BitcoinLightning Network

docs: add release note for DNS fallback SRV lookup panic fix

This commit only adds a release note describing a previously fixed bug in LND's DNS fallback code. The actual code fix is not shown in this commit. The bug could crash the LND daemon (a panic) if a DNS response contained unexpected record …

Denial of Service via daemon panicUnsafe type assertion in DNS SRV lookupOut-of-bounds index access on empty lookup result
2ee49698by Erick Cestari+6−01 file
Vendor flagged security relevance
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 →