Consent

Security toolkit for managing consent records — generate tokens, check strength, rotate credentials, audit logs, store and retrieve entries, manage policies, and produce compliance reports. All data stays local.

Commands

Command Behavior

• With arguments: Each command logs the input with a timestamp to its own dedicated log file (e.g., generate.log, audit.log)
• Without arguments: Each command displays the 20 most recent entries from its log file

Data Storage

• Default data directory: ~/.local/share/consent/
• Per-command logs: $DATA_DIR/.log (e.g., generate.log, audit.log, store.log)
• History log: $DATA_DIR/history.log — master timeline of all activity
• Export files: $DATA_DIR/export. — generated by the export command
• All data is local plain-text. No network calls, no cloud sync.

Requirements

• Bash 4+ (uses set -euo pipefail)
• No external dependencies or API keys required
• Works entirely offline — your data stays on your machine

When to Use

1. Tracking consent and compliance — Record who consented to what and when with store, audit, and policy for a simple compliance trail
2. Credential rotation logging — Use rotate and expire to log when credentials were changed or invalidated
3. Security auditing — Run audit entries and pull report data to review security posture over time
4. Exporting compliance data — Use export json or export csv to produce machine-readable records for external auditing tools
5. Quick lookups and verification — Search across all logs with search or verify specific entries with verify and hash

Examples

# Store a consent record
consent store "user:alice accepted terms-of-service v2.1"

# Audit a policy change
consent audit "updated data retention policy to 90 days"

# Generate a new token entry
consent generate "api-key-prod-2025"

# Rotate a credential and log it
consent rotate "db-password-main rotated"

# Check strength of a passphrase
consent check-strength "my-complex-passphrase-2025!"

# Export all data as JSON
consent export json

# Search across all logs
consent search "alice"

# View summary statistics
consent stats

# Health check
consent status

# Show recent activity
consent recent

How It Works

Each domain command (generate, audit, store, etc.) maintains its own log file in the data directory. Entries are stored as timestamp|value lines. The stats command aggregates counts across all log files. The export command merges all logs into a single file in your chosen format. Every action is also recorded in history.log as a master audit trail.

Tips

• Run any command without arguments to see its recent entries — great for quick review
• Use consent recent to see a timeline of all activity across all commands
• Pipe exports to other tools: consent export csv && cat ~/.local/share/consent/export.csv | head
• Combine search with grep for complex queries: consent search "2025" | grep "policy"
• Run consent help at any time for the full command reference

Powered by BytesAgain | bytesagain.com | hello@bytesagain.com