smart-secrets-scanner
Intelligent secrets detection — scan code, configs, and git history for exposed API keys, passwords, tokens, and credentials before they leak.
Skill Metadata
- Slug: smart-secrets-scanner
- Version: 1.0.0
- Description: Intelligent secrets and credential scanner for codebases. Detects exposed API keys, passwords, tokens, private keys, and credentials in source code, config files, environment variables, and git commit history. Provides auto-remediation suggestions.
- Category: security
- Trigger Keywords:
secrets scanner, credential leak, API key detection, token exposure, security scan, secret detection, git secret
Capabilities
1. Scan Current Project
```bash
node scanner.js scan ./src
node scanner.js scan ./ --include ".js,.json,.yaml,.env*"
```
Detects 50+ patterns: AWS keys, GitHub tokens, Slack webhooks, database URLs, private keys, JWTs, etc.
2. Scan Git History
```bash
node scanner.js git-scan --depth 50
node scanner.js git-scan --since "2024-01-01"
```
Finds secrets that were committed and later removed (still in git history).
3. Pre-commit Hook
```bash
node scanner.js hook --install
Now every commit is scanned automatically
```
4. Auto-Redact
```bash
node scanner.js redact ./src/config.js --replace-with "[REDACTED]"
```
Replace detected secrets with placeholder values.
Detection Patterns
| Category |
Examples |
| Cloud Keys |
AWS_ACCESS_KEY, GCP_SERVICE_ACCOUNT, AZURE_CLIENT_SECRET |
| API Tokens |
GitHub, Slack, Stripe, OpenAI, Anthropic, Google Maps |
| Database |
MongoDB URI, PostgreSQL URL, Redis password |
| Crypto |
RSA private key, SSH key, certificate |
| App Secrets |
JWT secret, session key, encryption key |
| Config Files |
.env, .npmrc, .pypirc, credentials.json |
Use Cases
- CI/CD Pipeline: Block deployments with exposed secrets
- Pre-commit: Prevent secrets from entering git history
- Audit: Scan existing codebase for leaked credentials
- Compliance: SOC2, GDPR requirement for credential management
- Education: Teach developers about secret management
Output Format
```json
{
"findings": [
{
"file": "src/config.js",
"line": 12,
"type": "AWS_ACCESS_KEY",
"severity": "CRITICAL",
"matched": "AKIAIOSFODNN7EXAMPLE",
"suggestion": "Move to environment variable or secrets manager"
}
],
"summary": { "critical": 1, "high": 0, "medium": 2, "low": 5 }
}
```
1---2name: smart-secrets-scanner3description: Intelligent secrets detection and prevention — scan code, configs, and git history for exposed API keys, passwords, tokens, and credentials4---56# smart-secrets-scanner78> Intelligent secrets detection — scan code, configs, and git history for exposed API keys, passwords, tokens, and credentials before they leak.910## Skill Metadata1112- **Slug**: smart-secrets-scanner13- **Version**: 1.0.014- **Description**: Intelligent secrets and credential scanner for codebases. Detects exposed API keys, passwords, tokens, private keys, and credentials in source code, config files, environment variables, and git commit history. Provides auto-remediation suggestions.15- **Category**: security16- **Trigger Keywords**: `secrets scanner`, `credential leak`, `API key detection`, `token exposure`, `security scan`, `secret detection`, `git secret`1718---1920## Capabilities2122### 1. Scan Current Project23\`\`\`bash24node scanner.js scan ./src25node scanner.js scan ./ --include "*.js,*.json,*.yaml,*.env*"26\`\`\`27Detects 50+ patterns: AWS keys, GitHub tokens, Slack webhooks, database URLs, private keys, JWTs, etc.2829### 2. Scan Git History30\`\`\`bash31node scanner.js git-scan --depth 5032node scanner.js git-scan --since "2024-01-01"33\`\`\`34Finds secrets that were committed and later removed (still in git history).3536### 3. Pre-commit Hook37\`\`\`bash38node scanner.js hook --install39# Now every commit is scanned automatically40\`\`\`4142### 4. Auto-Redact43\`\`\`bash44node scanner.js redact ./src/config.js --replace-with "[REDACTED]"45\`\`\`46Replace detected secrets with placeholder values.4748---4950## Detection Patterns5152| Category | Examples |53|----------|----------|54| Cloud Keys | AWS_ACCESS_KEY, GCP_SERVICE_ACCOUNT, AZURE_CLIENT_SECRET |55| API Tokens | GitHub, Slack, Stripe, OpenAI, Anthropic, Google Maps |56| Database | MongoDB URI, PostgreSQL URL, Redis password |57| Crypto | RSA private key, SSH key, certificate |58| App Secrets | JWT secret, session key, encryption key |59| Config Files | .env, .npmrc, .pypirc, credentials.json |6061## Use Cases62631. **CI/CD Pipeline**: Block deployments with exposed secrets642. **Pre-commit**: Prevent secrets from entering git history653. **Audit**: Scan existing codebase for leaked credentials664. **Compliance**: SOC2, GDPR requirement for credential management675. **Education**: Teach developers about secret management6869## Output Format7071\`\`\`json72{73 "findings": [74 {75 "file": "src/config.js",76 "line": 12,77 "type": "AWS_ACCESS_KEY",78 "severity": "CRITICAL",79 "matched": "AKIAIOSFODNN7EXAMPLE",80 "suggestion": "Move to environment variable or secrets manager"81 }82 ],83 "summary": { "critical": 1, "high": 0, "medium": 2, "low": 5 }84}85\`\`\`