Scan Git repositories for exposed secrets and sensitive data.
npx skills add https://github.com/emliunix/home.conf --skill privacy-review
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
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.
Run privacy_scan.py on a repository to generate a privacy report.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
jtucker9Detect hardcoded secrets in codebases and Git history.
Greenmamba29Scan environment files and codebases for exposed secrets and generate a remediation report.
DevHive1Orchestrate dependency, static analysis, and privacy dataflow scanners into prioritized reports.
yashvinthanManage secrets in CI/CD pipelines with Vault or AWS Secrets Manager.
