Scan git repositories and local filesystems for leaked credentials and secrets.
npx skills add https://github.com/zachmayer/skills --skill trufflehog-zachmayer
Please help me install this Agent Skill. Skill: trufflehog Source: https://github.com/zachmayer/skills/tree/main/.claude/skills/trufflehog Command: npx skills add https://github.com/zachmayer/skills --skill trufflehog-zachmayer
This skill identifies hardcoded credentials, API keys, and sensitive secrets hidden within your codebase, preventing accidental exposure and security breaches.
Use the trufflehog skill to scan the current directory for any verified leaked secrets and output the results in json format.
High-intent search queries and answers about installing and using this skill.
To scan git history for leaked secrets, you can run a deep history scan across local repositories and filesystems. This process identifies hardcoded credentials and verifies them against provider APIs to confirm if they are active.
Auditing a remote GitHub organization for exposed API keys requires scanning the organization's repositories directly. This approach detects leaked credentials across the remote infrastructure and verifies findings against provider APIs.
Yes, you need the TruffleHog binary installed and accessible in your system path to scan local filesystems for sensitive data. The binary handles the execution required to detect and verify hardcoded secrets within your directories.
Credential verification works by validating detected secrets against provider APIs to confirm if a credential is live and active. This mechanism ensures you only act on verified leaked credentials, preventing accidental exposure and reducing false positives.
Yes, you can scan full git history for database passwords before pushing code to a public repository. Deep history scanning identifies sensitive secrets hidden in previous commits, ensuring no hardcoded credentials are accidentally exposed.
balsm-healthAutomate hardcoded secret detection in CI/CD pipelines with gitleaks and trufflehog.
drvossDetect hardcoded API keys, tokens, and passwords in source code and git history.
QuintenpsScan staged files for regex-defined secret patterns before git commits.
salmanabdurrahmanDetect hardcoded credentials and sensitive tokens in source code and Git history.
