
Angular Security
- 203 installs
- 6 repo stars
- Updated April 4, 2026
- oguzhan18/angular-ecosystem-skills
angular-security is a Claude Code skill that applies Angular XSS, CSRF, CSP and sanitization defenses when building Angular apps.
About
angular-security is a Claude Code skill that applies Angular's built-in security defenses when writing or reviewing Angular code. It covers DomSanitizer usage, HttpClient CSRF protection, Content Security Policy, Trusted Types, input validation, auth interceptors and route guards. A developer uses it while hardening an Angular app against XSS, CSRF and injection. It ships code patterns keyed to Angular 21 APIs.
- DomSanitizer and bypassSecurityTrust guidance
- HttpClient CSRF/XSRF configuration
- Content Security Policy and Trusted Types
- Auth interceptors and router guards
Angular Security by the numbers
- 203 all-time installs (skills.sh)
- +3 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #769 of 2,203 Security skills by installs in the Skillselion catalog
- Data as of Aug 4, 2026 (Skillselion catalog sync)
angular-security capabilities & compatibility
free, no API key required
- Capabilities
- xss prevention · csrf protection · content security policy · html sanitization · input validation
- Use cases
- security audit · frontend
- Pricing
- Free
What angular-security says it does
ALWAYS use when working with Angular Security, XSS prevention, CSRF protection, Content Security Policy, or sanitization in Angular applications.
NEW: HttpClient CSRF — Built-in CSRF protection with CookieXSRFStrategy
npx skills add https://github.com/oguzhan18/angular-ecosystem-skills --skill angular-securityAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 203 |
|---|---|
| repo stars | ★ 6 |
| Last updated | April 4, 2026 |
| Repository | oguzhan18/angular-ecosystem-skills ↗ |
How do I prevent XSS and CSRF in an Angular app the right way?
security-audit
Who is it for?
Angular developers hardening a component or HTTP layer against XSS and CSRF.
Skip if: Non-Angular stacks or general application-security programs beyond the front end.
When should I use this skill?
When working with Angular security, XSS prevention, CSRF protection, Content Security Policy, or sanitization in Angular applications.
What you get
Angular code that uses DomSanitizer, CSRF tokens, CSP and Trusted Types correctly.
By the numbers
- Targets Angular 21 (2025)
- 4 NEW version-specific security API changes documented
Files
Angular Security
Version: Angular 21 (2025) Tags: Security, XSS, CSRF, CSP, Sanitization
References: Security Guide • DomSanitizer
API Changes
This section documents recent version-specific API changes.
- NEW: Trusted Types — Angular supports Trusted Types for CSP
- NEW: HttpClient CSRF — Built-in CSRF protection with CookieXSRFStrategy
- NEW: provideZoneChangeDetection with untrustedEvents — Zone.js event filtering
- NEW: afterNextRender security — Run code safely after rendering
Best Practices
- Use DomSanitizer for safe HTML
import { DomSanitizer, SafeHtml } from '@angular/platform-browser';
constructor(private sanitizer: DomSanitizer) {}
getSafeHtml(html: string): SafeHtml {
return this.sanitizer.bypassSecurityTrustHtml(html);
}- Use bypassSecurityTrust methods carefully
// Only use when content is trusted
this.safeUrl = this.sanitizer.bypassSecurityTrustUrl(userInput);
this.safeScript = this.sanitizer.bypassSecurityTrustScript(script);
this.safeStyle = this.sanitizer.bypassSecurityTrustStyle(style);
this.safeResourceUrl = this.sanitizer.bypassSecurityTrustResourceUrl(url);- Use HttpClient with CSRF protection
// Automatically uses XSRF-TOKEN cookie
http.get('/api/data').subscribe();
// Configure CSRF
provideHttpClient(
withXsrfConfiguration({
cookieName: 'XSRF-TOKEN',
headerName: 'X-XSRF-TOKEN'
})
)- Use innerHTML with sanitization
@Component({
template: `<div [innerHTML]="safeContent"></div>`
})
export class MyComponent {
// Angular sanitizes automatically
safeContent = '<p>Safe content</p>';
}- Avoid dynamic template evaluation
// ❌ Dangerous
eval(userInput);
// ✅ Safe - use Angular's binding
{{ userInput }}- Use Content Security Policy
<meta http-equiv="Content-Security-Policy"
content="default-src 'self'; script-src 'self'">- Use Trusted Types
import { provideTrustedTypes } from '@angular/core';
export const appConfig: ApplicationConfig = {
providers: [
provideTrustedTypes()
]
};- Validate user input
import { Pipe, PipeTransform } from '@angular/core';
@Pipe({ name: 'escapeHtml' })
export class EscapeHtmlPipe implements PipeTransform {
transform(value: string): string {
return value
.replace(/&/g, '&')
.replace(/</g, '<')
.replace(/>/g, '>')
.replace(/"/g, '"');
}
}- Use HttpClient interceptors for auth
export const authInterceptor: HttpInterceptorFn = (req, next) => {
const token = inject(AuthService).getToken();
if (token) {
const authReq = req.clone({
setHeaders: { Authorization: `Bearer ${token}` }
});
return next(authReq);
}
return next(req);
};- Use router guards for route protection
export const authGuard: CanActivateFn = () => {
const auth = inject(AuthService);
const router = inject(Router);
if (auth.isAuthenticated()) {
return true;
}
return router.createUrlTree(['/login']);
};Docs Reference Index
Official Documentation
- Angular Security - Main guide
- DomSanitizer API
- HttpClient Security
Tutorials
Releases Reference Index
Blog Posts
Changelog
Related skills
FAQ
What does angular-security cover?
XSS prevention, CSRF protection, Content Security Policy, Trusted Types, input validation, auth interceptors and route guards for Angular applications.
Which Angular version does it target?
It documents Angular 21 (2025) APIs including Trusted Types, HttpClient CSRF and afterNextRender security.