sast

Identify security weaknesses in source code across languages and frameworks.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/AshtonVaughan/bountyhound --skill sast-ashtonvaughan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sast
Source: https://github.com/AshtonVaughan/bountyhound/tree/main/bountyhound/skills/sast
Command: npx skills add https://github.com/AshtonVaughan/bountyhound --skill sast-ashtonvaughan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Source code security review is the process of identifying exploitable vulnerabilities in source code across languages and frameworks, enabling teams to secure builds before release and reduce risk.

Core Features & Use Cases

  • Automated discovery of common security weaknesses in codebases through static analysis and guided manual review.
  • Framework- and language-agnostic guidance for code reviews, pull requests, and CI pipelines to surface high-risk patterns.
  • Use Case: A development team reviews a GitHub repository to detect injection flaws, insecure deserialization, and misconfigurations before merge.

Quick Start

Provide a codebase you want scanned and I will initiate a SAST review to identify vulnerabilities.

Frequently Asked Questions about sast

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

FAQPage Schema
How do I find security vulnerabilities in source code before merging a pull request?

To find security vulnerabilities in source code before merging, initiate a SAST review to surface injection flaws, insecure deserialization, and misconfigurations. This process applies automated static analysis and step-by-step checklists during code reviews and CI pipelines to drive consistent remediation.

What types of security flaws can static analysis identify in my codebase?

Static analysis identifies common security weaknesses in source code across languages and frameworks, including injection flaws, insecure deserialization, and insecure configurations. It combines automated scanners with guided manual review to catalog exploitable vulnerabilities.

Can I run a SAST code review on any programming language or framework?

Yes, this SAST code review provides framework- and language-agnostic guidance to surface high-risk patterns. You can apply it across diverse open-source repositories or client-side codebases to uncover common security weaknesses.

What is the best way to integrate static analysis into a CI pipeline for security reviews?

The best way to integrate static analysis into a CI pipeline is enforcing a reproducible review process that combines automated scanners, manual focus areas, and step-by-step checklists. This approach consistently uncovers security flaws in source code before release.

How do I use static analysis to fix insecure configurations in my repository?

To fix insecure configurations using static analysis, provide your codebase to initiate a SAST review. The review identifies misconfigurations and applies guided manual focus areas and checklists to drive consistent, step-by-step remediation of the detected flaws.