sast-scanner

Scan TypeScript/JavaScript source code for OWASP-aligned security vulnerabilities.

5|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/47network/Sven --skill sast-scanner
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sast-scanner
Source: https://github.com/47network/Sven/tree/main/skills/security/sast-scanner
Command: npx skills add https://github.com/47network/Sven --skill sast-scanner

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Static analysis of TypeScript/JavaScript source code to identify security vulnerabilities, enabling teams to catch OWASP-aligned issues before release.

Core Features & Use Cases

  • SAST scanning: analyze code to detect vulnerabilities across common categories.
  • Rule inspection: list and inspect detection rules to understand coverage and findings.
  • Targeted remediation: filter findings by severity or category to prioritize fixes in code reviews and CI pipelines.

Quick Start

Run the scan action on your TypeScript/JavaScript project to generate a security report.

Frequently Asked Questions about sast-scanner

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

FAQPage Schema
How do I run static analysis to detect security vulnerabilities in JavaScript code?

To run static analysis for security vulnerabilities in JavaScript, trigger the scan action with a files map of your source code. The SAST scanner analyzes the provided TypeScript or JavaScript files and generates a security report detailing detected issues.

What types of security flaws does static analysis find in TypeScript projects?

Static analysis for TypeScript projects identifies OWASP-aligned security vulnerabilities. The SAST scanner inspects source code to detect common security flaws across various vulnerability categories, enabling targeted remediation before software release.

Can I filter static analysis findings by severity or category in code reviews?

Yes, you can filter static analysis findings by severity or category to prioritize fixes during code reviews. Use the filter_rules action with optional severity and category parameters to isolate specific vulnerabilities in your security report.

How do I inspect available detection rules before scanning my TypeScript codebase?

To inspect detection rules before scanning a TypeScript codebase, use the list_rules action to view all rules. For specific details on a single rule's coverage, use the get_rule action with the corresponding rule_id parameter.

Does this static analysis scanner require any external dependencies or setup?

No, this static analysis scanner does not require any external dependencies or setup. It operates directly on TypeScript or JavaScript source code files provided through the files map parameter during the scan action.