crypto: Add pub extern crate for crates with public api types
What changed, and why it matters
This change simply re-exports a few internal Rust crates through the public API of the `crypto` sub-crate so users don't have to add those dependencies manually. It is a routine dependency-management and API-ergonomics patch with no apparent security relevance.
No security action required; review as normal API-maintenance change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The commit adds pub extern crate re-exports for base58, network, io, and secp256k1 in crypto/src/lib.rs, and removes a doc comment on the existing hex_stable re-export. These are compile-time visibility/dependency-handling changes; no logic, parsing, cryptography, or unsafe code is modified.
Changed components
crypto/src/lib.rsInspect captured patch +8 / −1
diff --git a/crypto/src/lib.rs b/crypto/src/lib.rs
index 1574571c..20a6c692 100644
--- a/crypto/src/lib.rs
+++ b/crypto/src/lib.rs
@@ -15,9 +15,16 @@ extern crate alloc;
#[cfg(feature = "std")]
extern crate std;
-/// Re-export the `hex-conservative` crate.
pub extern crate hex_stable as hex;
+pub extern crate base58;
+
+pub extern crate network;
+
+pub extern crate io;
+
+pub extern crate secp256k1;
+
#[cfg(feature = "alloc")]
pub mod ecdsa;
#[cfg(feature = "alloc")]
Why this scored 16/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.