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

Changes worth understanding

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

17251 analyses
Highest risk·RSS
Informational 15 AI analysisMessage 55 · Thin
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

add wallet labels import and export unit test

This commit only adds a new unit test file for importing and exporting wallet labels. It does not change any production code, so it cannot introduce a security vulnerability on its own. It is a routine test addition.

0b819994by Craig Raw+262−01 file
No security note in commit
Informational 15 AI analysisMessage 68 · Adequate
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

hashes: implement sha256t::Tag without the macro

This commit is a routine code cleanup in the rust-bitcoin library. It replaces a macro used to define SHA-256 tagged hash identifiers with direct Rust code that does the same thing. The actual hash values and behavior are unchanged; only t…

0131814dby jrakibi+30−133 files
No security note in commit
Informational 16 AI analysisMessage 90 · Strong
BC Bitcoin CoreHardware Wallet Interface BitcoinHardware integrationSoftware wallets

test: pin Trezor T Rust nightly to 2025-04-15

This change only adjusts a test setup script to pin a specific Rust compiler version when building the Trezor T hardware wallet emulator for automated tests. It is a build/test infrastructure fix, not a security patch, and does not change …

eb36bd69by Sjors Provoost+9−61 file
No security note in commit
Informational 15 AI analysisMessage 90 · Strong
LDK Lightning Dev Kitrust-lightning BitcoinCryptographic librariesLightning Network

ci: don't double-assign reviewers, support manual assignment runs

This is a routine update to the project's automated reviewer-assignment workflow. It prevents the bot from accidentally adding a second random reviewer when one is already assigned, and adds a manual trigger so maintainers can request an a…

24651a1aby Matt Corallo+73−91 file
No security note in commit
Informational 18 AI analysisMessage 55 · Thin
LDK Lightning Dev Kitrust-lightning BitcoinCryptographic librariesLightning Network

Fix assign-reviewer's auth by setting the authorized integration audience

This is a one-line fix to a Forgejo workflow that assigns reviewers. The workflow requests a temporary identity token from the CI system so it can call another service. The change adds an explicit audience parameter to that token request, …

OIDC token audience now explicitly scopedCI workflow authentication hardeningNo change to application code or cryptographic logic
055d334dby Matt Corallo+1−11 file
No security note in commit
Informational 15 AI analysisMessage 68 · Adequate
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

fuzz: Remove ConsumeUniValue

This commit removes a fuzz-test helper that built a UniValue from hard-coded constants and replaces it with parsing a UniValue from random fuzz data. It only affects test code and does not change production behavior or fix a security vulne…

9f3e4272by marcofleon+2−143 files
No security note in commit
Informational 15 AI analysisMessage 58 · Thin
RB Rust Bitcoinrust-bitcoin BitcoinCryptographic libraries

consensus_encoding: Add decode_from_hex_with

This commit adds a new public helper function called decode_from_hex_with to a Rust Bitcoin encoding library. It is a pure feature addition that mirrors existing decode helpers and gives callers a way to decode hex strings by specifying a …

b8c3387aby Mitchell Bagot+37−54 files
No security note in commit
Informational 15 AI analysisMessage 72 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

refactor(crypto): rename noise implementation

This commit is a simple rename of the cryptographic module from 'noise' to 'noise_kk1' across file names, function names, constants, and build scripts. No security behavior changes are visible in the diff. It is a code-maintenance refactor…

e70ee580by M1nd3r+524−51911 files
No security note in commit
Low 31 AI analysisMessage 80 · Strong
TZ TrezorTrezor firmware BitcoinHardware wallets

fix(crypto): minor fixes in `noise_kk1`

This commit fixes several minor issues in a cryptographic module used for secure device communication. The changes include preventing undefined behavior when copying from NULL pointers, zeroing out sensitive key material after use, and pro…

NULL pointer guard added around memcpy in encrypt/decryptMissing memzero of sensitive key material added on error pathsReturn value of encrypt() now checked in handshake request handler
1b60dbbfby M1nd3r+15−61 file
Vendor flagged security relevance
Informational 7 AI analysisMessage 62 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

feat(crypto): implement `noise_xxpsk3`

This commit adds a brand-new cryptographic module implementing the Noise_XXpsk3_25519_AESGCM_SHA256 protocol for secure encrypted communication. It is a feature addition with no changelog entry and no accompanying security advisory. The co…

New cryptographic primitive handling static private keys, ephemeral keys, and pre-shared keysAES-GCM nonce construction uses 64-bit counter with 4-byte zero padding; nonce reuse would be catastrophic but current code increments per operation and rejects at NONCE_LIMITNo explicit authentication-tag verification failure path beyond gcm_decrypt_message return check
ad545339by M1nd3r+1231−03 files
No security note in commit
Informational 15 AI analysisMessage 67 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

test(crypto): add tests for `noise_xxpsk3`

This commit only adds new automated tests for an existing cryptographic handshake protocol called noise_xxpsk3. It does not change the actual security code, fix a bug, or introduce a vulnerability. The tests verify that the protocol works …

77196398by M1nd3r+393−01 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