vulnerability-analysis

Identify and report source code vulnerabilities using taint analysis and CWE-style classifications.

338|59|Updated May 19, 2026
One-click install
npx skills add https://github.com/hypnguyen1209/offensive-claude --skill vulnerability-analysis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vulnerability-analysis
Source: https://github.com/hypnguyen1209/offensive-claude/tree/main/skills/vulnerability-analysis
Command: npx skills add https://github.com/hypnguyen1209/offensive-claude --skill vulnerability-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Efficiently identify and report vulnerabilities in source code using taint analysis, memory-safety checks, and vulnerability classifications to reduce exploitable risks.

Core Features & Use Cases

  • Taint analysis and source-forward/sink-backward methods to track untrusted data from origin to dangerous operations.
  • Hybrid vulnerability auditing across languages, focusing on authentication, authorization, cryptographic weaknesses, concurrency bugs, and supply chain risks.
  • Audit protocol guidance and structured findings with CWE-style taxonomy.

Quick Start

Run a vulnerability-analysis pass over your codebase to generate a taint-analysis report and remediation recommendations.

Frequently Asked Questions about vulnerability-analysis

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

FAQPage Schema
How do I perform a taint analysis on my source code to find vulnerabilities?

Taint analysis tracks untrusted data from origin to dangerous operations to identify vulnerabilities in source code. You can run an audit pass over your codebase to generate a report with structured findings and remediation recommendations.

What is the best way to audit code for cryptographic weaknesses and concurrency bugs?

Hybrid vulnerability auditing across languages focuses on authentication, authorization, cryptographic weaknesses, and concurrency bugs. It applies memory-safety checks and source-forward or sink-backward methods to track exploitable risks.

How does taint analysis classify vulnerabilities during a code security audit?

Taint analysis classifies vulnerabilities using a CWE-style taxonomy during code security audits. It provides audit protocol guidance, structured findings, and variant hunting guidelines to reduce exploitable risks in your codebase.

Can I use static analysis to detect memory-safety issues across different programming languages?

Static analysis can detect memory-safety issues across different programming languages using hybrid vulnerability auditing. It tracks untrusted data flows and applies memory-safety checks to identify exploitable code security risks.

What steps are involved in an audit protocol for automated vulnerability discovery?

An audit protocol for automated vulnerability discovery involves reconnaissance, auditing, and remediation guidance. It uses source-forward and sink-backward taint analysis to track data flows and generate structured findings with CWE-style taxonomy.

Why do I need source-forward and sink-backward methods for secure coding?

Source-forward and sink-backward methods are needed for secure coding to effectively track untrusted data from origin to dangerous operations. This taint analysis approach identifies vulnerabilities and provides structured remediation guidance to reduce exploitable risks.