security-scanning

Analyze code for OWASP Top 10 vulnerabilities, secrets, and dependency CVEs.

Updated Mar 13, 2026
One-click install
npx skills add https://github.com/kirvin/copilot-cli-essentials --skill security-scanning-kirvin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-scanning
Source: https://github.com/kirvin/copilot-cli-essentials/tree/main/plugins/cpe/skills/security-scanning
Command: npx skills add https://github.com/kirvin/copilot-cli-essentials --skill security-scanning-kirvin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps identify and mitigate security risks in your codebase, ensuring that vulnerabilities, secrets, and outdated dependencies are addressed before they can be exploited.

Core Features & Use Cases

  • Vulnerability Identification: Detects common application security flaws like injection, broken access control, and cross-site scripting (XSS).
  • Secret Detection: Scans code for hardcoded secrets, API keys, and other sensitive credentials.
  • Dependency Auditing: Checks for known vulnerabilities (CVEs) in project dependencies.
  • Use Case: Before merging a pull request, run this skill to perform a comprehensive security audit, catching potential vulnerabilities and exposed secrets.

Quick Start

Run a security scan on the current codebase to identify vulnerabilities and exposed secrets.

Frequently Asked Questions about security-scanning

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

FAQPage Schema
How do I scan my codebase for hardcoded secrets and exposed API keys?

Scanning code for hardcoded secrets requires a comprehensive security analysis that inspects source files for sensitive credentials. This process identifies exposed secrets within your codebase, allowing you to mitigate risks before they are exploited in production environments.

How do I audit project dependencies for known CVEs and supply chain risks?

Auditing project dependencies for known CVEs involves analyzing dependency manifests to identify vulnerable packages. This supply chain risk assessment checks your project dependencies against known vulnerability databases to ensure outdated or compromised libraries are addressed before release.

What is the best way to detect OWASP Top 10 vulnerabilities in my application?

Detecting OWASP Top 10 vulnerabilities requires a comprehensive security analysis of application code structure. This process identifies common application security flaws like injection, broken access control, and cross-site scripting, ensuring your codebase is hardened against standard exploit vectors.

Can I use a security scan to check for vulnerabilities before merging a pull request?

Yes, you can run a comprehensive security scan before merging a pull request to perform a pre-release audit. This checks your code structure and dependency manifests for potential vulnerabilities, exposed secrets, and runtime exploits, ensuring continuous auditing during development.

What does application security scoping entail for pre-release hardening?

Application security scoping for pre-release hardening entails analyzing code structure, dependency manifests, and potential runtime exploits. This comprehensive assessment scopes application security, secrets management, and supply chain risks to identify and mitigate vulnerabilities before software release.