fprint-core 0.1.0

Modern, GObject-free Rust core for fingerprint readers: device/print domain model and backend traits, shared by a libfprint (FFI) shim backend and native Rust drivers.
Documentation
  • Coverage
  • 100%
    110 out of 110 items documented2 out of 2 items with examples
  • Size
  • Source code size: 90.0 kB This is the summed size of all the files inside the crates.io package for this release.
  • Documentation size: 2.1 MB This is the summed size of all files generated by rustdoc for all configured targets
  • Ø build duration
  • this release: 6s Average build duration of successful builds.
  • all releases: 6s Average build duration of successful builds in releases after 2024-10-23.
  • Links
  • Homepage
  • P4suta/fprintd
    1 0 5
  • crates.io
  • Dependencies
  • Versions
  • Owners
  • P4suta

fprint-core

The GObject-free core of an fprintd-compatible fingerprint stack: the domain model (fingers, device capabilities, prints/templates) plus the Backend/Device traits a concrete backend implements. Zero dependencies, #![forbid(unsafe_code)]. Both traits are native async fn traits with no dyn and no runtime. It contains no drivers, USB code, or matching algorithms; those live in downstream crates. The daemon depends only on these traits, so a backend can be swapped without touching it.

Quickstart

use fprint_core::{Backend, Device, DeviceId, Error, Result};

struct MyBackend;

impl Backend for MyBackend {
    type Device = MyDevice;
    async fn enumerate(&self) -> Result<Vec<MyDevice>> { /* probe the bus */ }
    async fn open(&self, id: &DeviceId) -> Result<MyDevice> { /* claim a reader */ }
}

// impl Device for MyDevice { open/close/enroll/verify/identify/... }

The crate-root docs carry a complete, compiled Backend + Device implementation that depends on nothing but std.

Links

License

MIT OR Apache-2.0, at your option.