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.

23Projects watched
16915Commits 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 21 AI analysisMessage 72 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

fix(build): force UV to use nix-provided Python

This commit changes the Trezor firmware build environment so that a Python package tool called 'uv' is forced to use the Python interpreter provided by the Nix build system, rather than silently downloading and using its own. The change pr…

Build environment now pins uv to the Nix-provided Python interpreterDisables uv's automatic Python interpreter downloadsReduces supply-chain risk from externally downloaded build tooling
f07b610cby M1nd3r+6−01 file
No security note in commit
Informational 16 AI analysisMessage 85 · Strong
EP Elements ProjectCore Lightning BitcoinLightning Network

nix: fix `nix build` and simplify NixOS install docs

This commit fixes the Nix package build for Core Lightning so that `nix build` works again. It is a build-system/documentation fix, not a security patch. There is no vulnerability being fixed here.

531673a4by enaples+40−72 files
No security note in commit
Informational 11 AI analysisMessage 80 · Strong
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

build(zcash): use released protocol crates

This commit is a routine build update for the Zcash parts of the Keystone 3 firmware. It switches several Rust libraries from using specific GitHub revisions to using published versions from crates.io, and bumps a few version numbers. Ther…

Dependency source changed from Git revisions to crates.io releasesPre-release Zcash crate versions bumped to stable releasesur-registry pinned to a newer SDK revision
ef5ad05fby Adam Tucker+37−454 files
No security note in commit
Informational 15 AI analysisMessage 85 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

fix(l10n): updating and fixing English strings - fewer versions per different layout - added period in places where it was missing - new description string for PIN reenter on Delizia [no changelog]

This commit only changes user-visible text strings in the Trezor firmware. It updates English translations, removes duplicate layout-specific versions of the same phrase, adds missing periods, and introduces a new description string shown …

42dbc643by Michal Kazda+19−212 files
No security note in commit
Informational 15 AI analysisMessage 72 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

fix(l10n): updated generated files [no changelog]

This commit is a routine refresh of automatically generated translation files. It updates user-facing text strings (for example, changing punctuation or wording of on-screen messages) and adds one new string used during PIN setup. There is…

6ee734adby Michal Kazda+12201−121645 files
No security note in commit
Informational 15 AI analysisMessage 72 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

fix(l10n): updated fixtures [no changelog]

This commit only updates expected test result fingerprints (hashes) in a single test data file. It does not change any firmware, application, or cryptographic code. There is no indication of a security fix or vulnerability being addressed.

27ea3039by Michal Kazda+137−1371 file
No security note in commit
Low 47 AI analysisMessage 80 · Strong
EL ElectrumElectrum BitcoinSoftware wallets

json_db: set_modified after incomplete data

This commit fixes a bug in Electrum's wallet storage recovery. If a wallet file was partially corrupted (a 'patch' was cut off mid-write), the app could recover the old data but then fail to mark the wallet as changed. As a result, later u…

Data-loss / integrity failure in wallet storage recovery pathMissing dirty flag after fallback data recoveryAppend-only storage file not rewritten after corruption cleanup
f75f1958by f321x+22−12 files
No security note in commit
Moderate 59 AI analysisMessage 88 · Strong
EL ElectrumElectrum BitcoinSoftware wallets

json_db: escape '\' and '~' in json patch pointer

This commit fixes a bug in how Electrum builds JSON Patch pointers when wallet data contains special characters like '/' or '~' in keys. Before the fix, these characters were not escaped, which could cause patch operations to target the wr…

Incorrect JSON Pointer escaping can misroute patch operationsPotential data corruption or loss in wallet database updatesNo explicit security framing in commit message or diff
97007d9eby f321x+13−12 files
No security note in commit
Informational 15 AI analysisMessage 57 · Thin
SS SeedSignerSeedSigner BitcoinHardware wallets

refactor: use `Seed` instead of `seed_num`

This commit is a straightforward internal code cleanup: it replaces the use of numeric seed indexes (seed_num) with direct references to Seed objects throughout the user interface and tests. There is no security-relevant change; it is pure…

65e312c9by okaybro+238−2698 files
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