Lib.rs

› Cryptography › Bdrck
#unsafe-bindings #libsodium #stable #branch #security #upstream #full

sys halite-sys

Unsafe Rust bindings for libsodium stable

by Axel Rasmussen

13 releases

0.1.12 Aug 5, 2024
0.1.11 May 28, 2024
0.1.10 Apr 30, 2024
0.1.9 Mar 2, 2024
0.1.1 Jun 7, 2022

#956 in Cryptography

Download history 8/week @ 2024-08-26 13/week @ 2024-09-16 26/week @ 2024-09-23 8/week @ 2024-09-30 1/week @ 2024-10-07 1/week @ 2024-10-14 6/week @ 2024-11-04 1/week @ 2024-11-18 107/week @ 2024-12-02

108 downloads per month
Used in 3 crates (via bdrck)

Apache-2.0

5.5MB
63K SLoC

C 36K SLoC // 0.0% comments Shell 9K SLoC // 0.2% comments M4 8K SLoC // 0.2% comments Visual Studio Project 3.5K SLoC GNU Style Assembly 3K SLoC // 0.0% comments Automake 1K SLoC Pan 520 SLoC Visual Studio Solution 418 SLoC Zig 253 SLoC // 0.0% comments Python 209 SLoC // 0.0% comments Batch 178 SLoC // 0.0% comments Rust 117 SLoC // 0.0% comments C# 35 SLoC Bitbake 22 SLoC VBScript 11 SLoC

Contains (autotools obfuscated code, 695KB) libsodium/configure, (obscure autoconf code, 33KB) libsodium/configure.ac

halite-sys

halite-sys provides unsafe Rust bindings for libsodium.

This crate tracks upstream's stable branch. In general, upstream appears to publish fixes to this branch regularly, whereas new full release versions aren't released very frequently. In general, tracking this branch seems reasonable based on the documentation describing it.

Why not use libsodium-sys or sodiumoxide? Because those crates are deprecated. Further, those crates have known security vulnerabilities.

No runtime deps