integrity-check

A system integrity checker for verifying script and configuration files

Version: 9.8.4 (build 319) | Size: 3.6MB | Author: Warith Al Maawali

License: Proprietary | Website: https://digi77.com

File Information

Property	Value
Binary Name	integrity-check
Version	9.8.4 (build 319)
Build Date	REDACTED-BUILD-TIME
Rust Version	1.82.0
File Size	3.6MB
Author	Warith Al Maawali
License	Proprietary
Category	Kodachi Binary
Description	A system integrity checker for verifying script and configuration files
Git Commit	unknown
Metadata Generated	2026-06-28T11:16:27Z
Binary Timestamp	Unknown
JSON Data	View Raw JSON

SHA256 Checksum

58a32691ed45489f600c95f33c2904abd6da0df53ff8754d65379bfd7b7dccbf

Features

#	Feature
1	File integrity verification using SHA-256 hashes
2	Cryptographic signature verification
3	Version checking against remote repositories
4	Configuration file validation
5	Offline mode support
6	Comprehensive logging and reporting

Security Features

Feature	Description
Authentication	Certificate pinning for secure connections
Encryption	TLS 1.3 for all network communications
Input Validation	All inputs validated and sanitized
Rate Limiting	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\|json) [default: text]
`--base-dir <DIR>`	Base directory for the application
`-V, --verbosity <LEVEL>`	Verbosity level (0-3) [default: 1]
`--log-level <LEVEL>`	Logging level (error\|warn\|info\|debug\|trace)
`--no-network`	Disable network operations
`--strict`	Enable strict validation mode

Commands

Integrity Operations

`check-integrity`

Verify file integrity for scripts, binaries, and configs

Usage:

integrity-check check-integrity [OPTIONS]

Examples:

integrity-check check-integrity

integrity-check check-integrity --json

`generate`

Generate new hash file for all tracked files

Usage:

integrity-check generate [OPTIONS]

Examples:

integrity-check generate

integrity-check generate --json

`check-signatures`

Verify cryptographic signatures of tracked files

Usage:

integrity-check check-signatures [OPTIONS]

Examples:

integrity-check check-signatures

integrity-check check-signatures --json

Verification Operations

`check-version`

Compare local package versions against remote repositories

Usage:

integrity-check check-version [OPTIONS]

Examples:

integrity-check check-version

integrity-check check-version --json

`check-config`

Verify the integrity and format of configuration files

Usage:

integrity-check check-config [OPTIONS]

Examples:

integrity-check check-config

integrity-check check-config --json

`check-all`

Perform comprehensive check including integrity, versions, and signatures

Usage:

integrity-check check-all [OPTIONS]

Examples:

integrity-check check-all

integrity-check check-all --json

Utility Operations

`view-logs`

Display the most recent integrity check logs

Usage:

integrity-check view-logs [OPTIONS]

Examples:

integrity-check view-logs

integrity-check view-logs --json

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

integrity-check check-integrity

Expected Output: Shows pass/fail status for each file

Step 2: Integrity check with JSON output

integrity-check check-integrity --json

Expected Output: JSON response with detailed results

Step 3: Check integrity using custom base directory

integrity-check check-integrity --base-dir /path/to/custom/dir

Expected Output: Integrity results for custom location

Step 4: Custom directory check with JSON output

integrity-check check-integrity --base-dir /path/to/custom/dir --json

Expected Output: JSON results for custom location

Scenario 2: Comprehensive System Checks

Advanced multi-component verification

Step 1: Complete system verification

sudo integrity-check check-all

Expected Output: Full system verification report

Step 2: Full system verification with extended timeout

sudo integrity-check check-all --timeout 300

Expected Output: Comprehensive system check

Note

For thorough system checks

Scenario 3: Hash Generation

Creating and managing file integrity hashes

Step 1: Create new hash file for all tracked files

sudo integrity-check generate

Expected Output: Hash database created/updated

Note

Run after system updates

Step 2: Hash generation with JSON output for automation

sudo integrity-check generate --json

Expected Output: JSON response with generation status

Scenario 4: Version Checking

Package version verification against remote repositories

Step 1: Compare local package versions against remote repositories

integrity-check check-version

Expected Output: Version comparison results

Step 2: Version check with JSON output for scripting

integrity-check check-version --json

Expected Output: JSON response with version data

Scenario 5: Configuration Management

Configuration file verification and validation

Step 1: Verify the integrity and format of configuration files

integrity-check check-config

Expected Output: Configuration validation results

Step 2: Configuration check with JSON output

integrity-check check-config --json

Expected Output: JSON configuration status

Scenario 6: Signature Verification

Cryptographic signature validation

Step 1: Verify cryptographic signatures of tracked files

sudo integrity-check check-signatures

Expected Output: Signature verification results

Step 2: Signature verification with JSON output

sudo integrity-check check-signatures --json

Expected Output: Structured signature status data

Step 3: Strict signature verification

sudo integrity-check check-signatures --strict

Expected Output: Cryptographic verification results

Note

Fails on any signature mismatch

Scenario 7: Log Management

Viewing and managing integrity check logs

Step 1: Display the most recent integrity check logs

integrity-check view-logs

Expected Output: Recent log entries

Step 2: View logs in JSON format for parsing

integrity-check view-logs --json

Expected Output: Structured log data

Note

Useful for log analysis tools

Environment Variables

Variable	Description	Default	Values
`RUST_LOG`	Set logging level	info	error\|warn\|info\|debug\|trace
`NO_COLOR`	Disable all colored output when set	unset	1\|true\|yes (any value disables color)
`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