Scope
Static facts read once and cached (OS name and version, CPU model, core counts, CPU features, caches, topology, virtualization, form factor); live readings read fresh on every call with no allocation for single values (memory, swap, uptime, load, disk space, this process's memory and CPU time); caller-owned samplers for values that need two readings (CPU usage, network rates); the boot kit (build info, instance info, process guard); and an opt-in device id derived with a keyed hash, so raw hardware identifiers never leave the library. It does not inspect other processes, change system settings, or run in the background.
The shape of the Tier 1 API, arriving from 0.3.0. Cargo's rename makes the crate sys in your code:
[]
= { = "sys-lib", = "0.2" }
println!; // "Ubuntu 24.04.1 LTS", "macOS 15.1 Sequoia", "Windows 11 Pro"
println!; // "Ubuntu"; "Windows" and "macOS" elsewhere
println!; // "AMD Ryzen 9 7950X"
println!;
println!; // "41.2 GiB of 125.6 GiB"
println!; // "12.4%" (blocks for 100 ms)
let t = traffic?; // download and upload (blocks for 1 s)
let _guard = guard?; // one copy only; safe permissions
The complete planned API, with the version each item arrives in, is in docs/API.md; where every value comes from on each operating system is in docs/SOURCES.md. See dev/PLAN.md for the full scope, what is deliberately left to other crates, and the decision log.
Contributing
See dev/DIRECTIVES.md for engineering standards and the definition of done. Before a PR: cargo fmt --all, cargo clippy --all-targets --all-features -- -D warnings, and cargo test --all-features must be clean.