Map codebase architecture and technology stack into sast/architecture.md.
npx skills add https://github.com/utkusen/sast-skills --skill sast-analysis
Please help me install this Agent Skill. Skill: sast-analysis Source: https://github.com/utkusen/sast-skills/tree/main/sast-files/.agents/skills/sast-analysis Command: npx skills add https://github.com/utkusen/sast-skills --skill sast-analysis
Perform codebase analysis and architecture mapping as the first phase of a security assessment. Explores the tech stack, frameworks, entry points, data flows, and trust boundaries. Outputs sast/architecture.md. Run this before any vulnerability detection skill. Use when asked to analyze a codebase for security or when sast/architecture.md does not yet exist.
Run sast-analysis to generate the architecture.md file for your codebase before executing vulnerability detection.
High-intent search queries and answers about installing and using this skill.
To map codebase architecture for a security assessment, analyze the codebase to identify the technology stack, frameworks, entry points, data flows, and trust boundaries. This process outputs an architecture.md artifact detailing the structural overview for threat modeling.
Codebase reconnaissance in threat modeling is the initial analysis phase that identifies languages, frameworks, dependencies, and infrastructure hints. It maps data flows and trust boundaries to establish the security context before vulnerability detection begins.
Yes, you need to analyze architecture before running vulnerability detection to establish security context. Mapping technology stacks, entry points, and trust boundaries first guides accurate threat modeling and remediation planning across diverse deployment patterns.
Identify trust boundaries and data flows by performing technology reconnaissance across the codebase. Analyze deployment patterns and frameworks to map how data moves through entry points, generating an architectural overview to support threat modeling.
The best way to document a tech stack for security reviews is to analyze the codebase and generate an architecture.md artifact. This file records identified languages, dependencies, infrastructure hints, and data flows to guide remediation planning.
Yes, this codebase analysis approach applies to security reviews across diverse languages, frameworks, and deployment patterns. It maps architecture and technology stacks universally to guide threat modeling regardless of the underlying environment.
alangebPerform Git bisecting, cherry-picking, and log analysis operations locally.
borgheiIdentify and mitigate security risks in software systems using expert security engineering practices.
florianbuetowScan code and dependencies for vulnerabilities mapped to CWEs.
mlvpatelIdentify and remediate security weaknesses in source code via static analysis.
