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.

24Projects watched
17533Commits captured
17131AI analyses
88High-risk findings · 30d
The watch feed

Changes worth understanding

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

17131 analyses
Highest risk·RSS
Informational 15 AI analysisMessage 98 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

chore(core/ethereum): drop EIP-7702 delegation support for now

This commit removes support for a new Ethereum transaction type (EIP-7702) from Trezor hardware wallets. It is described by the developers as a temporary revert of a feature that will be re-added later. There is no indication this is a sec…

347c3c4dby PrisionMike+4−2086 files
No security note in commit
Informational 15 AI analysisMessage 80 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

ci: disable Qt build in OpenBSD cross job

This commit changes a single CI (continuous integration) configuration file for an OpenBSD cross-compilation test job. It disables building the Qt GUI library in that specific test job because the build tool llvm-ranlib does not support th…

b0e09511by fanquake+1−11 file
No security note in commit
Informational 17 AI analysisMessage 62 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

fix(xbuild): emit raw deflate for embedded binaries

This is a small build-tooling change in Trezor's firmware build system. It changes how embedded binary files are compressed before being baked into the firmware image: instead of producing standard zlib-wrapped deflate streams, it now prod…

No security framing in commit message or diffChange is in build tooling, not device firmware runtimeNo mention of vulnerability, CVE, researcher, or security issue
427d85cbby cepetr+7−11 file
No security note in commit
Low 25 AI analysisMessage 73 · Adequate
EP Elements ProjectCore Lightning BitcoinLightning Network

crates: update dependencies and upgrade quick-xml, tower-http, and tokio-tungstenite

This commit is a routine update of third-party Rust libraries used by Core Lightning's REST and WebSocket proxy plugins. The author says no code changes were needed. It is not a security patch itself, but keeping dependencies current can p…

Dependency version bumps for network-facing libraries (quick-xml, tower-http, tokio-tungstenite)No application code changes or security-related commit messageNo CVE, advisory, or vendor security disclosure referenced
678ff47dby daywalker90+273−2903 files
No security note in commit
Moderate 57 AI analysisMessage 50 · Thin
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

add the se wipe and reorder the ErasePublicInfo to fix the power lose issue

This commit changes the factory-reset/wipe routine in a Keystone hardware wallet's startup self-check. It replaces one wipe step with a call to wipe the secure element (SE_WipeAll) and moves the 'ErasePublicInfo' step to occur after accoun…

Secure-element wipe added to factory-reset pathFlash/public-info erasure reordered before final system resetCommit message frames change as fixing power-loss-related data-remanence issue
a366addeby aaron+4−21 file
Vendor flagged security relevance
Informational 15 AI analysisMessage 43 · Thin
BT BTCPay ServerBTCPay Server BitcoinLightning NetworkPayment infrastructure

Refactor breadcrumb (#7455)

This commit is a routine user-interface cleanup. It replaces many copies of hand-written breadcrumb navigation HTML across the application with a single shared 'Breadcrumb' view component. There is no security-relevant change here—only the…

eac04593by Nicolas Dorier+229−48547 files
No security note in commit
Low 41 AI analysisMessage 45 · Thin
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

update the string and fix the pages reused

This commit fixes a page-number overlap in the secure-element storage layout and updates a user-facing help string. Previously, the RSA hash page was defined as page 36, which was also used for account status. The change gives the RSA hash…

Secure-element page-number collision fixed (page 36 reused for both account status and RSA primes hash)New dedicated RSA hash pages (39-41) introduced to prevent overlapping storage useUser-facing string clarified to indicate passcode-reset context and device-wipe consequence
11ed27b3by aaron+15−93 files
No security note in commit
Informational 17 AI analysisMessage 72 · Adequate
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

chore: resume Zcash firmware version changes

This commit is a routine feature patch for the Keystone 3 hardware wallet. It resumes adding the device's firmware version into Zcash wallet connection data, and it fixes two simulator-only bugs: a keyboard crash when a text box is destroy…

Use-after-free crash avoided in simulator keyboard event handlerSynchronous simulator async execution replaced with FIFO timer queue to match device semanticsFirmware version added to Zcash account synchronization UR
4518972cby soralit+123−75 files
No security note in commit
Low 40 AI analysisMessage 45 · Thin
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

Clarify cross-pool rk validation

This commit only rewrites a code comment in the Zcash PCZT validation logic. It clarifies why the code checks that certain cryptographic keys are not reused across Orchard and Ironwood 'pools.' The actual validation behavior does not chang…

Comment clarifies defensive validation of distinct randomized validating keys (rk) across Orchard and Ironwood poolsOriginal comment implied a cross-pool signature-replay risk that the new comment says does not existNo executable code change; purely documentation/comment update
e4ab2e4dby Adam Tucker+3−31 file
No security note in commit
Low 31 AI analysisMessage 35 · Opaque
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

Optimize duplicate rk validation

This commit is a small code cleanup in the Zcash part of the Keystone hardware wallet firmware. It changes how the code checks for duplicate 'rk' values across Orchard and Ironwood shielded transaction actions. The old code used chained it…

No security-relevant behavioral change visible in diffFunction still rejects duplicate Orchard/Ironwood action rk valuesRefactoring from iterator-based duplicate detection to vector-based nested loops
15709554by Adam Tucker+11−121 file
No security note in commit
Informational 15 AI analysisMessage 51 · Thin
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

Make ToU64 private

This commit simply changes a Rust helper trait from public to private visibility (pub(crate)). It is a routine API-cleanup change with no security relevance. The trait converts integer sizes to u64 and is no longer needed in any public int…

56b2eff9by Mitchell Bagot+1−11 file
No security note in 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