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

Changes worth understanding

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

17247 analyses
Highest risk·RSS
Informational 21 AI analysisMessage 83 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

rpc: add `vsize_adjusted` and `vsize_bip141` field to mempool-related RPCs

This Bitcoin Core change fixes a labeling problem in several RPC (remote procedure call) responses. The old 'vsize' field was actually reporting a sigop-adjusted size, not the plain BIP 141 virtual size its documentation claimed. The patch…

Deprecated RPC field with corrected documentationNew explicit fields to disambiguate sigop-adjusted vs BIP 141 vsizeNo change to mempool acceptance rules or fee calculation logic
eaef8d31by Musa Haruna+53−155 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 85 · Strong
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

docs(zcash): rename preflight FUTURE marker to omitted-field-recompute

This commit only renames a future-work comment marker in the Zcash code from 'qr-v2-omitted-fields' to 'omitted-field-recompute'. No actual code behavior changes; it is purely a documentation-style edit to avoid confusing terminology. Ther…

0ace2edcby Adam Tucker+4−41 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 45 · Thin
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

style(zcash): rustfmt the checked-PCZT additions

This commit only reformats existing Rust code to match the project's style rules (rustfmt). No behavior, logic, or security properties of the Zcash PCZT handling changed.

a808c11bby Adam Tucker+6−72 files
No security note in commit
Open full analysis →Source commit ↗
Low 27 AI analysisMessage 62 · Adequate
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

refactor(zcash): drop ufvk from sign FFI and retire byte-level postflights

This commit refactors how Keystone's Zcash signing code handles shielded transactions. It removes several old byte-level 'preflight' and 'postflight' checks and no longer passes a full viewing key (ufvk) into the final signing functions. T…

Removal of explicit byte-level postflight signature verification for shielded Zcash actionsRemoval of explicit preflight check that at least one signable shielded action exists before batch signingFFI signature change drops unified full viewing key (ufvk) from signing path
4f0442e6by Adam Tucker+14−2344 files
No security note in commit
Open full analysis →Source commit ↗
Low 31 AI analysisMessage 62 · Adequate
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

feat(zcash): drive batch display/sign from the checked batch container

This commit changes how a Zcash hardware wallet handles batches of transactions. Previously, the signing and display code used the raw, unchecked batch data directly. After the patch, the code first runs a checking function that produces a…

Separation of checked/sanitized transaction container from raw UR inputDisplay and signing paths now both consume the same checked objectAddition of explicit cleanup/free for the checked container
843d4513by Adam Tucker+21−121 file
No security note in commit
Open full analysis →Source commit ↗
Low 32 AI analysisMessage 62 · Adequate
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

refactor(zcash): route batch FFI through per-message checked preflight

This commit rewrites how the Keystone hardware wallet handles Zcash batch transactions. Instead of checking each transaction message separately at every step, it now runs a single 'preflight' check that normalizes the messages, stores the …

Refactor moves security-critical checks from three separate call sites into a single preflight stepNew checked container (ZcashCheckedPczt) binds parsed/signed data to the preflight outputPer-message normalization and digest stamping before signing
a776ed69by Adam Tucker+107−931 file
No security note in commit
Open full analysis →Source commit ↗
Informational 12 AI analysisMessage 62 · Adequate
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

feat(zcash): add batch-policy preflight for checked batch messages

This commit adds a new Rust function for Zcash that pre-checks a batch of private (shielded) transaction data before signing. It is a feature addition with explicit safety checks and tests; the diff itself does not show a vulnerability bei…

New preflight function enforces account ownership and batch policy before signingReuses existing `check_parsed_pczt_cypherpunk` and `signable_shielded_actions` helpersAdds tests for negative cases (wrong account, unsupported Sapling outputs)
1753fe42by Adam Tucker+76−01 file
No security note in commit
Open full analysis →Source commit ↗
Low 26 AI analysisMessage 62 · Adequate
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

feat(zcash): store checked_PCZT in C and drive display/sign from it

This commit refactors how the Keystone hardware wallet handles Zcash transaction data. Previously, the wallet parsed and signed directly from the raw incoming transaction data. Now it first runs a 'check' function that produces a validated…

Refactor to use a single validated intermediate representation for both display and signingAddition of explicit cleanup/free path for the new checked_PCZT objectFunction pointer casts added to align Rust FFI signers with C callback signatures
d88c86ecby Adam Tucker+24−131 file
No security note in commit
Open full analysis →Source commit ↗
Low 32 AI analysisMessage 62 · Adequate
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

refactor(zcash): route single-tx FFI through checked-PCZT preflight/sign

This commit changes how the Keystone hardware wallet handles Zcash transactions. Previously, the wallet checked a transaction and then signed it in separate steps, with the signing step accepting any raw transaction object. Now, the check …

Single Zcash signing and parsing paths now require a checked PCZT object produced by preflightRaw ZcashPczt input removed from sign_zcash_tx, sign_zcash_tx_cypherpunk, and parse_zcash_tx entry pointsNull checks and verified_bytes() validation added before signing/parsing
15f21756by Adam Tucker+103−971 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 57 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

feat(core): add support for U5A5 MCU

This commit adds support for a new microcontroller chip (the STM32U5A5) to the Trezor firmware build system. It is a hardware-enablement change: it wires up the right compiler flags, linker scripts, memory layouts, and trustzone settings s…

6e5a0940by tychovrahe+612−426 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 57 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

feat(core): add mock touch driver

This commit adds a new 'mock' touch driver for Trezor hardware wallets that have no touch screen, such as bare development boards. The driver simply reports 'no touch activity' so the software can compile and run without real touch hardwar…

f0fdf2f1by tychovrahe+74−13 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 57 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

feat(core): aad mock display driver

This commit adds a new optional 'headless' display driver for Trezor hardware that has no screen. It does not change any existing behavior for real devices; it simply lets the firmware compile and run on display-less development boards by …

9a120ec0by tychovrahe+152−03 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 →