vulnerability-scanner

Scan project directories for dependencies, secrets, code patterns, and configuration vulnerabilities.

Updated Feb 24, 2026

Search Tags:#code quality #security #vulnerability #owasp #dependencies #secrets #scan

Ready to run

npx skills add https://github.com/nonputtipong/Oryn --skill vulnerability-scanner-nonputtipong

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: vulnerability-scanner
Source: https://github.com/nonputtipong/Oryn/tree/main/.agent/skills/vulnerability-scanner
Command: npx skills add https://github.com/nonputtipong/Oryn --skill vulnerability-scanner-nonputtipong

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps identify and mitigate security risks within a project by scanning for common vulnerabilities, insecure configurations, and dangerous code patterns, aligning with modern security best practices.

Core Features & Use Cases

Dependency Security: Analyzes project dependencies for known vulnerabilities (OWASP A03).
Secret Detection: Scans code and configuration files for hardcoded secrets like API keys and passwords (OWASP A04).
Code Pattern Analysis: Identifies risky code patterns such as injection vulnerabilities and insecure deserialization (OWASP A05).
Configuration Review: Checks for common security misconfigurations in project settings.
Use Case: Before deploying a new feature, run this scanner to ensure no critical vulnerabilities or exposed secrets are present in the codebase or its dependencies.

Quick Start

Use the vulnerability-scanner skill to perform a full security scan on the current project directory.

Frequently Asked Questions about vulnerability-scanner

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

FAQPage Schema

How do I scan a project directory for security vulnerabilities before deployment?▼

To scan for security vulnerabilities, run a comprehensive security scanner on your project directory. This identifies known dependency vulnerabilities, hardcoded secrets, dangerous code patterns, and configuration misconfigurations before deployment.

How do I detect hardcoded secrets and API keys in my source code?▼

To detect hardcoded secrets, perform a targeted secret scan on your code and configuration files. This identifies exposed API keys and passwords aligning with OWASP A04 insecure design practices to mitigate security risks.

Can I check project dependencies for known vulnerabilities and OWASP compliance?▼

Yes, you can check project dependencies for known vulnerabilities. A targeted dependency scan analyzes your project packages against security best practices and OWASP A03 injection risks to identify outdated or insecure libraries.

What is the best way to identify dangerous code patterns like insecure deserialization?▼

The best way to identify dangerous code patterns is to run a targeted code pattern analysis scan. This process flags risky code like injection vulnerabilities and insecure deserialization aligning with OWASP A05 security misconfiguration standards.

Does a full security scan review project configurations against best practices?▼

Yes, a full security scan reviews project configurations against security best practices. The configuration review checks for common security misconfigurations in project settings to prevent unintended exposure of sensitive data.

Can I run a targeted scan for just secrets without analyzing dependencies?▼

Yes, you can run a targeted scan for just secrets without analyzing dependencies. The scanner supports isolated scans for secrets, dependencies, code patterns, or configuration to fit specific vulnerability mitigation workflows.