sast-investigator

Trace source-to-sink data flow to classify SAST findings as true positives.

1|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/0x53c7/security-testing-rovodev-skills --skill sast-investigator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sast-investigator
Source: https://github.com/0x53c7/security-testing-rovodev-skills/tree/main/.rovodev/skills/sast-investigator
Command: npx skills add https://github.com/0x53c7/security-testing-rovodev-skills --skill sast-investigator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps security engineers triage SAST findings by performing rigorous source-to-sink analysis to distinguish real vulnerabilities from false positives.

Core Features & Use Cases

  • Comprehensive triage: trace data flow from source input to sink (dangerous operation) across files.
  • Evidence-driven decisions: every verdict includes file path, line, code snippet, and rationale.
  • Scoped handling: supports Semgrep and other SAST outputs to prioritise remediation.

Quick Start

Identify and triage SAST findings by tracing data flow from source to sink and classifying as true positive, false positive, or uncertain.

Frequently Asked Questions about sast-investigator

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

FAQPage Schema
How do I triage SAST findings to identify true positives?

Triage SAST findings by performing source-to-sink data flow analysis across files to distinguish real vulnerabilities from false positives. This skill traces data from source input to dangerous operations and produces evidence-backed classifications with file paths and code snippets.

What is source-to-sink analysis in static analysis code review?

Source-to-sink analysis in static code review traces untrusted data flow from entry points to dangerous operations. This skill applies it to validate SAST findings, determining if a vulnerability is exploitable by verifying the complete execution path.

Can I use this to triage Semgrep output with evidence?

Yes, you can triage Semgrep output along with other SAST tool results. The skill processes these outputs to prioritize remediation by validating findings and documenting decisions with evidence like file paths, line numbers, and code rationale.

How do I classify false positives in static analysis findings?

Classify false positives in static analysis by tracing data flow paths to see if sanitization blocks the vulnerability. This skill evaluates SAST findings and categorizes them as true positives, false positives, or uncertain based on rigorous source-to-sink validation.

Do I need workspace code access to validate SAST findings?

Yes, you need workspace code access to validate SAST findings effectively. The skill requires direct access to source code and tooling to trace data flow, verify the execution context, and document evidence-backed decisions for each finding.

Why does SAST tools report so many false positives during code review?

SAST tools report many false positives during code review because they lack contextual execution path validation. This skill resolves this by performing rigorous source-to-sink data flow analysis to distinguish actual vulnerabilities from benign code patterns.