Vulnerability Database · npm · Package report
@firebase/vertexai: vulnerability history, versions and safety
@firebase/vertexai 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 @firebase/vertexai 1.2.4 i
Updated on 23 Oct 2026
Good news: 1.2.4, the version you would install today, has no known vulnerabilities.
- Security No known security issues
- Maintenance Maintaining
- Popularity Niche
- Community Moderate
What to do: Stay on 1.2.4 or newer. This can change: a vulnerability disclosed tomorrow can affect 1.2.4 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release 1.2.4 — 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 5,154 i
- OpenSSF scorecard 6/10 i
- Last release 17 months ago i
- Licence Apache-2.0 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 @firebase/vertexai, 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.
- 1.2.4 14 May 2025
- 1.2.4-20250514221114 14 May 2025
- 1.2.3-firebase-studio-sdk-integration.dd7924e1b 14 May 2025
- 1.2.3 14 May 2025
- 1.2.1-firebase-studio-sdk-integration.12759bc2e 13 May 2025
- 1.2.3-20250513212531 13 May 2025
- 1.2.2-canary.72852e12d 12 May 2025
- 1.2.1-firebase-studio-sdk-integration.0615f555a 12 May 2025
- 1.2.2-canary.d5082f9f2 12 May 2025
- 1.2.1-firebase-studio-sdk-integration.dbac496fa 12 May 2025
- 1.2.2-canary.6be75f74d 12 May 2025
- 1.2.2-canary.8a03143b9 09 May 2025
- 1.2.1-firebase-studio-sdk-integration.a528caf5f 09 May 2025
- 1.2.2-canary.88584fdeb 08 May 2025
- 1.2.2-canary.e99683b17 08 May 2025
- 1.2.2-canary.050c1b6a0 08 May 2025
- 1.2.2-canary.f8334eade 07 May 2025
- 1.2.2-canary.51e7b489d 07 May 2025
- 1.2.2-canary.d5428f3d2 07 May 2025
- 1.2.2 07 May 2025
- 1.2.2-20250507151459 07 May 2025
- 1.2.1-canary.3789b5ad1 07 May 2025
- 1.2.2-20250507150015 07 May 2025
- 1.2.1-firebase-studio-sdk-integration.fe1264c00 06 May 2025
- 1.2.1-firebase-studio-sdk-integration.927daddb8 06 May 2025
- 1.2.1-firebase-studio-sdk-integration.bffdabd70 05 May 2025
- 1.2.1-canary.6a02778e3 05 May 2025
- 1.2.2-20250505162014 05 May 2025
- 1.2.1-canary.080a90dcc 01 May 2025
- 1.2.1-firebase-studio-sdk-integration.9de25069c 30 Apr 2025
- 1.2.1-canary.0e1276649 30 Apr 2025
- 1.2.1-firebase-studio-sdk-integration.226be0bb1 29 Apr 2025
- 1.2.1-eap-vertexai-hybgoog.31261ca31 29 Apr 2025
- 1.2.1-firebase-studio-sdk-integration.1adc0ae1f 29 Apr 2025
- 1.2.1-canary.ea1f9139e 29 Apr 2025
- 1.2.1-canary.dd6a8f076 29 Apr 2025
- 1.2.1-canary.0e2558a96 28 Apr 2025
- 1.2.1-eap-vertexai-hybgoog.dc3794a2b 28 Apr 2025
- 1.2.1-auth-redirect-credentials.b424e5897 25 Apr 2025
- 1.2.1-auth-redirect-credentials.82faa0828 25 Apr 2025
- 1.2.1-canary.9952dbc2d 24 Apr 2025
- 1.2.1-ssl-check.4f23f3343 23 Apr 2025
- 1.2.1-eap-vertexai-hybgoog.abf0491ae 23 Apr 2025
- 1.2.1-canary.20b45d3ab 23 Apr 2025
- 1.2.1-eap-vertexai-hybridinference.e83974308 23 Apr 2025
- 1.2.1-eap-vertexai-hybridinference.5fa83b371 22 Apr 2025
- 1.2.1-eap-vertexai-hybridinference.43a69d5da 22 Apr 2025
- 1.2.1-eap-vertexai-hybridinference.3d7df8b90 21 Apr 2025
- 1.2.1-canary.1363ecc53 16 Apr 2025
- 1.2.1-canary.8bb66c28b 15 Apr 2025
- 1.2.1-canary.0cbff6bc7 15 Apr 2025
- 1.2.1-canary.e055e9057 14 Apr 2025
- 1.2.1-canary.ed0803a29 11 Apr 2025
- 1.2.0-eap-vertexai-hybridinference.dcc62c031 09 Apr 2025
- 1.2.1-canary.4e0f630e7 09 Apr 2025
- 1.2.1-canary.b3328250d 09 Apr 2025
- 1.2.1-canary.66a09f247 08 Apr 2025
- 1.2.1-canary.1df3d26fb 04 Apr 2025
- 1.2.1-canary.88a805580 01 Apr 2025
- 1.2.1-canary.933ba9d3c 31 Mar 2025
- 1.2.1 31 Mar 2025
- 1.2.0-canary.c8cbfff16 29 Mar 2025
- 1.2.0-canary.61f0102ac 28 Mar 2025
- 1.2.0-canary.195d94310 28 Mar 2025
- 1.2.1-20250327233251 27 Mar 2025
- 1.2.0-canary.fb5d42275 27 Mar 2025
- 1.2.0-canary.670eba607 27 Mar 2025
- 1.2.0-canary.dcc62c031 25 Mar 2025
- 1.2.0-canary.ab8eb26ce 25 Mar 2025
- 1.2.0-canary.648de84b0 25 Mar 2025
- 1.2.0-canary.edb40010b 21 Mar 2025
- 1.2.0-canary.571883817 20 Mar 2025
- 1.2.0-canary.14d97210c 20 Mar 2025
- 1.2.0-canary.faaeb48e0 20 Mar 2025
- 1.2.0-canary.202c7328f 20 Mar 2025
- 1.2.0 20 Mar 2025
- 1.2.0-20250318174027 18 Mar 2025
- 1.1.0-canary.e8865f241 18 Mar 2025
- 1.2.0-20250318151245 18 Mar 2025
- 1.1.0-canary.cf3c8fb2a 18 Mar 2025
- 1.2.0-20250318143520 18 Mar 2025
- 1.2.0-20250318131644 18 Mar 2025
- 1.1.0-canary.95b4fc69d 17 Mar 2025
- 1.1.0-canary.a512bc655 17 Mar 2025
- 1.1.0-canary.feb2c9dfa 10 Mar 2025
- 1.1.0-canary.51465ce87 06 Mar 2025
- 1.1.0-canary.561117597 06 Mar 2025
- 1.1.0-canary.33acc6e3c 06 Mar 2025
- 1.1.0-canary.25985ac3c 06 Mar 2025
- 1.1.0-canary.42cea4810 05 Mar 2025
- 1.1.0-canary.058afa280 04 Mar 2025
- 1.1.0-canary.7ae48246b 03 Mar 2025
- 1.1.0-canary.43d6b6735 03 Mar 2025
- 1.1.0-canary.a24a76aa2 27 Feb 2025
- 1.1.0 27 Feb 2025
- 1.0.4-canary.113c965a3 27 Feb 2025
- 1.1.0-20250226175635 26 Feb 2025
- 1.0.4-canary.777f465ff 26 Feb 2025
- 1.0.4-canary.2d74e5bfb 26 Feb 2025
- 1.0.4-canary.117279e27 26 Feb 2025
- 1.1.0-20250226000544 26 Feb 2025
- 1.0.4-canary.dcfb3da2e 24 Feb 2025
- 1.0.4-canary.1daf8b47b 24 Feb 2025
- 1.0.4-canary.9d8266593 24 Feb 2025
- 1.0.4-canary.ce2c77511 21 Feb 2025
- 1.0.4-canary.c3266f8d7 20 Feb 2025
- 1.0.4-canary.604133f8d 19 Feb 2025
- 1.0.4-canary.84dfeca39 19 Feb 2025
- 1.0.4-canary.f68148253 19 Feb 2025
- 1.0.4-canary.884cbd7d8 18 Feb 2025
- 1.0.5-20250214170153 14 Feb 2025
- 1.0.4-canary.b92592d98 13 Feb 2025
- 1.0.4-canary.554c7bdc1 12 Feb 2025
- 1.0.4-canary.c8e5b3e77 12 Feb 2025
- 1.0.4-canary.6a28a72eb 12 Feb 2025
- 1.0.4-canary.c791ecf3a 11 Feb 2025
- 1.0.4-canary.70e08cf95 11 Feb 2025
- 1.0.4-canary.b3e68ca41 11 Feb 2025
- 1.0.4-canary.69c33266d 11 Feb 2025
- 1.0.4-canary.3418ef807 11 Feb 2025
The newest 120 of 206 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 @firebase/vertexai
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 @firebase/vertexai
Is @firebase/vertexai safe to use?
Vulert has no vulnerabilities on record for @firebase/vertexai 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 @firebase/vertexai's Vulert package health score?
Vulert scores @firebase/vertexai 76/100, which reads as in good shape. 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 @firebase/vertexai affected?
No. 1.2.4, 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.
Which version of @firebase/vertexai should I use?
1.2.4 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.
How many vulnerabilities does @firebase/vertexai have?
0 vulnerabilities are recorded for @firebase/vertexai 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 @firebase/vertexai vulnerabilities disclosed?
0 vulnerabilities were recorded for @firebase/vertexai 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 @firebase/vertexai 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 @firebase/vertexai for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the @firebase/vertexai version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.