Vuln Scanner

Identify real security vulnerabilities in trending repositories and route disclosures.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/Atrium-Hermes/atrium-lighthouse --skill vuln-scanner-atrium-hermes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Vuln Scanner
Source: https://github.com/Atrium-Hermes/atrium-lighthouse/tree/main/skills/vuln-scanner
Command: npx skills add https://github.com/Atrium-Hermes/atrium-lighthouse --skill vuln-scanner-atrium-hermes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Security teams often struggle to identify real vulnerabilities amid noise and to disclose them safely. Vuln Scanner automates detection and routes findings to the correct, safe disclosure channel, supporting private vulnerability reporting for code flaws and public PRs only for publicly disclosed dependency CVEs.

Core Features & Use Cases

  • Private Vulnerability Reporting (PVR) for code flaws with safe, non-public disclosure channels until a vulnerability is disclosed.
  • Dependency CVE handling via public PR bumps for already disclosed CVEs, guided by OSV scanning.
  • Automated triage workflow that consolidates findings from multiple scanners and selects the proper channel based on the type of finding.

Quick Start

Run the vuln-scanner against a target repository to begin triage and determine the appropriate private disclosure route.

Frequently Asked Questions about Vuln Scanner

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

FAQPage Schema
How do I safely report security vulnerabilities found in GitHub repositories?

Private vulnerability reporting routes code flaws through non-public disclosure channels until they are safely resolved, while public PRs are used only for already disclosed dependency CVEs.

Does the vulnerability triage process support semgrep, trufflehog, and osv-scanner?

The triage workflow requires SAST, secret scanning, and dependency-analysis tools including semgrep, trufflehog, osv-scanner, and slither to identify and consolidate findings from target repositories.

What is the difference between handling code flaws and dependency CVEs during security disclosure?

Code flaws require private vulnerability reporting to avoid public exposure, whereas dependency CVEs that are already public can be safely handled via public PR bumps guided by OSV scanning.

How do I consolidate noisy scanner results to identify real security vulnerabilities?

An automated triage workflow consolidates findings from multiple scanners, applies a dedup state to remove noise, and selects the proper disclosure channel based on the finding type.

When should I use private vulnerability reporting instead of opening a public PR?

Private vulnerability reporting should be used for code flaws to ensure safe, non-public disclosure, while public PRs are reserved exclusively for dependency CVEs that are already publicly known.

Can I scan trending GitHub repositories for secret exposure and dependency issues?

The scanner identifies real vulnerabilities in trending repositories by running trufflehog for secrets, osv-scanner for dependencies, and slither for analysis within a safe triage workflow.