privacy-review

Scan Git repositories for exposed secrets and sensitive data.

Updated Mar 27, 2022

Search Tags:#git #security #secrets #credentials #privacy #scanning

Ready to run

npx skills add https://github.com/emliunix/home.conf --skill privacy-review

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: privacy-review
Source: https://github.com/emliunix/home.conf/tree/main/skills/privacy-review
Command: npx skills add https://github.com/emliunix/home.conf --skill privacy-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Automated privacy review for git repositories. Scans for sensitive data exposure including API keys, passwords, database credentials, and tokens, helping teams prevent leaks before sharing code.

Core Features & Use Cases

Scans commits for sensitive files and patterns (e.g., .env, private keys) across history and current state.
Verifies .gitignore protections and detects local .env presence to guide safe practices.
Generates structured reports and remediation guidance to support quick cleanup before publishing.

Quick Start

Run privacy_scan.py on a repository to generate a privacy report.

Frequently Asked Questions about privacy-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I scan a Git repository for exposed secrets and credentials?▼

To scan a Git repository for exposed secrets, run privacy_scan.py on your local clone to analyze commit histories and configurations. It flags API keys, passwords, and tokens across commits and environment files, generating a structured report with remediation guidance.

Does this automated privacy check detect sensitive files across the entire commit history?▼

Yes, the automated privacy check scans the entire commit history to detect sensitive files like .env and private keys. It analyzes both historical commits and the current repository state to identify sensitive file patterns and in-code secrets comprehensively.

How do I prevent sensitive data exposure in Git before sharing or deployment?▼

Prevent sensitive data exposure by running privacy checks in CI pipelines before deployment. The scan verifies .gitignore protections, detects local .env presence, and flags in-code secrets, providing structured reports to support quick cleanup before publishing.

Can I integrate secrets scanning into my CI pipelines for Git repositories?▼

Yes, you can integrate this secrets scanning into CI pipelines for Git repositories. It analyzes commits, code content, and environment files during CI, flagging leaks before deployment and providing remediation guidance to prevent sharing exposed credentials.

What is the best way to check if .gitignore protects sensitive files in my repository?▼

The best way to check .gitignore protections is running an automated privacy scan on your repository. It verifies .gitignore rules against sensitive file patterns, detects local .env presence, and generates a structured report highlighting unprotected sensitive data.

What should I do if my Git history contains accidentally committed API keys and tokens?▼

If your Git history contains accidentally committed API keys and tokens, run a privacy scan to identify the exact leaks. It generates a structured report with specific remediation guidance to help you clean up exposed secrets before sharing or deploying the code.