Add re-export for primitives to Bitcoin crate
What changed, and why it matters
This commit simply makes an existing internal crate called `primitives` usable directly through the main `bitcoin` crate (e.g., `use bitcoin::primitives`). It is a routine API/export convenience change with no security relevance visible in the code.
No security action needed. Review as normal API/export change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff adds one line in bitcoin/src/lib.rs: pub extern crate primitives;. This re-exports the primitives dependency so downstream users can reference it via bitcoin::primitives instead of depending on the separate crate. No logic, parsing, cryptography, or unsafe code is changed.
Changed components
bitcoin/src/lib.rsInspect captured patch +3 / −0
diff --git a/bitcoin/src/lib.rs b/bitcoin/src/lib.rs
index 06b3c405..1f681c94 100644
--- a/bitcoin/src/lib.rs
+++ b/bitcoin/src/lib.rs
@@ -74,6 +74,9 @@ pub extern crate hex;
/// Re-export the `bitcoin-io` crate.
pub extern crate io;
+/// Re-export the `primitives` crate.
+pub extern crate primitives;
+
/// Re-export the `rust-secp256k1` crate.
///
/// Rust wrapper library for Pieter Wuille's libsecp256k1. Implements ECDSA and BIP-0340 signatures
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.