Nozomi

A Rust library that wipe all file or folder.
This library includes most of the secure deletion methods of the Eraser for Windows software.

Add to your project

[dependencies]
nozomi = "3.0.3"

Test libraries

Prerequire (optional)

cargo install cargo-nextest

Test

git clone https://github.com/Sans-Atout/Nozomi.git
cd Nozomi
cargo nextest run

Code example

use nozomi::Method::Afssi5020;

fn main() -> Result<(),nozomi::Error> {
    Afssi5020::delete("path/to/file.txt")?;
    // OR
    match Afssi5020::delete("path/to/file.txt"){
        Ok(info) => println!("{}",info), // If you want
        Err(error) => println!("{}",error)
    };

    Ok(())
}

Support

End of life dates

Support life cycle

When a new major version (N) is released, it will become actively supported. Bugs will be fixed and new features will be added (new default deletion algorithm, better documentation, etc.). The library will be audited every week with the cargo audit command to ensure that no flaws persist in the solution.

The previous major version (N-1) will enter in the passive support phase, which will last 5 years. During this period, the library dependencies will be updated every three months to ensure that the project is running as up-to-date as possible. The code will also be audited, but only on a monthly basis with the cargo audit. If a CVE requiring a modification to the library code is discovered, a new minor version will be published.

Once this passive support phase is over, the version will enter in the end-of-life process, which will last 1 year. During this phase, no more dependencies will be updated and no more issues concerning this library will be taken into account. This phase exists to give projects that may use the library additional time to make the necessary changes to their code before moving the version to ‘Yanked’ on crates.io

Features

Changelog

Contributing

Erase Method