orbit-sec-secrets-leak

Detect hardcoded secrets in WordPress plugins and git history.

2|1|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/adityaarsharma/orbit --skill orbit-sec-secrets-leak
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: orbit-sec-secrets-leak
Source: https://github.com/adityaarsharma/orbit/tree/main/skills/orbit-sec-secrets-leak
Command: npx skills add https://github.com/adityaarsharma/orbit --skill orbit-sec-secrets-leak

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gitleaks, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill scans WordPress plugin codebases and git histories for hardcoded secrets, such as API keys, OAuth tokens, and password hashes, helping prevent security breaches.

Core Features & Use Cases

  • Secret Detection: Identifies hardcoded secrets in the codebase and git history.
  • Regex Detection: Uses regex patterns to identify common API key formats.
  • Entropy Detection: Identifies strings with high entropy that are likely secrets.
  • Git History Scan: Checks for secrets in the full git history, including committed and reverted ones.
  • Quick Start: Offers a simple command to start scanning a plugin's codebase.

Quick Start

Use the gitleaks detect --source ~/plugins/my-plugin --verbose command to scan the codebase.

Frequently Asked Questions about orbit-sec-secrets-leak

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

FAQPage Schema
How do I scan a WordPress plugin for hardcoded secrets?

Scanning a WordPress plugin for hardcoded secrets involves using gitleaks to detect API keys, OAuth tokens, and password hashes in the codebase by running a command like `gitleaks detect --source ~/plugins/my-plugin --verbose`.

Does gitleaks scan git history for reverted API keys and OAuth tokens?

Gitleaks scans the full git history for reverted API keys and OAuth tokens, ensuring that committed and reverted secrets within a WordPress plugin codebase are detected.

How does entropy detection find secrets in a codebase?

Entropy detection finds secrets in a codebase by identifying strings with high randomness that are likely hardcoded secrets, complementing regex patterns used to find common API key formats in WordPress plugins.

Do I need gitleaks to detect hardcoded secrets in WordPress plugins?

You need gitleaks installed as a required dependency to detect hardcoded secrets in WordPress plugins, as it provides the regex pattern matching and entropy detection scanning engine for codebases and git histories.

What types of hardcoded secrets can be detected in a WordPress plugin codebase?

Hardcoded secrets detected in a WordPress plugin codebase include API keys, OAuth tokens, and password hashes, identified through regex pattern matching and entropy detection mechanisms.