Vulnerability Database · npm · Package report
@angular/fire: vulnerability history, versions and safety
@angular/fire is a package in the npm ecosystem. Vulert holds no vulnerabilities for it yet.
Nothing recorded for this package in the npm ecosystem.
Every vulnerability has a patched version to move to.
No published version shipped hostile code.
Vulert verdict on @angular/fire 20.1.1 i
Updated on 23 Oct 2026
Good news: 20.1.1, the version you would install today, has no known vulnerabilities.
- Security No known security issues
- Maintenance Sustainable
- Popularity Niche
- Community Active
What to do: Stay on 20.1.1 or newer. This can change: a vulnerability disclosed tomorrow can affect 20.1.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release 20.1.1 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Depended on by 2 packages i
- Stars 7,798 i
- OpenSSF scorecard 7/10 i
- Last release this month i
- Licence MIT i
Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. 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 Versions
Which versions are affected
Every version Vulert tracks for @angular/fire, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.
- 21.0.1-canary.20261010050934.sha-f020821 12 Oct 2026
- 21.0.0-rc.2 10 Oct 2026
- 20.1.1 10 Oct 2026
- 21.0.1-canary.20261009185857.sha-4c5ba7e 09 Oct 2026
- 21.0.1-canary.20261009184859.sha-d95316b 09 Oct 2026
- 21.0.1-canary.20261009184033.sha-bbce8f0 09 Oct 2026
- 21.0.1-canary.20261009183126.sha-31fb2ae 09 Oct 2026
- 21.0.1-canary.20261005034752.sha-bc3fdad 06 Oct 2026
- 21.0.1-canary.20261005001317.sha-eee3486 05 Oct 2026
- 21.0.1-canary.20261005000202.sha-7cc64e6 05 Oct 2026
- 21.0.0-canary.20260930011755.sha-59d44e7 01 Oct 2026
- 21.0.0-canary.20260927235954.sha-f182972 28 Sep 2026
- 21.0.0-canary.20260927235300.sha-84a8a51 27 Sep 2026
- 21.0.0-canary.20260927232311.sha-38dfc3f 27 Sep 2026
- 21.0.0-canary.20260927231611.sha-ac17ede 27 Sep 2026
- 21.0.0-canary.a2662fe 24 Sep 2026
- 21.0.0-rc.1 22 Sep 2026
- 20.1.0 22 Sep 2026
- 21.0.0-rc.1-canary.95b3de1 21 Sep 2026
- 21.0.0-rc.0-canary.345726a 21 Sep 2026
- 20.0.3 21 Sep 2026
- 21.0.0-rc.0-canary.5b3112a 02 Sep 2026
- 21.0.0-rc.0-canary.36bab40 02 Sep 2026
- 21.0.0-rc.0-canary.97f61a4 02 Sep 2026
- 21.0.0-rc.0-canary.e578ccb 01 Sep 2026
- 21.0.0-rc.0-canary.b83343d 21 Aug 2026
- 21.0.0-rc.0-canary.fb6796b 20 Aug 2026
- 21.0.0-rc.0-canary.4ff403d 18 Aug 2026
- 21.0.0-rc.0-canary.73acea7 18 Aug 2026
- 21.0.0-rc.0-canary.e410e5a 18 Aug 2026
- 21.0.0-rc.0-canary.778625a 17 Aug 2026
- 21.0.0-rc.0-canary.934cc46 17 Aug 2026
- 21.0.0-rc.0-canary.0e8ed0c 13 Aug 2026
- 21.0.0-rc.0-canary.b257054 12 Aug 2026
- 21.0.0-rc.0-canary.0b8a49d 12 Aug 2026
- 21.0.0-rc.0-canary.279d891 06 Aug 2026
- 21.0.0-rc.0-canary.c4c4ad1 05 Aug 2026
- 21.0.0-rc.0-canary.a99f09b 05 Aug 2026
- 21.0.0-rc.0-canary.6ef4767 05 Aug 2026
- 21.0.0-rc.0-canary.3b1096f 05 Aug 2026
- 21.0.0-rc.0-canary.88c7b80 03 Aug 2026
- 21.0.0-rc.0-canary.b551b5f 03 Aug 2026
- 21.0.0-rc.0-canary.f54c0fe 29 Jul 2026
- 21.0.0-rc.0 26 Nov 2025
- 21.0.0-rc.0-canary.ac3dd7c 26 Nov 2025
- 20.0.1 12 Jun 2025
- 20.0.0-canary.eb99d8e 12 Jun 2025
- 20.0.0 03 Jun 2025
- 20.0.0-rc.0 30 May 2025
- 20.0.0-canary.c1c6af9 30 May 2025
- 19.2.0 20 May 2025
- 19.2.0-canary.61fde1b 20 May 2025
- 19.1.0-canary.20bee94 14 May 2025
- 19.1.0 09 Apr 2025
- 19.1.0-canary.ec4e3bd 09 Apr 2025
- 19.0.0 16 Jan 2025
- 19.0.0-canary.35e0a98 16 Jan 2025
- 19.0.0-rc.5 10 Jan 2025
- 19.0.0-canary.8ce95bf 10 Jan 2025
- 19.0.0-canary.e567618 09 Jan 2025
- 19.0.0-canary.bc926a8 14 Dec 2024
- 19.0.0-rc.4 13 Dec 2024
- 19.0.0-canary.45ccd39 13 Dec 2024
- 19.0.0-rc.3 13 Dec 2024
- 19.0.0-canary.6b1b0ca 12 Dec 2024
- 19.0.0-rc.2 12 Dec 2024
- 19.0.0-canary.e18d8da 11 Dec 2024
- 19.0.0-rc.1 11 Dec 2024
- 19.0.0-rc.0 20 Nov 2024
- 19.0.0-canary.a58b329 20 Nov 2024
- 18.0.1-canary.a4faa10 19 Nov 2024
- 18.0.1-canary.94e57c6 24 Oct 2024
- 18.0.1-canary.f379433 10 Sep 2024
- 18.0.1-canary.6982c75 06 Aug 2024
- 18.0.1-canary.f283d1a 30 Jul 2024
- 18.0.1-canary.831ab69 15 Jul 2024
- 18.0.1-canary.5a8eeef 15 Jul 2024
- 18.0.1-canary.73e6a0e 15 Jul 2024
- 18.0.1 23 May 2024
- 18.0.1-canary.3639e41 23 May 2024
- 18.0.0-canary.cd18129 23 May 2024
- 18.0.0 22 May 2024
- 18.0.0-canary.bfc27e2 22 May 2024
- 18.0.0-rc.0 22 May 2024
- 18.0.0-canary.c866d08 22 May 2024
- 17.1.0-canary.58e6c3b 16 May 2024
- 17.1.0-canary.827a717 15 May 2024
- 17.1.0 14 May 2024
- 17.1.0-canary.1302e3a 14 May 2024
- 17.0.0-canary.05e9da2 14 May 2024
- 17.0.0-canary.4d322f9 14 May 2024
- 17.0.1 11 Jan 2024
- 17.0.0-canary.73b40da 11 Jan 2024
- 17.0.0 07 Dec 2023
- 17.0.0-canary.8157744 07 Dec 2023
- 17.0.0-canary.6604db7 07 Dec 2023
- 17.0.0-canary.99a1bb1 07 Dec 2023
- 17.0.0-canary.817cf0a 07 Dec 2023
- 17.0.0-next.0 30 Oct 2023
- 17.0.0-canary.4f7932c 30 Oct 2023
- 16.0.0 26 Oct 2023
- 16.0.0-canary.1350920 26 Oct 2023
- 16.0.0-canary.78407bc 25 Oct 2023
- 16.0.0-rc.0 25 Oct 2023
- 16.0.0-canary.2d48ab0 25 Oct 2023
- 16.0.0-canary.5793d6f 01 Sep 2023
- 16.0.0-canary.4172abd 29 Aug 2023
- 16.0.0-canary.596e208 28 Aug 2023
- 16.0.0-canary.e04cd7f 28 Aug 2023
- 7.6.0-canary.34e89a4 11 Jul 2023
- 7.6.0-canary.a26980b 28 Jun 2023
- 7.6.0-canary.8370222 26 Jun 2023
- 7.6.0-canary.60943d6 23 Jun 2023
- 7.6.0-canary.59b95af 23 Jun 2023
- 7.6.0-canary.960dd59 23 Jun 2023
- 7.6.1 27 May 2023
- 7.6.0-canary.b4c3da8 27 May 2023
- 7.6.0 27 May 2023
- 7.6.0-canary.7a2402a 27 May 2023
- 7.5.0-canary.57d9005 23 Nov 2022
The newest 120 of 402 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.
02 Disclosure history
How often vulnerabilities are recorded
No dated vulnerabilities are recorded for this package yet.
Other ways into the data
03 Vulnerabilities
Recorded vulnerabilities for @angular/fire
No vulnerabilities match this view.
Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback
Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315
Questions
About @angular/fire
Is @angular/fire safe to use?
Vulert has no vulnerabilities on record for @angular/fire in npm at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.
What is @angular/fire's Vulert package health score?
Vulert scores @angular/fire 86/100, which reads as healthy. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).
Is the latest version of @angular/fire affected?
No. 20.1.1, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.
How many vulnerabilities does @angular/fire have?
0 vulnerabilities are recorded for @angular/fire in the npm ecosystem: 0 critical, 0 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.
How often are new @angular/fire vulnerabilities disclosed?
0 vulnerabilities were recorded for @angular/fire in the last 12 months. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.
Which versions of @angular/fire are affected?
Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.
How do I monitor @angular/fire for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the @angular/fire version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.