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
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
High 79 AI analysisMessage 35 · Opaque
SW SparrowSparrow Wallet BitcoinHardware integrationSoftware wallets

persistence hardening followup

This commit hardens how Sparrow Wallet opens its encrypted wallet files. It blocks several H2 database features that could be abused to run code or read files when a malicious wallet file is opened, and it prevents Java object deserializat…

H2 database feature hardeningJava deserialization disabledDDL blacklist expansion
aeb0eeb1by Craig Raw+166−212 files
No security note in commit
Informational 15 AI analysisMessage 83 · Strong
BC Bitcoin CoreBitcoin Core BitcoinSupply chain

fuzz: populate wallet TXO index in wallet_create_transaction

This is a fix to a Bitcoin Core fuzz test (an automated testing harness), not to the main wallet code that real users run. The test was inserting fake wallet transactions in a way that skipped updating an internal index called m_txos. Beca…

Test-only change in fuzz harnessFixes internal test-state consistency, not production wallet behaviorNo validation, consensus, or P2P networking changes
1eac6a72by frankomosh+1−01 file
No security note in commit
Informational 15 AI analysisMessage 40 · Thin
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

chore: update change log

This commit only edits the project's changelog text. It rewrites the release notes for version 3.0.2, removing detailed bug-fix descriptions and replacing them with a shorter note about Zcash Ironwood support. No source code, build scripts…

c224a7f5by soralit+12−232 files
No security note in commit
Informational 15 AI analysisMessage 40 · Thin
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

chore: bump version

This commit only changes two version numbers in a header file: the build number is increased from 1 to 2, and the beta flag is turned off (set to 0). There is no code change, no bug fix, and no security-related content in the diff or commi…

62a5d952by soralit+2−21 file
No security note in commit
Low 37 AI analysisMessage 45 · Thin
KS KeystoneKeystone 3 firmware BitcoinHardware wallets

Fix Zcash wallet preparation on unlock

This commit fixes a bug in a helper function that checks whether a text string is a valid hexadecimal value of the expected length. The changelog frames the user-visible fix as 'preventing Zcash public information from being regenerated on…

Input validation hardening in a shared utility functionChangelog describes a Zcash wallet preparation/unlock behavior fixPotential off-by-one length check corrected
dd034199by Adam Tucker+8−44 files
No security note in commit
Informational 15 AI analysisMessage 57 · Thin
TZ TrezorTrezor firmware BitcoinHardware wallets

chore(core): bump version to 2.12.4

This commit is a routine version bump from 2.12.3 to 2.12.4 for the Trezor firmware. It only changes the version number in one header file and updates the same version number in translation files, plus refreshes the translation signature m…

98259629by Martin Milata+10−108 files
No security note in commit
Informational 14 AI analysisMessage 62 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

chore(core): less confusing log message when decoding protobuf

This commit only changes debug log messages and error text when decoding protobuf data. It adds a parameter so internal credential decoding can say 'protobuf' instead of 'message' in logs/errors, making diagnostics less confusing. There is…

bb5133c4by Martin Milata+13−92 files
No security note in commit
Low 37 AI analysisMessage 77 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

fix(core): store packet across session restart during channel preemption

This commit fixes a behavior in Trezor's core firmware where, during a 'channel preemption' (one computer taking over communication with the device from another), the device would send a TRANSPORT_BUSY message and force the new host to res…

Avoids TRANSPORT_BUSY race/retransmission during channel preemptionAdds global mutable buffer for a single in-flight packet across session restartKills active channel with ChannelPreemptedException before storing packet
4367a35aby Martin Milata+140−94 files
No security note in commit
Informational 15 AI analysisMessage 62 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

docs(core): THP synchronization layer clarification

This commit is purely a documentation and log-message wording update. It clarifies which message types participate in the Trezor Host Protocol (THP) synchronization layer, documents how sequence and ACK bits are encoded, and renames 'sync …

74d3b048by Martin Milata+11−63 files
No security note in commit
High 72 AI analysisMessage 77 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

fix(core/bitcoin): Fix external input misidentification.

This update fixes a bug in the Trezor hardware wallet's Bitcoin transaction signing. When a transaction included an external input (someone else's coin) with empty placeholder fields, the device could mistake it for an already-signed input…

Security-relevant bug fix in Bitcoin transaction signingChange from identity comparison to truthiness to handle empty byte fields consistentlyAddition of input sanitization rules for ownership_proof presence
675fa659by Andrew Kozlik+55−45 files
Vendor flagged security relevance
Informational 12 AI analysisMessage 77 · Adequate
TZ TrezorTrezor firmware BitcoinHardware wallets

refactor(core/bitcoin): Consolidate external input classification.

This commit is a code cleanup (refactor) in the Bitcoin signing code of the Trezor firmware. It introduces a helper that classifies external transaction inputs into three categories (presigned, has ownership proof, or unverified) and uses …

No security-relevant behavior change: same input classification conditions are preservedRefactor only: logic moved into a new helper enum/classmethodNo new trust boundaries, no new parsing, no new memory handling
e70633eeby Andrew Kozlik+38−122 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