Every captured commit receives deterministic security triage and a separate communication-quality score. Security candidates and broader second-pass signals receive full-patch Ollama analysis.
Message quality measures whether a commit identifies its scope, purpose, rationale, testing, and supporting references. It does not change the security-severity score.
This commit is a routine version bump from 0.11.1 to 0.12.0 in the project's package metadata files. It changes only the version number strings in Cargo.toml and Cargo.lock. There is no code change, no bug fix, and no security-related cont…
This commit only adds a new section to the RELEASE-NOTES.md file describing version 0.12.0. It lists user-visible changes such as a new indexing dependency, API fixes, a new SECURITY.md file, and routine dependency updates. No program code…
This is an automated patch by Dependabot that updates the 'log' programming library from version 0.4.33 to 0.4.34. The change only updates a version number and cryptographic checksum in the project's dependency lock file. There is no indic…
This commit only adds a SECURITY.md file to the project. It is a documentation-only change that explains the project's security policy and how to report vulnerabilities. No code was changed, and no security vulnerability was fixed or intro…
This is a routine automated patch by Dependabot that updates a single Rust dependency, crossbeam-channel, from version 0.5.15 to 0.5.16. The change only modifies the recorded version and cryptographic checksum in the project's lock file. T…
This is an automated dependency update by Dependabot that bumps the serde_json library from version 1.0.150 to 1.0.151. The change only updates a version number and cryptographic checksum in the project's lock file. There is no indication …
This commit only updates user-facing documentation and a helper shell script for an upcoming release. It changes wording in setup guides, replaces old example output with newer version numbers, and switches the default database directory i…
This is an automated dependency update by Dependabot that bumps the Rust `log` crate from version 0.4.29 to 0.4.33. The change only updates a version number and cryptographic checksum in the project's lock file. There is no indication in t…
This commit simply updates the version of Bitcoin Core used in the project's automated testing environment from a release candidate (31.0rc2) to the final stable release (31.1). It is a routine CI/infrastructure maintenance change with no …
This commit only updates a single line in the installation documentation, changing the recommended minimum version of Bitcoin Core from 0.21+ to 31.0+. There is no code change, no bug fix, and no security patch in the diff itself.
This commit is a routine feature update. It upgrades a dependency called bindex from version 0.1.1 to 0.1.2 and changes the code to pass a configurable REST server URL into the indexing component. There is no indication in the commit that …
This commit fixes broken documentation links. It changes three Markdown links from an incorrect anchor name (binaries.md#cnative-os-packages) to the correct one (binaries.md#native-os-packages). There is no code change and no security rele…
This is an automated dependency update by Dependabot that bumps the serde_json library from version 1.0.149 to 1.0.150. The change only updates a version number and cryptographic checksum in the project's lock file. There is no indication …
This is a routine automated dependency update by Dependabot, bumping the Rust 'bytes' library from version 1.11.0 to 1.11.1. Only the Cargo.lock file changed. There is no indication in the commit of any security fix, bug fix, or behavior c…
This is a routine dependency update by Dependabot that upgrades the jsonrpc library used by the electrs Bitcoin server from version 0.18.0 to 0.20.1. The change also removes an older copy of the base64 library from the dependency tree. Dep…
Dependency version bump of a networking/RPC crateRemoval of an older transitive dependency (base64 0.13.1) in favor of a newer version (base64 0.22.1)No explicit security claim or CVE reference in commit or supplied materials
This is a large refactoring commit that replaces electrs's custom Bitcoin indexing, chain tracking, P2P networking, and RocksDB storage code with a new external library called `bindex`. It removes thousands of lines of in-house code (index…
Large architectural refactor replacing core indexing/storage/networking subsystemsRemoval of in-house P2P Bitcoin protocol implementation (reduced custom network parsing attack surface)Switch from bitcoincore-rpc to direct jsonrpc usage (custom deserialization of RPC responses)
This is an automated patch by Dependabot that updates the 'bitcoin' Rust library used by the electrs project from version 0.32.8 to 0.32.9. Only version and checksum numbers changed in the dependency list; no project source code was modifi…
This is a routine automated dependency update by Dependabot that bumps the 'rayon' Rust library from version 1.11.0 to 1.12.0. The change only updates version numbers in the project's package manifest and lock file. There is no indication …
This commit simply removes a previously added feature: support for Unix domain sockets. It reverts the code back to using only standard TCP network sockets. There is no indication in the commit itself that this is a security fix, and the c…
This commit adds support for Unix domain sockets to the electrs Bitcoin Electrum server. The main security benefit is that administrators can use filesystem permissions to control which local users or processes can connect, instead of rely…
Adds Unix domain socket support, enabling filesystem-permission-based access control for RPC and metrics endpointsIntroduces public_addr option to decouple bound listening address from advertised Electrum server address (relevant for NAT/SSH tunnels)Adds cleanup of Unix socket path on accept-loop termination
Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.
Lower-priorityDocument REST server for 0.12 releaseby Roman Zeyde · d975dd03 · Sep 19, 2026 · 2 filesMessage 45 · ThinTriage 0Details
Commit message · Roman Zeyde
Document REST server for 0.12 release
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
documentation-only discount
AI review queuedRelease 0.12.0by Roman Zeyde · 37501cc4 · Sep 13, 2026 · 2 filesMessage 28 · OpaqueInformational 15Details
Commit message · Roman Zeyde
Release 0.12.0
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
This commit is a routine version bump from 0.11.1 to 0.12.0 in the project's package metadata files. It changes only the version number strings in Cargo.toml and Cargo.lock. There is no code change, no bug fix, and no security-related content in the diff.
AI review queuedAdd 0.12.0 changelogby Roman Zeyde · 6c763137 · Sep 13, 2026 · 1 fileMessage 38 · OpaqueInformational 15Details
Commit message · Roman Zeyde
Add 0.12.0 changelog
38/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Names a concrete action or component! No meaningful explanatory body
This commit only adds a new section to the RELEASE-NOTES.md file describing version 0.12.0. It lists user-visible changes such as a new indexing dependency, API fixes, a new SECURITY.md file, and routine dependency updates. No program code was changed, so this commit by itself cannot introduce, fix, or exploit a security vulnerability.
Lower-prioritydocs: clarify script-hash status wordingby ginavalent · cd03a757 · Aug 31, 2026 · 1 fileMessage 72 · AdequateTriage 0Details
This is an automated patch by Dependabot that updates the 'log' programming library from version 0.4.33 to 0.4.34. The change only updates a version number and cryptographic checksum in the project's dependency lock file. There is no indication of a security fix or vulnerability in the commit itself, and no security references were provided.
AI review queuedAdd SECURITY.mdby Roman Zeyde · da1860e6 · Aug 29, 2026 · 1 fileMessage 33 · OpaqueInformational 15Details
Commit message · Roman Zeyde
Add SECURITY.md
33/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Names security-relevant behavior explicitly! No meaningful explanatory body
This commit only adds a SECURITY.md file to the project. It is a documentation-only change that explains the project's security policy and how to report vulnerabilities. No code was changed, and no security vulnerability was fixed or introduced.
This is a routine automated patch by Dependabot that updates a single Rust dependency, crossbeam-channel, from version 0.5.15 to 0.5.16. The change only modifies the recorded version and cryptographic checksum in the project's lock file. There is no indication in the commit itself that this update fixes a security vulnerability.
AI review queuedBump serde_json from 1.0.150 to 1.0.151by dependabot[bot] · b69f1a57 · Jul 20, 2026 · 1 fileMessage 76 · AdequateInformational 15Details
Commit message · dependabot[bot]
Bump serde_json from 1.0.150 to 1.0.151
Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.150 to 1.0.151. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.150...v1.0.151)
This is an automated dependency update by Dependabot that bumps the serde_json library from version 1.0.150 to 1.0.151. The change only updates a version number and cryptographic checksum in the project's lock file. There is no indication in the commit itself that this fixes a security issue, and no security references were provided.
Lower-priorityUpdate documentation for the upcoming releaseby Roman Zeyde · 9cd09afa · Jul 18, 2026 · 6 filesMessage 45 · ThinInformational 15Details
Commit message · Roman Zeyde
Update documentation for the upcoming release
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI analysis · Informational 15/100
This commit only updates user-facing documentation and a helper shell script for an upcoming release. It changes wording in setup guides, replaces old example output with newer version numbers, and switches the default database directory in server.sh from ./_db to ./db. There is no code change that fixes or introduces a security vulnerability.
AI review queuedBump log from 0.4.29 to 0.4.33by dependabot[bot] · 9175b0f9 · Jul 18, 2026 · 1 fileMessage 76 · AdequateInformational 15Details
Commit message · dependabot[bot]
Bump log from 0.4.29 to 0.4.33
Bumps [log](https://github.com/rust-lang/log) from 0.4.29 to 0.4.33. - [Release notes](https://github.com/rust-lang/log/releases) - [Changelog](https://github.com/rust-lang/log/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-lang/log/compare/0.4.29...0.4.33)
This is an automated dependency update by Dependabot that bumps the Rust `log` crate from version 0.4.29 to 0.4.33. The change only updates a version number and cryptographic checksum in the project's lock file. There is no indication in the commit of any security fix or vulnerability being addressed, and the `log` crate is a widely-used, stable logging utility. This appears to be a routine maintenance patch with no direct security relevance.
AI review queuedRequire latest bitcoindby Roman Zeyde · c0a4b3fa · Jul 18, 2026 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · Roman Zeyde
Require latest bitcoind
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
This commit only updates a single line in the installation documentation, changing the recommended minimum version of Bitcoin Core from 0.21+ to 31.0+. There is no code change, no bug fix, and no security patch in the diff itself.
Lower-priorityUpdate bitcoind release in CIby Roman Zeyde · eed01b98 · Jul 18, 2026 · 1 fileMessage 45 · ThinInformational 15Details
Commit message · Roman Zeyde
Update bitcoind release in CI
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI analysis · Informational 15/100
This commit simply updates the version of Bitcoin Core used in the project's automated testing environment from a release candidate (31.0rc2) to the final stable release (31.1). It is a routine CI/infrastructure maintenance change with no direct security fix or code change to the electrs software itself.
Lower-priorityAllow setting REST server URLby Roman Zeyde · 1255a377 · Jul 18, 2026 · 3 filesMessage 45 · ThinInformational 11Details
Commit message · Roman Zeyde
Allow setting REST server URL
Requires `bindex` 0.1.2
45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI analysis · Informational 11/100
This commit is a routine feature update. It upgrades a dependency called bindex from version 0.1.1 to 0.1.2 and changes the code to pass a configurable REST server URL into the indexing component. There is no indication in the commit that this fixes a security vulnerability.
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
Why it was queued
documentation-only discount
AI analysis · Informational 15/100
This commit fixes broken documentation links. It changes three Markdown links from an incorrect anchor name (binaries.md#cnative-os-packages) to the correct one (binaries.md#native-os-packages). There is no code change and no security relevance.
AI review queuedBump serde_json from 1.0.149 to 1.0.150by dependabot[bot] · ca254cb5 · Jun 16, 2026 · 1 fileMessage 76 · AdequateInformational 15Details
Commit message · dependabot[bot]
Bump serde_json from 1.0.149 to 1.0.150
Bumps [serde_json](https://github.com/serde-rs/json) from 1.0.149 to 1.0.150. - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](https://github.com/serde-rs/json/compare/v1.0.149...v1.0.150)
This is an automated dependency update by Dependabot that bumps the serde_json library from version 1.0.149 to 1.0.150. The change only updates a version number and cryptographic checksum in the project's lock file. There is no indication in the commit itself that this fixes a security issue, and no security references were provided.
AI review queuedBump bytes from 1.11.0 to 1.11.1by dependabot[bot] · d889624f · Jun 16, 2026 · 1 fileMessage 76 · AdequateInformational 15Details
Commit message · dependabot[bot]
Bump bytes from 1.11.0 to 1.11.1
Bumps [bytes](https://github.com/tokio-rs/bytes) from 1.11.0 to 1.11.1. - [Release notes](https://github.com/tokio-rs/bytes/releases) - [Changelog](https://github.com/tokio-rs/bytes/blob/master/CHANGELOG.md) - [Commits](https://github.com/tokio-rs/bytes/compare/v1.11.0...v1.11.1)
This is a routine automated dependency update by Dependabot, bumping the Rust 'bytes' library from version 1.11.0 to 1.11.1. Only the Cargo.lock file changed. There is no indication in the commit of any security fix, bug fix, or behavior change in electrs itself.
AI review queuedBump jsonrpc from 0.18.0 to 0.20.1by dependabot[bot] · acf4b98d · Jun 15, 2026 · 2 filesMessage 76 · AdequateLow 25Details
Commit message · dependabot[bot]
Bump jsonrpc from 0.18.0 to 0.20.1
Bumps [jsonrpc](https://github.com/rust-bitcoin/corepc) from 0.18.0 to 0.20.1. - [Commits](https://github.com/rust-bitcoin/corepc/commits/jsonrpc-0.20.1)
This is a routine dependency update by Dependabot that upgrades the jsonrpc library used by the electrs Bitcoin server from version 0.18.0 to 0.20.1. The change also removes an older copy of the base64 library from the dependency tree. Dependency updates can sometimes fix security bugs, but the commit message itself does not say this update fixes any vulnerability, and no security advisory was provided.
AI review queuedSwitch to `bindex`by Roman Zeyde · 0fe14fdf · May 31, 2026 · 24 filesMessage 28 · OpaqueLow 32Details
Commit message · Roman Zeyde
Switch to `bindex`
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
This is a large refactoring commit that replaces electrs's custom Bitcoin indexing, chain tracking, P2P networking, and RocksDB storage code with a new external library called `bindex`. It removes thousands of lines of in-house code (indexing, chain state, P2P connection, RocksDB wrapper, transaction cache) and switches RPC communication from the `bitcoincore-rpc` crate to direct `jsonrpc` calls. The change is architectural, not a targeted security fix. There is no mention of a vulnerability, CVE, or security issue in the commit message or diff.
AI review queuedBump bitcoin from 0.32.8 to 0.32.9by dependabot[bot] · 32e5944a · May 30, 2026 · 2 filesMessage 76 · AdequateInformational 15Details
Commit message · dependabot[bot]
Bump bitcoin from 0.32.8 to 0.32.9
Bumps [bitcoin](https://github.com/rust-bitcoin/rust-bitcoin) from 0.32.8 to 0.32.9. - [Release notes](https://github.com/rust-bitcoin/rust-bitcoin/releases) - [Changelog](https://github.com/rust-bitcoin/rust-bitcoin/blob/master/CHANGELOG.md) - [Commits](https://github.com/rust-bitcoin/rust-bitcoin/compare/bitcoin-0.32.8...bitcoin-0.32.9)
This is an automated patch by Dependabot that updates the 'bitcoin' Rust library used by the electrs project from version 0.32.8 to 0.32.9. Only version and checksum numbers changed in the dependency list; no project source code was modified. There is no information in the commit or supplied references indicating this update fixes a security problem, so it appears to be a routine maintenance bump.
AI review queuedBump rayon from 1.11.0 to 1.12.0by dependabot[bot] · d81dc35a · May 10, 2026 · 2 filesMessage 76 · AdequateInformational 15Details
Commit message · dependabot[bot]
Bump rayon from 1.11.0 to 1.12.0
Bumps [rayon](https://github.com/rayon-rs/rayon) from 1.11.0 to 1.12.0. - [Changelog](https://github.com/rayon-rs/rayon/blob/main/RELEASES.md) - [Commits](https://github.com/rayon-rs/rayon/compare/rayon-core-v1.11.0...rayon-core-v1.12.0)
This is a routine automated dependency update by Dependabot that bumps the 'rayon' Rust library from version 1.11.0 to 1.12.0. The change only updates version numbers in the project's package manifest and lock file. There is no indication in the commit itself that this update fixes a security problem.
Lower-priorityRevert "Support Unix sockets"by Roman Zeyde · c134d64d · May 10, 2026 · 10 filesMessage 50 · ThinInformational 12Details
Commit message · Roman Zeyde
Revert "Support Unix sockets"
This reverts commit 898e57dcdded9e9a77c6026d2d80d4331489b1d3.
50/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides an explanatory body
AI analysis · Informational 12/100
This commit simply removes a previously added feature: support for Unix domain sockets. It reverts the code back to using only standard TCP network sockets. There is no indication in the commit itself that this is a security fix, and the change does not appear to introduce or remove any vulnerability. It is a feature rollback.
Lower-prioritySupport Unix socketsby Martin Habovstiak · 898e57dc · May 3, 2026 · 10 filesMessage 68 · AdequateLow 29Details
Commit message · Martin Habovstiak
Support Unix sockets
Unix sockets provide better security and performance, so it is natural for electrs to want to support them. Because of how similar they are to TCP sockets the required changes are theoretically small. However, there is no crate I know of that provided the abstract API, so I made one.
I originally only wanted to support electrum RPC but it turns out not having to deal with two sets of `SocketAddr` is easier and it wasn't too difficult. Unix socket was already supported by `tiny_http` via their own abstraction and we have no other dependencies requiring TCP.
Because this also required modifying the logic around publishing the electrum address I added an option to set it explicitly regardless of whether the user is dealing with Unix or TCP socket because having this is useful for TCP too - the user might want to publish a different port number if the port was mapped via NAT or a different address when tunnelled. In theory, this is still not perfect because the same server could be tunnelled multiple times but we don't bother with such edge case until someone requires it.
Another side improvement is reporting if the accept thread ends because of incoming stream ending rather than error. This should never happen but is useful for debugging if it ever does.
68/100 · AdequateMessage clarity
✓ Subject identifies a change✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Names security-relevant behavior explicitly
AI analysis · Low 29/100
This commit adds support for Unix domain sockets to the electrs Bitcoin Electrum server. The main security benefit is that administrators can use filesystem permissions to control which local users or processes can connect, instead of relying solely on TCP network rules. It also lets operators advertise a different public address than the one the server actually binds to, which is useful when tunneling through SSH or NAT. The changes are mostly a feature addition and refactoring; there is no direct evidence in the commit of a fixed vulnerability or exploit.
AI review queuedBump rand from 0.8.5 to 0.8.6by dependabot[bot] · fb1013af · Apr 23, 2026 · 1 fileMessage 81 · StrongInformational 15Details
Commit message · dependabot[bot]
Bump rand from 0.8.5 to 0.8.6
Bumps [rand](https://github.com/rust-random/rand) from 0.8.5 to 0.8.6. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/0.8.6/CHANGELOG.md) - [Commits](https://github.com/rust-random/rand/compare/0.8.5...0.8.6)
This is a routine automated dependency update by Dependabot, bumping the Rust 'rand' crate from version 0.8.5 to 0.8.6 in the project's lock file. There is no indication in the commit itself that this update fixes a security issue or changes any project code. It is a normal maintenance patch.
AI review queuedFix clippy commentby Roman Zeyde · bad9dfdc · Apr 23, 2026 · 1 fileMessage 28 · OpaqueInformational 15Details
Commit message · Roman Zeyde
Fix clippy comment
28/100 · OpaqueMessage clarity
✓ Subject identifies a change! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100
This is a one-line code cleanup that removes an unnecessary `.into_iter()` call. It does not change what the program does, only makes the code slightly simpler and silences a Clippy lint warning. There is no security relevance.