stacks-security-audit

To perform a Stacks security audit, invoke the skill to map attack surfaces and evaluate code against OWASP Top 10 and STRIDE threat models. This process targets API routes, authentication flows, middleware, and dependencies to identify exploitable vulnerabilities.

STRIDE threat modeling is a framework used to evaluate security by categorizing risks like spoofing and repudiation. This skill applies STRIDE alongside OWASP Top 10 to analyze API routes and authentication flows, ensuring high-confidence findings for actionable improvements.

You can check dependencies for known vulnerabilities using the skill's dependency auditing feature. It scans project dependency trees to flag known security issues and overly permissive configurations, providing a structured framework for maintaining a secure codebase.

Yes, you can use this skill to map attack surfaces and evaluate code against the OWASP Top 10. It automatically identifies entry points including API routes, CLI commands, and WebSocket endpoints to ensure comprehensive security coverage.

The best way to identify exploitable vulnerabilities is by running a comprehensive security analysis that targets middleware and authentication flows. The skill requires concrete exploit scenarios and high-confidence findings to ensure all results are actionable.

Yes, a Stacks security audit flags overly permissive dependency configurations. During the dependency auditing phase, the skill scans the project tree to identify both known vulnerabilities and settings that pose security risks.