@angular/compiler
npmIs @angular/compiler safe to use?
Based on the latest brin safety scan, no vulnerabilities or threats were detected for @angular/compiler v21.1.2. Trust score: 75/100. 1 known CVE, no detected threat patterns, and no suspicious capabilities identified. This is an automated, point-in-time assessment.
Install (safety-checked)
@angular/compiler Passed Security Checks
No security concerns detected
1
0
0
@angular/compiler CVE Vulnerabilities (1)
Angular has XSS Vulnerability via Unsanitized SVG Script Attributes
brin Recommendations
- →1 high-severity CVE with no known fix. Consider alternatives or implement mitigations.
Install with brin add @angular/compiler to automatically apply these checks before installation.
This is an automated, point-in-time assessment and may contain errors. Findings are risk indicators, not confirmed threats. Security posture may change over time. Maintainers can dispute findings via the brin review process.
@angular/compiler Capabilities & Permissions
No system capabilities detected for @angular/compiler. It does not appear to access the network, filesystem, spawn processes, or use native modules. No capability concerns identified for use with AI coding agents.
AGENTS.md for @angular/compiler
Good instructions lead to good results. brin adds @angular/compiler documentation to your AGENTS.md so your agent knows how to use it properly—improving both safety and performance.
brin initVercel's research: 100% accuracy with AGENTS.md vs 53% without →
@angular/compiler Documentation & Source Code
For the full @angular/compiler README, API documentation, and source code, visit the official package registry.
Frequently asked questions about @angular/compiler safety
Install (safety-checked)
Weekly Downloads
Version
21.1.2License
MITLast Scanned
Trust Score
CVEs (1)
Angular has XSS Vulnerability via Unsanitized SVG Script Attributes
Capabilities
No special capabilities detected