VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@types/chrome: vulnerability history, versions and safety

@types/chrome 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.

See all @types/chrome vulnerabilities

Vulert verdict on @types/chrome 0.3.6 i

Updated on 23 Oct 2026

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

Package health score 84/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

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

  • Current release 0.3.6 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 42 packages i
  • Stars 51,449 i
  • OpenSSF scorecard 4/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 @types/chrome, 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
0.3.6 21 Oct 2026 none MIT — Details →
0.3.5 09 Oct 2026 none MIT — Details →
0.3.4 29 Sep 2026 none MIT — Details →
0.3.3 28 Sep 2026 none MIT — Details →
0.3.2 28 Sep 2026 none MIT — Details →
0.3.1 28 Sep 2026 none MIT — Details →
0.3.0 15 Sep 2026 none MIT — Details →
0.2.9 05 Sep 2026 none MIT — Details →
0.2.8 01 Sep 2026 none MIT — Details →
0.2.7 21 Aug 2026 none MIT — Details →
0.2.6 13 Aug 2026 none MIT — Details →
0.2.5 31 Jul 2026 none MIT — Details →
0.2.4 31 Jul 2026 none MIT — Details →
0.2.3 31 Jul 2026 none MIT — Details →
0.2.2 01 Jul 2026 none MIT — Details →
0.2.1 01 Jul 2026 none MIT — Details →
0.2.0 20 Jun 2026 none MIT — Details →
0.1.43 05 Jun 2026 none MIT — Details →
0.1.42 07 May 2026 none MIT — Details →
0.1.41 07 May 2026 none MIT — Details →
0.1.40 08 Apr 2026 none MIT — Details →
0.1.39 03 Apr 2026 none MIT — Details →
0.1.38 16 Mar 2026 none MIT — Details →
0.1.37 20 Feb 2026 none MIT — Details →
0.1.36 21 Jan 2026 none MIT — Details →
0.1.35 20 Jan 2026 none MIT — Details →
0.1.34 19 Jan 2026 none MIT — Details →
0.1.33 10 Jan 2026 none MIT — Details →
0.1.32 01 Dec 2025 none MIT — Details →
0.1.31 19 Nov 2025 none MIT — Details →
0.1.30 17 Nov 2025 none MIT — Details →
0.1.29 14 Nov 2025 none MIT — Details →
0.1.28 11 Nov 2025 none MIT — Details →
0.1.27 27 Oct 2025 none MIT — Details →
0.1.26 27 Oct 2025 none MIT — Details →
0.1.25 27 Oct 2025 none MIT — Details →
0.1.24 11 Oct 2025 none MIT — Details →
0.1.23 11 Oct 2025 none MIT — Details →
0.1.22 03 Oct 2025 none MIT — Details →
0.1.21 03 Oct 2025 none MIT — Details →
0.1.20 03 Oct 2025 none MIT — Details →
0.1.19 02 Oct 2025 none MIT — Details →
0.1.18 02 Oct 2025 none MIT — Details →
0.1.17 01 Oct 2025 none MIT — Details →
0.1.16 30 Sep 2025 none MIT — Details →
0.1.15 30 Sep 2025 none MIT — Details →
0.1.14 29 Sep 2025 none MIT — Details →
0.1.13 29 Sep 2025 none MIT — Details →
0.1.12 16 Sep 2025 none MIT — Details →
0.1.11 12 Sep 2025 none MIT — Details →
0.1.10 12 Sep 2025 none MIT — Details →
0.1.9 08 Sep 2025 none MIT — Details →
0.1.8 08 Sep 2025 none MIT — Details →
0.1.7 08 Sep 2025 none MIT — Details →
0.1.6 03 Sep 2025 none MIT — Details →
0.1.5 03 Sep 2025 none MIT — Details →
0.1.4 14 Aug 2025 none MIT — Details →
0.1.3 08 Aug 2025 none MIT — Details →
0.1.2 08 Aug 2025 none MIT — Details →
0.1.1 16 Jul 2025 none MIT — Details →
0.1.0 11 Jul 2025 none MIT — Details →
0.0.332 09 Jul 2025 none MIT — Details →
0.0.331 08 Jul 2025 none MIT — Details →
0.0.330 08 Jul 2025 none MIT — Details →
0.0.329 01 Jul 2025 none MIT — Details →
0.0.328 28 Jun 2025 none MIT — Details →
0.0.327 27 Jun 2025 none MIT — Details →
0.0.326 31 May 2025 none MIT — Details →
0.0.325 30 May 2025 none MIT — Details →
0.0.324 30 May 2025 none MIT — Details →
0.0.323 16 May 2025 none MIT — Details →
0.0.322 12 May 2025 none MIT — Details →
0.0.321 09 May 2025 none MIT — Details →
0.0.320 05 May 2025 none MIT — Details →
0.0.319 04 May 2025 none MIT — Details →
0.0.318 01 May 2025 none MIT — Details →
0.0.317 24 Apr 2025 none MIT — Details →
0.0.316 22 Apr 2025 none MIT — Details →
0.0.315 11 Apr 2025 none MIT — Details →
0.0.314 11 Apr 2025 none MIT — Details →
0.0.313 27 Mar 2025 none MIT — Details →
0.0.312 25 Mar 2025 none MIT — Details →
0.0.311 25 Mar 2025 none MIT — Details →
0.0.310 20 Mar 2025 none MIT — Details →
0.0.309 11 Mar 2025 none MIT — Details →
0.0.308 04 Mar 2025 none MIT — Details →
0.0.307 28 Feb 2025 none MIT — Details →
0.0.306 21 Feb 2025 none MIT — Details →
0.0.305 21 Feb 2025 none MIT — Details →
0.0.304 08 Feb 2025 none MIT — Details →
0.0.303 08 Feb 2025 none MIT — Details →
0.0.302 07 Feb 2025 none MIT — Details →
0.0.301 03 Feb 2025 none MIT — Details →
0.0.300 30 Jan 2025 none MIT — Details →
0.0.299 21 Jan 2025 none MIT — Details →
0.0.298 20 Jan 2025 none MIT — Details →
0.0.297 16 Jan 2025 none MIT — Details →
0.0.296 14 Jan 2025 none MIT — Details →
0.0.295 14 Jan 2025 none MIT — Details →
0.0.294 14 Jan 2025 none MIT — Details →
0.0.293 09 Jan 2025 none — — Details →
0.0.292 09 Jan 2025 none — — Details →
0.0.291 08 Jan 2025 none — — Details →
0.0.290 06 Jan 2025 none — — Details →
0.0.289 02 Jan 2025 none — — Details →
0.0.288 02 Jan 2025 none — — Details →
0.0.287 26 Nov 2024 none — — Details →
0.0.286 26 Nov 2024 none — — Details →
0.0.285 25 Nov 2024 none — — Details →
0.0.284 24 Nov 2024 none — — Details →
0.0.283 15 Nov 2024 none — — Details →
0.0.282 15 Nov 2024 none — — Details →
0.0.281 14 Nov 2024 none — — Details →
0.0.280 01 Nov 2024 none — — Details →
0.0.279 21 Oct 2024 none — — Details →
0.0.278 14 Oct 2024 none — — Details →
0.0.277 04 Oct 2024 none — — Details →
0.0.276 03 Oct 2024 none — — Details →
0.0.275 02 Oct 2024 none — — Details →
0.0.274 02 Oct 2024 none — — Details →

The newest 120 of 375 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.

03 Vulnerabilities

Recorded vulnerabilities for @types/chrome

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 @types/chrome

Is @types/chrome safe to use?

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

Vulert scores @types/chrome 84/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 @types/chrome affected?

No. 0.3.6, 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 @types/chrome have?

0 vulnerabilities are recorded for @types/chrome 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 @types/chrome vulnerabilities disclosed?

0 vulnerabilities were recorded for @types/chrome 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 @types/chrome 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 @types/chrome for upcoming vulnerabilities?

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