Vulnerability Database · npm · Package report

@google-cloud/translate: vulnerability history, versions and safety

@google-cloud/translate is a package in the npm ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the npm ecosystem.

i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on @google-cloud/translate 10.3.0 i

Updated on 23 Oct 2026

Good news: 10.3.0, the version you would install today, has no known vulnerabilities.

Package health score 83/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Moderate

What to do: Stay on 10.3.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 10.3.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 10.3.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 8 packages i
  • Stars 3,210 i
  • OpenSSF scorecard 5/10 i
  • Last release this month 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 @google-cloud/translate, 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.

i
Version Released Vulert vulnerabilities Licence Fix published Details
10.3.0 12 Oct 2026 none Apache-2.0 — Details →
10.2.0 07 Oct 2026 none Apache-2.0 — Details →
10.1.1 28 Sep 2026 none Apache-2.0 — Details →
10.1.0 08 Sep 2026 none Apache-2.0 — Details →
10.0.1 12 Aug 2026 none Apache-2.0 — Details →
9.4.2 04 Jun 2026 none Apache-2.0 — Details →
9.4.1 01 May 2026 none Apache-2.0 — Details →
9.3.0 11 Nov 2025 none Apache-2.0 — Details →
9.2.1 13 Oct 2025 none Apache-2.0 — Details →
9.2.0 10 Jul 2025 none Apache-2.0 — Details →
9.1.0 13 May 2025 none Apache-2.0 — Details →
9.0.1 20 Mar 2025 none Apache-2.0 — Details →
9.0.0 18 Mar 2025 none Apache-2.0 — Details →
8.5.1 26 Feb 2025 none Apache-2.0 — Details →
8.5.0 20 Aug 2024 none Apache-2.0 — Details →
8.4.0 12 Aug 2024 none Apache-2.0 — Details →
8.3.0 21 May 2024 none Apache-2.0 — Details →
8.2.0 02 Apr 2024 none Apache-2.0 — Details →
8.1.0 13 Feb 2024 none Apache-2.0 — Details →
8.0.3 11 Jan 2024 none Apache-2.0 — Details →
8.0.2 06 Sep 2023 none Apache-2.0 — Details →
8.0.1 10 Aug 2023 none Apache-2.0 — Details →
8.0.0 07 Aug 2023 none Apache-2.0 — Details →
7.2.2 28 Jun 2023 none Apache-2.0 — Details →
7.2.1 14 Apr 2023 none Apache-2.0 — Details →
7.2.0 23 Feb 2023 none Apache-2.0 — Details →
7.1.1 16 Feb 2023 none Apache-2.0 — Details →
7.1.0 30 Jan 2023 none Apache-2.0 — Details →
7.0.5 20 Dec 2022 none Apache-2.0 — Details →
7.0.4 09 Nov 2022 none Apache-2.0 — Details →
7.0.3 22 Sep 2022 none Apache-2.0 — Details →
7.0.2 07 Sep 2022 none Apache-2.0 — Details →
7.0.1 10 Aug 2022 none Apache-2.0 — Details →
7.0.0 30 Jun 2022 none Apache-2.0 — Details →
6.3.1 18 Oct 2021 none Apache-2.0 — Details →
6.3.0 16 Sep 2021 none Apache-2.0 — Details →
6.2.7 17 Aug 2021 none Apache-2.0 — Details →
6.2.6 21 Jul 2021 none Apache-2.0 — Details →
6.2.5 12 Jul 2021 none Apache-2.0 — Details →
6.2.4 29 Jun 2021 none Apache-2.0 — Details →
6.2.3 24 Jun 2021 none Apache-2.0 — Details →
6.2.2 03 Jun 2021 none Apache-2.0 — Details →
6.2.1 11 May 2021 none Apache-2.0 — Details →
6.2.0 07 Apr 2021 none Apache-2.0 — Details →
6.1.0 12 Jan 2021 none Apache-2.0 — Details →
6.0.5 08 Dec 2020 none Apache-2.0 — Details →
6.0.4 16 Nov 2020 none Apache-2.0 — Details →
6.0.3 17 Sep 2020 none Apache-2.0 — Details →
6.0.2 15 Jul 2020 none Apache-2.0 — Details →
6.0.1 29 Jun 2020 none Apache-2.0 — Details →
6.0.0 04 Jun 2020 none Apache-2.0 — Details →
5.3.0 11 Mar 2020 none Apache-2.0 — Details →
5.2.0 27 Feb 2020 none Apache-2.0 — Details →
5.1.6 07 Feb 2020 none Apache-2.0 — Details →
5.1.5 05 Feb 2020 none Apache-2.0 — Details →
5.1.4 06 Jan 2020 none Apache-2.0 — Details →
5.1.3 17 Dec 2019 none Apache-2.0 — Details →
5.1.2 11 Dec 2019 none Apache-2.0 — Details →
5.1.1 05 Dec 2019 none Apache-2.0 — Details →
5.1.0 22 Nov 2019 none Apache-2.0 — Details →
5.0.2 08 Nov 2019 none Apache-2.0 — Details →
5.0.1 28 Oct 2019 none Apache-2.0 — Details →
5.0.0 28 Oct 2019 none Apache-2.0 — Details →
4.2.1 22 Oct 2019 none Apache-2.0 — Details →
4.2.0 14 Oct 2019 none Apache-2.0 — Details →
4.1.3 05 Aug 2019 none Apache-2.0 — Details →
4.1.2 23 Jul 2019 none Apache-2.0 — Details →
4.1.1 01 Jul 2019 none Apache-2.0 — Details →
4.1.0 14 Jun 2019 none Apache-2.0 — Details →
4.0.1 20 May 2019 none Apache-2.0 — Details →
4.0.0 13 May 2019 none Apache-2.0 — Details →
3.0.1 09 Apr 2019 none Apache-2.0 — Details →
3.0.0 02 Apr 2019 none Apache-2.0 — Details →
2.1.4 12 Mar 2019 none Apache-2.0 — Details →
2.1.3 08 Dec 2018 none Apache-2.0 — Details →
2.1.2 21 Sep 2018 none Apache-2.0 — Details →
2.1.1 05 Sep 2018 none Apache-2.0 — Details →
1.1.0 25 Oct 2017 none Apache-2.0 — Details →
1.0.0 05 Jul 2017 none Apache-2.0 — Details →
0.8.2 13 May 2017 none Apache-2.0 — Details →
0.8.1 14 Apr 2017 none Apache-2.0 — Details →
0.8.0 31 Mar 2017 none Apache-2.0 — Details →
0.7.0 02 Feb 2017 none Apache-2.0 — Details →
0.6.1 10 Jan 2017 none Apache-2.0 — Details →
0.5.3 10 Jan 2017 none Apache-2.0 — Details →
0.5.2 10 Jan 2017 none Apache-2.0 — Details →
0.6.0 09 Dec 2016 none Apache-2.0 — Details →
0.5.1 16 Nov 2016 none Apache-2.0 — Details →
0.5.0 15 Nov 2016 none Apache-2.0 — Details →
0.4.0 17 Oct 2016 none Apache-2.0 — Details →
0.3.0 26 Sep 2016 none Apache-2.0 — Details →
0.2.0 30 Aug 2016 none Apache-2.0 — Details →
0.1.1 11 Aug 2016 none Apache-2.0 — Details →
0.1.0 11 Aug 2016 none Apache-2.0 — Details →

All 94 versions Vulert tracks for this package. 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.

03 Vulnerabilities

Recorded vulnerabilities for @google-cloud/translate

No vulnerability write-ups match this view

Search all 0 in the database →

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

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About @google-cloud/translate

Is @google-cloud/translate safe to use?

Vulert has no vulnerabilities on record for @google-cloud/translate 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 @google-cloud/translate's Vulert package health score?

Vulert scores @google-cloud/translate 83/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 @google-cloud/translate affected?

No. 10.3.0, 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 @google-cloud/translate have?

0 vulnerabilities are recorded for @google-cloud/translate 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 @google-cloud/translate vulnerabilities disclosed?

0 vulnerabilities were recorded for @google-cloud/translate 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 @google-cloud/translate 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 @google-cloud/translate for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the @google-cloud/translate version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.