dev-security-frontend

Scans Angular and TypeScript frontend code for OWASP Top 10:2025 compliance and vulnerabilities.

7|3|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/eriklieben/agentic-dev-workflow --skill dev-security-frontend
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev-security-frontend
Source: https://github.com/eriklieben/agentic-dev-workflow/tree/main/.claude/skills/dev-security-frontend
Command: npx skills add https://github.com/eriklieben/agentic-dev-workflow --skill dev-security-frontend

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill addresses the critical need for consistent, automated security reviews in Angular/TypeScript applications, preventing common vulnerabilities like XSS, broken access control, and secret leakage.

Core Features & Use Cases

  • OWASP Compliance: Validates code against the latest OWASP Top 10:2025 standards specifically adapted for modern Angular.
  • Automated Scanning: Performs static analysis for secrets, console leaks, and insecure dependency configurations.
  • Use Case: Before a production release, run this skill to verify that your Angular components are free of sensitive data exposure, that your route guards are functional, and that your build configuration is hardened against common injection attacks.

Quick Start

Invoke the dev-security skill with the full flag to perform a comprehensive security review of your current frontend codebase.

Frequently Asked Questions about dev-security-frontend

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

FAQPage Schema
How do I check my Angular application for OWASP Top 10 vulnerabilities?

You can check an Angular application for OWASP vulnerabilities by running an automated static analysis security review that validates code against OWASP Top 10:2025 standards, specifically targeting XSS prevention and broken access control.

How do I scan a TypeScript frontend bundle for leaked secrets?

To scan a TypeScript frontend bundle for leaked secrets, execute an automated security scan that performs static analysis on your build output to identify sensitive data exposure and insecure dependency configurations.

What is the best way to audit Angular route guards and form handling for security flaws?

The best way to audit Angular route guards and form handling is to run a pre-production security checklist that validates authentication patterns and ensures functional access control before deployment.

Can I use this to review dependency configurations for supply chain integrity?

Yes, you can use this security review to audit dependency configurations for supply chain integrity by performing static analysis on your TypeScript project to detect insecure package setups and potential injection risks.

When should I run a frontend security scan on my TypeScript codebase?

You should run a frontend security scan on your TypeScript codebase before a production release to verify that components are free of sensitive data exposure and that build configurations are hardened against injection attacks.