safe-read 0.1.0

Panic-free bounded integer readers over untrusted byte slices — the shared front door for offset/length fields parsed from attacker-controllable forensic images.
Documentation
  • Coverage
  • 100%
    7 out of 7 items documented1 out of 7 items with examples
  • Size
  • Source code size: 18.99 kB This is the summed size of all the files inside the crates.io package for this release.
  • Documentation size: 121.44 kB This is the summed size of all files generated by rustdoc for all configured targets
  • Ø build duration
  • this release: 2s Average build duration of successful builds.
  • all releases: 2s Average build duration of successful builds in releases after 2024-10-23.
  • Links
  • Homepage
  • SecurityRonin/safe-read
    0 0 0
  • crates.io
  • Dependencies
  • Versions
  • Owners
  • h4x0r

safe-read

Crates.io Docs.rs License: Apache-2.0

Panic-free bounded integer readers over untrusted byte slices — the shared front door for every offset/length field parsed from an attacker-controllable forensic image, so each reader crate stops re-deriving its own bounds-checked helpers.

use safe_read::{le_u32, be_u16};

// In range → the value; out of range → 0, never a panic.
assert_eq!(le_u32(&[0x78, 0x56, 0x34, 0x12], 0), 0x1234_5678);
assert_eq!(le_u32(&[1, 2, 3], 0), 0);          // too short
assert_eq!(be_u16(&[1, 2, 3, 4], usize::MAX), 0); // offset overflow

be_u16/be_u32/be_u64 and le_u16/le_u32/le_u64 each read a fixed-width integer at a byte offset, returning 0 when the window is out of range — too short, offset past EOF, or off + width overflowing usize. #![no_std], no dependencies, no unsafe.

Install

[dependencies]
safe-read = "0.1"

Privacy Policy · Terms of Service · © 2026 Security Ronin Ltd