Improve the collector with evidence.
Contributions are welcome for parsers/readers, profiles, deployment safety, performance, test coverage, and documentation.
Development loop
PowerShell · Administrator for profile inspection
git clone https://github.com/abaghinyan/Aralez.git
cd Aralez
cargo fmt --check
cargo check
cargo build
# Inspect the profile produced by your build
target\debug\aralez.exe --show_configbash
git clone https://github.com/abaghinyan/Aralez.git
cd Aralez
cargo fmt --check
cargo check
cargo build
# Inspect the profile produced by your build
sudo target/debug/aralez --show_configContribution expectations
- ✓Explain forensic value. State which investigative question or evidence gap the change addresses.
- ✓Describe endpoint impact. Include I/O, execution, memory, permissions, time, and data-volume implications.
- ✓Cover platform boundaries. Gate OS-specific code and verify compilation for affected targets.
- ✓Test failure paths. Include unavailable tools, unreadable files, interrupts, size limits, full disks, and failed delivery.
- ✓Document profile changes. Identify sensitive new data categories and safe defaults.
Project links
License
Aralez is licensed under the Apache License, Version 2.0. Retain required notices and review third-party tool licenses separately when redistributing a binary that embeds them.
Documentation provenance
This site was derived from the v0.11.0 source, configuration templates, README.md, and deploy/DEPLOYMENT.md. Where marketing text and implementation differ, the implementation behavior is documented.
You’re readyCollect a test endpoint→