Vulnerability Database · npm · @angular/localize · Version
@angular/localize 20.3.30
No vulnerabilities in this database cover 20.3.30.
Every vulnerability Vulert holds for @angular/localize was tested against this version and none of them covers it. That is the good answer, not a guarantee — the package page shows which versions are affected.
Critical 0 High 0 Medium 0 Low 0 Unrated 0
-
Released 26 Aug 2026
Licence MIT
Also known from other sources 0
Newer releases 300
Database updated 23/Oct/2026
Release and licence data published by the npm registry. Licence information is not legal advice.
Concerned about your application's security?
Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.
01 Vulnerabilities affecting this version
@angular/localize 20.3.30 vulnerabilities
No vulnerability in the Vulert database covers @angular/localize 20.3.30. See the versions that are affected →
Looking for another version, or everything Vulert holds for @angular/localize?
Questions
About @angular/localize 20.3.30
Is @angular/localize 20.3.30 vulnerable?
No. No vulnerability in the Vulert database covers @angular/localize 20.3.30. Every vulnerability Vulert holds for @angular/localize was tested against this release and none of them covers it — the good answer, though not a guarantee, since new vulnerabilities are published for packages all the time.
Is 20.3.30 the latest release of @angular/localize?
No. 20.3.30 was published 26 Aug 2026, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
How do I monitor @angular/localize for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the @angular/localize version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.