security_scan

Scan repository code and dependencies for security vulnerabilities with prioritized findings.

Updated Jun 20, 2026
One-click install
npx skills add https://github.com/4tie/fortiesr --skill security-scan-4tie
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security_scan
Source: https://github.com/4tie/fortiesr/tree/main/.local/skills/security_scan
Command: npx skills add https://github.com/4tie/fortiesr --skill security-scan-4tie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes the burden of manually checking codebases for dependency risks, insecure code patterns, and privacy-sensitive data flows.

Core Features & Use Cases

  • Dependency Auditing: Check package ecosystems for known vulnerabilities before they reach production.
  • Static Security Analysis: Surface risky code patterns, misconfigurations, and other implementation flaws in source files.
  • Dataflow and Privacy Review: Detect where sensitive information may be exposed, transmitted, or mishandled.
  • Use Case: A developer can run this skill on a repository before release to get a prioritized list of critical and high findings with clear remediation direction.

Quick Start

Ask the skill to scan the repository and return the most important security findings first.

Frequently Asked Questions about security_scan

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

FAQPage Schema
How do I scan a repository for security vulnerabilities before release?

Security scanning requires parallel scanner execution with per-scanner failure tolerance. If one scanner fails, others continue running, and the skill still delivers prioritized critical and high findings with remediation guidance.

What does static security analysis detect in source code?

Static security analysis surfaces risky code patterns, misconfigurations, and implementation flaws in source files. It works by scanning source code to identify insecure patterns before they reach production environments.

How does dependency auditing work for known vulnerabilities?

Dependency auditing checks package ecosystems for known vulnerabilities before they reach production. It works by cross-referencing your project's dependencies against vulnerability databases to identify at-risk packages.

When do I need a privacy-focused dataflow review?

Privacy-focused dataflow review detects where sensitive information may be exposed, transmitted, or mishandled. It traces the movement of sensitive data through your codebase to identify potential privacy violations.

Can I use security scanning during development or only pre-release?

Security scanning supports pre-release validation during the software development lifecycle. It applies to projects needing dependency auditing, static analysis, and privacy-focused dataflow review before deployment.

What happens if one scanner fails during a repository security scan?

Security scanning requires parallel scanner execution with per-scanner failure tolerance. If one scanner fails, others continue running, and the skill still delivers prioritized critical and high findings with remediation guidance.