integrity-check
A system integrity checker for verifying script and configuration files
Version: 9.0.1 | Size: 3.2MB | Author: Warith Al Maawali
License: Proprietary | Website: https://digi77.com
File Information
| Property | Value |
|---|---|
| Binary Name | integrity-check |
| Version | 9.0.1 |
| Build Date | 2026-03-23T08:26:01.259288326Z |
| Rust Version | 1.82.0 |
| File Size | 3.2MB |
| JSON Data | View Raw JSON |
SHA256 Checksum
Features
| Feature | Description |
|---|---|
| Feature | File integrity verification using SHA-256 hashes |
| Feature | Cryptographic signature verification |
| Feature | Version checking against remote repositories |
| Feature | Configuration file validation |
| Feature | Offline mode support |
| Feature | Comprehensive logging and reporting |
Security Features
| Feature | Description |
|---|---|
| Authentication | Certificate pinning for secure connections |
| Encryption | TLS 1.3 for all network communications |
| Inputvalidation | All inputs validated and sanitized |
| Ratelimiting | Maximum 3 retries with configurable timeouts |
System Requirements
| Requirement | Value |
|---|---|
| OS | Linux (Debian-based) |
| Privileges | sudo only for 'generate' and 'check-signatures' commands |
| Dependencies | OpenSSL, curl |
Global Options
| Flag | Description |
|---|---|
-h, --help |
Print help information |
-v, --version |
Print version information |
-n, --info |
Display detailed information |
-e, --examples |
Show usage examples |
--json |
Output in JSON format |
--json-pretty |
Pretty-print JSON output |
--json-filter <FIELDS> |
Filter JSON output fields |
--verbose |
Enable verbose output |
--quiet |
Suppress non-essential output |
--no-color |
Disable colored output |
--config <FILE> |
Use custom configuration file |
--timeout <SECS> |
Set timeout (default: 30) |
--retry <COUNT> |
Retry attempts (default: 3) |
--max-retries <COUNT> |
Maximum retry attempts (0-10) [default: 3] |
-o, --output-format <FORMAT> |
Output format (text |
--base-dir <DIR> |
Base directory for the application |
-V, --verbosity <LEVEL> |
Verbosity level (0-3) [default: 1] |
--log-level <LEVEL> |
Logging level (error |
--no-network |
Disable network operations |
--strict |
Enable strict validation mode |
Commands
Integrity Operations
check-integrity
Verify file integrity for scripts, binaries, and configs
Usage:
Examples:
generate
Generate new hash file for all tracked files
Usage:
Examples:
check-signatures
Verify cryptographic signatures of tracked files
Usage:
Examples:
Verification Operations
check-version
Compare local package versions against remote repositories
Usage:
Examples:
check-config
Verify the integrity and format of configuration files
Usage:
Examples:
check-all
Perform comprehensive check including integrity, versions, and signatures
Usage:
Examples:
Utility Operations
view-logs
Display the most recent integrity check logs
Usage:
Examples:
Operational Scenarios
Scenario-oriented workflows generated from the binary's built-in -e --json examples.
Scenario 1: Basic Usage
Core integrity checking operations
Step 1: Verify integrity of all tracked files
Expected Output: Shows pass/fail status for each fileStep 2: Integrity check with JSON output
Expected Output: JSON response with detailed resultsStep 3: Check integrity using custom base directory
Expected Output: Integrity results for custom locationStep 4: Custom directory check with JSON output
Expected Output: JSON results for custom locationScenario 2: Comprehensive System Checks
Advanced multi-component verification
Step 1: Complete system verification
Expected Output: Full system verification reportStep 2: Full system verification with extended timeout
Expected Output: Comprehensive system checkNote
For thorough system checks
Scenario 3: Hash Generation
Creating and managing file integrity hashes
Step 1: Create new hash file for all tracked files
Expected Output: Hash database created/updatedNote
Run after system updates
Step 2: Hash generation with JSON output for automation
Expected Output: JSON response with generation statusScenario 4: Version Checking
Package version verification against remote repositories
Step 1: Compare local package versions against remote repositories
Expected Output: Version comparison resultsStep 2: Version check with JSON output for scripting
Expected Output: JSON response with version dataScenario 5: Configuration Management
Configuration file verification and validation
Step 1: Verify the integrity and format of configuration files
Expected Output: Configuration validation resultsStep 2: Configuration check with JSON output
Expected Output: JSON configuration statusScenario 6: Signature Verification
Cryptographic signature validation
Step 1: Verify cryptographic signatures of tracked files
Expected Output: Signature verification resultsStep 2: Signature verification with JSON output
Expected Output: Structured signature status dataStep 3: Strict signature verification
Expected Output: Cryptographic verification resultsNote
Fails on any signature mismatch
Scenario 7: Log Management
Viewing and managing integrity check logs
Step 1: Display the most recent integrity check logs
Expected Output: Recent log entriesStep 2: View logs in JSON format for parsing
Expected Output: Structured log dataNote
Useful for log analysis tools
Environment Variables
| Variable | Description | Default | Values |
|---|---|---|---|
RUST_LOG |
Set logging level | info | error |
NO_COLOR |
Disable all colored output when set | unset | 1 |
HTTP_PROXY |
HTTP proxy for network requests | unset | http://proxy:port |
HTTPS_PROXY |
HTTPS proxy for secure requests | unset | https://proxy:port |
Exit Codes
| Code | Description |
|---|---|
| 0 | Success |
| 1 | General error |
| 10 | Check failure - integrity/version issues found |
| 2 | Invalid arguments |
| 3 | Permission denied |
| 4 | Network error |
| 5 | File not found |
| 6 | Timeout error |
| 7 | Authentication error |
| 8 | Internal error |
| 9 | Validation error |