taint-analysis

Perform offline static taint analysis and generate a Markdown vulnerability report.

Updated Jan 28, 2026
One-click install
npx skills add https://github.com/xuziqiang98/my-skills --skill taint-analysis-xuziqiang98
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: taint-analysis
Source: https://github.com/xuziqiang98/my-skills/tree/main/taint-analysis
Command: npx skills add https://github.com/xuziqiang98/my-skills --skill taint-analysis-xuziqiang98

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the process of static taint analysis, helping to identify potential security vulnerabilities in code by tracking the flow of untrusted data.

Core Features & Use Cases

  • Comprehensive Auditing: Performs a full static taint analysis workflow, from entry point discovery to vulnerability reporting.
  • Evidence Generation: Outputs detailed evidence chains, including sources, sinks, and propagation paths.
  • Use Case: Use this Skill to proactively audit your codebase for common security flaws like SQL injection, command execution vulnerabilities, and sensitive data leakage before deployment.

Quick Start

Run the taint analysis script in the current directory to generate a security report.

Frequently Asked Questions about taint-analysis

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

FAQPage Schema
How do I automate static taint analysis for security vulnerabilities in my codebase?

Automate static taint analysis by running a read-only script that identifies sources, tracks data flow to sinks, validates sanitizers, and generates a Markdown report with evidence chains and potential attack vectors.

What is static taint analysis and how does it detect data flow vulnerabilities?

Static taint analysis detects vulnerabilities by tracking untrusted data flow from sources to sinks without executing code, validating sanitizers along propagation paths to identify security flaws like SQL injection and sensitive data leakage.

Does static taint analysis work with any programming language or framework?

Yes, comprehensive static taint analysis can be performed in a language and framework-agnostic manner, operating offline in read-only mode to audit codebases regardless of the underlying technology stack.

How do I generate an evidence chain for vulnerability detection during a security audit?

Generate evidence chains by performing static taint analysis that documents the untrusted source, traces the data propagation path, identifies the vulnerable sink, and compiles these validation results into a Markdown report.

What types of security flaws can static taint analysis identify before deployment?

Static taint analysis proactively identifies common security flaws such as SQL injection, command execution vulnerabilities, and sensitive data leakage by tracking untrusted data flow and validating sanitizers across the codebase.

Will running static taint analysis modify my source code during the security audit?

No, static taint analysis operates strictly in a read-only mode for auditing purposes, ensuring it tracks data flow and generates vulnerability reports without modifying your underlying source code.