oss-secret-scan

Scan repositories for leaked secrets, PII, and infrastructure data.

21|3|Updated May 26, 2026
One-click install
npx skills add https://github.com/AlphaBitCore/nexus-gateway --skill oss-secret-scan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: oss-secret-scan
Source: https://github.com/AlphaBitCore/nexus-gateway/tree/main/.claude/skills/oss-secret-scan
Command: npx skills add https://github.com/AlphaBitCore/nexus-gateway --skill oss-secret-scan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OSS repositories often contain secrets, PII, and infrastructure data that, if leaked, pose security and compliance risks. This Skill provides a deterministic scanner that uses regex, Shannon entropy, and an allowlist to reliably detect leaks without relying on model inference, enabling safe triage and remediation.

Core Features & Use Cases

  • Deterministic detection: uses regex patterns plus entropy analysis to surface leak candidates with low false positives.
  • LLM triage workflow: surfaces candidates for human review while ensuring the model only triages, not detects.
  • Pre-release gate: helps ensure code released publicly is free of secrets and sensitive data.

Quick Start

Run the deterministic OSS scanner to identify leak candidates and triage them with a model.

Frequently Asked Questions about oss-secret-scan

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

FAQPage Schema
How do I scan a repository for leaked secrets and PII?

To scan a repository for leaked secrets and PII, this tool uses a deterministic detector combining regex patterns and Shannon entropy to identify leak candidates, outputting findings via standard output with optional JSON mode and severity filtering.

How does entropy analysis work for secret detection?

Entropy analysis for secret detection calculates Shannon entropy to identify high-randomness strings that likely represent leaked secrets, combining these results with regex pattern matching to reduce false positives without relying on model inference.

Can I use a deterministic scanner as a pre-release gate in CI?

Yes, you can use this deterministic scanner as a pre-release gate in CI to ensure code released publicly is free of secrets, utilizing allowlists and severity filtering to triage leak candidates across large mono-repos and multi-language projects.

What is the best way to triage leaked infrastructure data in code?

The best way to triage leaked infrastructure data is to use a deterministic scanner to surface candidates for human review, keeping triage decisions separate from detection to ensure safe remediation without false positives from LLM inference.

Does this secret scanner support JSON output for CI workflows?

Yes, this secret scanner supports JSON output mode for CI workflows, allowing you to filter findings by severity and parse standard output programmatically alongside regex and entropy analysis across multi-language projects.

Why use an allowlist instead of model inference for finding leaked PII?

Using an allowlist instead of model inference for finding leaked PII ensures deterministic detection with low false positives, preventing the model from hallucinating sensitive data and keeping human triage decisions strictly separate from the detection logic.