secret-scanner

Detect secrets and credentials in source code and configuration files.

5|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/47network/Sven --skill secret-scanner-47network
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: secret-scanner
Source: https://github.com/47network/Sven/tree/main/skills/security/secret-scanner
Command: npx skills add https://github.com/47network/Sven --skill secret-scanner-47network

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detect secrets and credentials in source code and configuration files, preventing leakage across repositories and CI pipelines.

Core Features & Use Cases

  • 20 built-in secret patterns covering AWS, GitHub, Slack, Stripe, database URLs, JWTs, and more.
  • Entropy evaluation to flag high-entropy strings that may be secrets.
  • Actionable outputs with redacted results suitable for reports and remediation.

Quick Start

Scan a set of repository files for secrets and generate a redacted report.

Frequently Asked Questions about secret-scanner

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

FAQPage Schema
How do I detect secrets in source code before they leak?

Detect secrets in source code by scanning repositories and configuration files with 20 built-in patterns covering AWS, GitHub, Slack, and JWTs, producing redacted reports for remediation.

What types of credentials can a code scan identify in a CI pipeline?

A code scan identifies credentials in a CI pipeline using 20 built-in secret patterns for AWS, GitHub, Slack, Stripe, database URLs, JWTs, and high-entropy strings.

Does secret scanning work across different programming languages and platforms?

Yes, secret scanning works across different programming languages and platforms, applying pattern detection and entropy evaluation to source code and configuration files in any repository.

How do I generate a redacted report after finding credentials in my repository files?

Generate a redacted report after finding credentials by running the TypeScript handler over your repository files, which outputs actionable, redaction-ready results suitable for code review.

Can entropy evaluation find unpatterned high-entropy strings in configuration files?

Yes, entropy evaluation finds unpatterned high-entropy strings in configuration files by evaluating string randomness, flagging potential secrets that bypass standard pattern matching.

What is the best way to scan code for secrets without exposing them in reports?

The best way to scan code for secrets without exposure is using a handler that outputs redaction-ready reports, ensuring detected AWS keys or JWTs are masked in the final remediation report.