sc-secrets

Detect hardcoded secrets and credentials in source code repositories.

56|5|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/ersinkoc/security-check --skill sc-secrets
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sc-secrets
Source: https://github.com/ersinkoc/security-check/tree/main/skills/sc-secrets
Command: npx skills add https://github.com/ersinkoc/security-check --skill sc-secrets

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Hardcoded secrets and credentials in source code pose serious security risks, and teams need automated detection to prevent leaks across repositories.

Core Features & Use Cases

  • Pattern-based detection for API keys, tokens, and credentials across languages.
  • High-entropy string detection and private-key recognition to catch unknown secrets.
  • Distinguishes production secrets from test or placeholder values and guides remediation.

Quick Start

Scan your repository to identify and surface hardcoded secrets and private keys.

Frequently Asked Questions about sc-secrets

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

FAQPage Schema
How do I detect hardcoded secrets and credentials in my code repository?

Detect hardcoded secrets by scanning source code, configuration files, and environment files using pattern matching for known key formats and entropy analysis for unknown values. This process identifies API keys, tokens, and private keys embedded across multiple languages during development and code review.

What is the best way to scan for unknown API keys and high-entropy strings?

Scanning for unknown API keys relies on high-entropy string detection and private-key recognition rather than predefined formats alone. Entropy analysis evaluates string randomness to catch undocumented credentials, while context checks distinguish actual production secrets from test placeholders.

Can I use secret detection to differentiate test keys from production credentials?

Secret detection differentiates test keys from production credentials by applying context checks alongside pattern matching. It evaluates the surrounding code structure to distinguish placeholder values from live secrets, ensuring accurate security reviews without false positives on mock data.

Does static analysis for hardcoded secrets work across multiple programming languages?

Static analysis for hardcoded secrets works across multiple languages and file types by scanning repositories, configuration files, and environment files. It applies pattern matching and entropy analysis universally to detect exposed credentials regardless of the underlying programming language.

How do I integrate secret detection into CI pipelines and code reviews?

Integrate secret detection into CI pipelines and code reviews by scanning repositories during automated development workflows. This surfaces hardcoded secrets and private keys before deployment, providing remediation guidance to remove credentials from configuration and environment files.

What remediation guidance is provided when hardcoded secrets are found?

Remediation guidance directs developers to remove identified hardcoded secrets from source code and configuration files. It distinguishes production secrets from test values, helping teams securely manage credentials and patch exposed API keys or tokens found during repository scans.