hashes: Separate optional dependencies
What the developer wrote
Authored by Tobin C. Harding
hashes: Separate optional dependencies
As is customary around here put a line of whitespace in between
optional and non-optional dependencies.
What changed, and why it matters
This commit only adds a blank line in a package configuration file to visually separate optional dependencies from required ones. There is no code change, no behavior change, and no security relevance.
No action needed; this is a non-functional formatting change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff modifies hashes/Cargo.toml by inserting a single blank line between the required ‘internals’ dependency and the optional ‘hex’ and ‘serde’ dependencies. This is a cosmetic formatting change with no functional or security impact.
Changed components
hashes/Cargo.tomlInspect captured patch +1 / −0
diff --git a/hashes/Cargo.toml b/hashes/Cargo.toml
index 99caab0b..5134e82f 100644
--- a/hashes/Cargo.toml
+++ b/hashes/Cargo.toml
@@ -23,6 +23,7 @@ small-hash = []
[dependencies]
internals = { package = "bitcoin-internals", path = "../internals" }
+
hex = { package = "hex-conservative", version = "0.3.0", default-features = false, optional = true }
serde = { version = "1.0.103", default-features = false, optional = true }
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.