loose-config-search

To detect dotfiles drift, compare your live system configuration files against the dotfiles MANIFEST by performing diffs to flag differences and identify untracked changes. This process surfaces missing sources and untracked edits across common config locations.

Find untracked configuration files by scanning common locations like ~/.config and home dotfiles, then comparing them against your MANIFEST. This discovery process locates user-edited files that are not included in the manifest and should be backed up.

Dotfiles drift occurs when live configuration files diverge from their tracked sources in the MANIFEST. You need to check for drift when you want to identify untracked edits, missing sources, or configuration differences that should be backed up.

Yes, you can check .gitignore and .gitattributes for secrets during config management. The process performs guardrail checks to highlight gaps in how these files handle sensitive data, ensuring your structured report exposes vulnerabilities without leaking private data.

Yes, loose-config-search works with Git and GitHub configuration files. It applies drift detection and untracked config discovery to common config locations, including home dotfiles, ~/.config, and Git/GitHub configurations, comparing them against the MANIFEST.

Generate a drift report without leaking private data by comparing live configs against the MANIFEST and exposing a structured report. The report lists items by status, including drift, untracked files, and guardrail gaps, while ensuring sensitive information is not leaked.