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
16913Commits 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 87 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

test(core): use layout-specific expected `view_all_data` string

This is a minor test-only change. It updates a single test helper to check for different on-screen text depending on which Trezor device screen layout is being used. It does not change any firmware behavior, user-facing functionality, or s…

8ecf0875by Roman Zeyde+8−41 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 95 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

ci: Put space and non-ASCII char in `BASE_BUILD_DIR`

This is a harmless CI (continuous integration) configuration change for Bitcoin Core. It adds a space and a non-ASCII character to a build directory path used only in automated testing, so the test environment exercises how the code handle…

f3f30215by Hennadii Stepanov+3−11 file
No security note in commit
Open full analysis →Source commit ↗
Informational 16 AI analysisMessage 85 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

build: Quote host paths in NSIS installer template

This commit fixes a Windows installer build script so that directory paths containing spaces are properly quoted. It is a build-system reliability fix, not a security vulnerability. There is no indication it can be exploited to attack user…

a7e980afby Hennadii Stepanov+11−111 file
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 87 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

fix(ci): use both runners for HW tests of T2B1 [no changelog]

This commit is a routine GitHub Actions CI configuration fix. It changes which physical hardware test runner is used for one Trezor device model (T2B1) so that both runners are used again. There is no change to firmware code, cryptography,…

3c70d736by Michal Kazda+2−41 file
No security note in commit
Open full analysis →Source commit ↗
Informational 12 AI analysisMessage 67 · Adequate
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

test(zcash): harden v1 PCZT end-to-end coverage

This commit only adds and updates test code for the Zcash PCZT (Partially-Created Zcash Transaction) feature. It hardens end-to-end test coverage for version 1 PCZTs that include both transparent and Orchard shielded inputs/outputs. There …

No production code changesTest-only commitAdds defensive assertions for signature finalization behavior
2c54cb53by Adam Tucker+177−363 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 62 · Adequate
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

refactor(zcash): use shielded pool display directly

This commit is a minor code cleanup in the Zcash shielded-transaction handling code. It removes temporary variables named `pool_label` and instead uses the existing `pool` value directly when building error messages. There is no change to …

9074e087by Adam Tucker+22−334 files
No security note in commit
Open full analysis →Source commit ↗
Informational 15 AI analysisMessage 75 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

fuzz: [refactor] Use 100'000 digit separator in __AFL_LOOP

This commit is a purely cosmetic code cleanup. It changes the number 100000 to 100'000 in a fuzz-testing helper, using a C++ digit separator to make the value easier to read. It does not alter program behavior, logic, or security.

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

fix(zcash): validate transparent PCZT formats

This commit tightens validation for Zcash transaction formats (PCZT) on the Keystone 3 hardware wallet. Previously, the firmware only checked that a transaction was version 6 or higher and not v6 specifically, plus that it had no Sapling o…

Input-validation hardening for transaction parsing/signingExplicit allow-listing of supported (tx_version, version_group_id, orchard_revision) tuplesNew negative test for v6 + Nu6 branch rejection
0d02c355by Adam Tucker+80−22 files
No security note in commit
Open full analysis →Source commit ↗
Informational 19 AI analysisMessage 68 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

p2p: Assume v2transport for addresses from seeds

This change makes Bitcoin Core assume that hard-coded and DNS seed nodes support the newer BIP324 encrypted transport (v2) when first connecting. If the guess is wrong, the software falls back to the older v1 protocol automatically. It is …

Adds NODE_P2P_V2 to assumed service flags for seed-derived addressesFallback to v1 transport exists if the v2 assumption is wrongNo input validation, memory safety, or cryptographic changes
cf0f2aeaby Martin Zumsande+10−22 files
No security note in commit
Open full analysis →Source commit ↗
Informational 21 AI analysisMessage 60 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

fuzz: Avoid dangling prevoutfetch threads after AFL fork

This commit fixes a fuzz-testing-only issue. When Bitcoin Core runs under AFL (a fuzzing tool), it forks the process after setup. Previously, worker threads created during initialization could become 'dangling' after the fork, causing cras…

thread lifecycle issue in test harnessAFL fork-after-initialization incompatibilitynon-determinism/race condition in fuzzing
fae067ecby MarcoFalke+3−11 file
No security note in commit
Open full analysis →Source commit ↗
Informational 12 AI analysisMessage 76 · Adequate
CK CoinkiteCOLDCARD firmware BitcoinHardware wallets

Bump pillow from 12.1.1 to 12.3.0 in /misc/q1font

This is a routine automated update by Dependabot that bumps the Python Pillow image-processing library from version 12.1.1 to 12.3.0 inside a small helper tool used only for font generation. The commit itself does not describe any security…

Dependency version bump of an image-processing library with a history of memory-safety bugsNo security claim, CVE reference, or advisory link supplied in commit or referencesChanged component is an auxiliary build-time font tool, not device firmware
bcc2c382by dependabot[bot]+1−11 file
No security note in commit
Open full analysis →Source commit ↗
Low 33 AI analysisMessage 57 · Thin
CK CoinkiteCOLDCARD firmware BitcoinHardware wallets

fix: can crash if scanner not initialized

This is a small bug-fix in the COLDCARD hardware wallet's battery monitoring code. It prevents a crash that could occur if a background battery check runs before the QR-code scanner module has finished starting up. The change makes the cod…

Null-pointer-like guard added to prevent crash in background taskBackground task (batt_idle_logout) could terminate unexpectedly without the fixCrash in battery/logout logic could affect device availability or user experience
aaab8a78by scgbckbone+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 →