Security Scanner

Scans public Git repositories for known vulnerabilities using the Burp Suite tool.

Updated Feb 3, 2026
One-click install
npx skills add https://github.com/sky770825/openclaw-console-hub --skill security-scanner-sky770825
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Security Scanner
Source: https://github.com/sky770825/openclaw-console-hub/tree/main/armory/security-scanner
Command: npx skills add https://github.com/sky770825/openclaw-console-hub --skill security-scanner-sky770825

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of identifying known security vulnerabilities within public Git repositories, helping to proactively secure software development pipelines.

Core Features & Use Cases

  • Vulnerability Scanning: Utilizes Trivy to scan a specified public Git repository for Common Vulnerabilities and Exposures (CVEs).
  • Automated Reporting: Provides immediate feedback on potential security risks found in the code repository.
  • Use Case: Before merging a new feature branch from a third-party contributor, use this Skill to scan its repository to ensure it doesn't introduce known security flaws.

Quick Start

Scan the public Git repository located at https://github.com/aquasecurity/trivy-ci-test for vulnerabilities.

Frequently Asked Questions about Security Scanner

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

FAQPage Schema
How do I scan a public Git repository for known vulnerabilities?

To scan a public Git repository for known vulnerabilities, this Skill uses the Trivy security scanner to analyze repository contents and identify Common Vulnerabilities and Exposures (CVEs). It automates vulnerability scanning for continuous integration pipelines and pre-deployment code audits.

Can I use this to check a third-party Git repository before merging code?

Yes, you can scan a third-party public Git repository before merging code. The Skill applies Trivy to analyze repository contents for CVEs, ensuring new feature branches from external contributors do not introduce known security flaws into your pipeline.

Do I need Trivy installed to scan my repository for CVEs?

Yes, you need Trivy installed in your execution environment to scan your repository for CVEs. The Skill requires the Trivy security scanner to be available locally to analyze Git repository contents and detect known vulnerabilities.

What is the best way to automate vulnerability scanning for continuous integration?

Automating vulnerability scanning for continuous integration is best achieved by running Trivy against target Git repositories. This Skill integrates into CI pipelines to automatically report CVEs and provide immediate feedback on potential security risks found in code.

Does this vulnerability scanner work with private Git repositories?

This vulnerability scanner is designed to work with public Git repositories. It uses Trivy to analyze publicly accessible repository contents for CVEs, and the metadata does not indicate support for scanning private Git repositories requiring authentication.