Vulnerability Database · npm · Package report

@types/serviceworker: vulnerability history, versions and safety

@types/serviceworker 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 @types/serviceworker 0.0.203 i

Updated on 23 Oct 2026

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

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

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

  • Current release 0.0.203 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 743 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 @types/serviceworker, 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.0.203 06 Oct 2026 none Apache-2.0 — Details →
0.0.202 20 Sep 2026 none Apache-2.0 — Details →
0.0.201 05 Sep 2026 none Apache-2.0 — Details →
0.0.200 19 Jul 2026 none Apache-2.0 — Details →
0.0.199 30 Jun 2026 none Apache-2.0 — Details →
0.0.198 29 Jun 2026 none Apache-2.0 — Details →
0.0.197 02 May 2026 none Apache-2.0 — Details →
0.0.196 30 Apr 2026 none Apache-2.0 — Details →
0.0.195 20 Apr 2026 none Apache-2.0 — Details →
0.0.194 19 Mar 2026 none Apache-2.0 — Details →
0.0.193 02 Mar 2026 none Apache-2.0 — Details →
0.0.192 23 Feb 2026 none Apache-2.0 — Details →
0.0.191 16 Feb 2026 none Apache-2.0 — Details →
0.0.190 15 Feb 2026 none Apache-2.0 — Details →
0.0.189 14 Feb 2026 none Apache-2.0 — Details →
0.0.188 13 Feb 2026 none Apache-2.0 — Details →
0.0.187 12 Feb 2026 none Apache-2.0 — Details →
0.0.186 10 Feb 2026 none Apache-2.0 — Details →
0.0.185 09 Feb 2026 none Apache-2.0 — Details →
0.0.184 08 Feb 2026 none Apache-2.0 — Details →
0.0.183 04 Feb 2026 none Apache-2.0 — Details →
0.0.182 31 Jan 2026 none Apache-2.0 — Details →
0.0.181 26 Jan 2026 none Apache-2.0 — Details →
0.0.180 23 Jan 2026 none Apache-2.0 — Details →
0.0.179 22 Jan 2026 none Apache-2.0 — Details →
0.0.178 21 Jan 2026 none Apache-2.0 — Details →
0.0.177 20 Jan 2026 none Apache-2.0 — Details →
0.0.176 12 Jan 2026 none Apache-2.0 — Details →
0.0.175 11 Jan 2026 none Apache-2.0 — Details →
0.0.174 10 Jan 2026 none Apache-2.0 — Details →
0.0.173 08 Jan 2026 none Apache-2.0 — Details →
0.0.172 25 Dec 2025 none Apache-2.0 — Details →
0.0.171 24 Dec 2025 none Apache-2.0 — Details →
0.0.170 20 Dec 2025 none Apache-2.0 — Details →
0.0.169 18 Dec 2025 none Apache-2.0 — Details →
0.0.168 05 Dec 2025 none Apache-2.0 — Details →
0.0.167 08 Nov 2025 none Apache-2.0 — Details →
0.0.166 07 Nov 2025 none Apache-2.0 — Details →
0.0.165 05 Nov 2025 none Apache-2.0 — Details →
0.0.164 02 Nov 2025 none Apache-2.0 — Details →
0.0.163 01 Nov 2025 none Apache-2.0 — Details →
0.0.162 31 Oct 2025 none Apache-2.0 — Details →
0.0.161 29 Oct 2025 none Apache-2.0 — Details →
0.0.160 26 Oct 2025 none Apache-2.0 — Details →
0.0.159 24 Oct 2025 none Apache-2.0 — Details →
0.0.158 06 Oct 2025 none Apache-2.0 — Details →
0.0.157 04 Oct 2025 none Apache-2.0 — Details →
0.0.156 03 Oct 2025 none Apache-2.0 — Details →
0.0.155 02 Oct 2025 none Apache-2.0 — Details →
0.0.154 27 Sep 2025 none Apache-2.0 — Details →
0.0.153 17 Sep 2025 none Apache-2.0 — Details →
0.0.152 28 Aug 2025 none Apache-2.0 — Details →
0.0.151 27 Aug 2025 none Apache-2.0 — Details →
0.0.150 18 Aug 2025 none Apache-2.0 — Details →
0.0.149 03 Aug 2025 none Apache-2.0 — Details →
0.0.148 01 Aug 2025 none Apache-2.0 — Details →
0.0.147 27 Jul 2025 none Apache-2.0 — Details →
0.0.146 22 Jul 2025 none Apache-2.0 — Details →
0.0.145 21 Jul 2025 none Apache-2.0 — Details →
0.0.144 20 Jul 2025 none Apache-2.0 — Details →
0.0.143 18 Jul 2025 none Apache-2.0 — Details →
0.0.142 15 Jul 2025 none Apache-2.0 — Details →
0.0.141 08 Jul 2025 none Apache-2.0 — Details →
0.0.140 29 Jun 2025 none Apache-2.0 — Details →
0.0.139 05 Jun 2025 none Apache-2.0 — Details →
0.0.138 04 Jun 2025 none Apache-2.0 — Details →
0.0.137 01 Jun 2025 none Apache-2.0 — Details →
0.0.136 29 May 2025 none Apache-2.0 — Details →
0.0.135 15 May 2025 none Apache-2.0 — Details →
0.0.134 09 May 2025 none Apache-2.0 — Details →
0.0.133 03 May 2025 none Apache-2.0 — Details →
0.0.132 23 Apr 2025 none Apache-2.0 — Details →
0.0.131 19 Apr 2025 none Apache-2.0 — Details →
0.0.130 18 Apr 2025 none Apache-2.0 — Details →
0.0.129 16 Apr 2025 none Apache-2.0 — Details →
0.0.128 15 Apr 2025 none Apache-2.0 — Details →
0.0.127 27 Mar 2025 none Apache-2.0 — Details →
0.0.126 15 Mar 2025 none Apache-2.0 — Details →
0.0.125 14 Mar 2025 none Apache-2.0 — Details →
0.0.124 13 Mar 2025 none Apache-2.0 — Details →
0.0.123 27 Feb 2025 none Apache-2.0 — Details →
0.0.122 23 Feb 2025 none Apache-2.0 — Details →
0.0.121 21 Feb 2025 none Apache-2.0 — Details →
0.0.120 09 Feb 2025 none Apache-2.0 — Details →
0.0.119 04 Feb 2025 none Apache-2.0 — Details →
0.0.118 29 Jan 2025 none Apache-2.0 — Details →
0.0.117 27 Jan 2025 none Apache-2.0 — Details →
0.0.116 24 Jan 2025 none Apache-2.0 — Details →
0.0.115 23 Jan 2025 none Apache-2.0 — Details →
0.0.114 18 Jan 2025 none Apache-2.0 — Details →
0.0.113 16 Jan 2025 none Apache-2.0 — Details →
0.0.112 14 Jan 2025 none Apache-2.0 — Details →
0.0.111 12 Jan 2025 none Apache-2.0 — Details →
0.0.110 09 Jan 2025 none Apache-2.0 — Details →
0.0.109 07 Jan 2025 none Apache-2.0 — Details →
0.0.108 24 Dec 2024 none Apache-2.0 — Details →
0.0.107 30 Nov 2024 none Apache-2.0 — Details →
0.0.106 24 Nov 2024 none Apache-2.0 — Details →
0.0.105 22 Nov 2024 none Apache-2.0 — Details →
0.0.104 21 Nov 2024 none Apache-2.0 — Details →
0.0.103 14 Nov 2024 none — — Details →
0.0.102 03 Nov 2024 none — — Details →
0.0.101 20 Oct 2024 none — — Details →
0.0.100 17 Oct 2024 none — — Details →
0.0.99 13 Oct 2024 none — — Details →
0.0.98 10 Oct 2024 none — — Details →
0.0.97 29 Sep 2024 none — — Details →
0.0.96 22 Sep 2024 none — — Details →
0.0.95 06 Sep 2024 none — — Details →
0.0.94 24 Aug 2024 none — — Details →
0.0.93 23 Aug 2024 none — — Details →
0.0.92 09 Aug 2024 none — — Details →
0.0.91 02 Aug 2024 none — — Details →
0.0.90 29 Jul 2024 none — — Details →
0.0.89 04 Jul 2024 none — — Details →
0.0.88 26 Jun 2024 none — — Details →
0.0.87 15 Jun 2024 none — — Details →
0.0.86 10 May 2024 none — — Details →
0.0.85 15 Apr 2024 none — — Details →
0.0.84 11 Mar 2024 none — — Details →

The newest 120 of 203 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/serviceworker

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/serviceworker

Is @types/serviceworker safe to use?

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

Vulert scores @types/serviceworker 78/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/serviceworker affected?

No. 0.0.203, 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 @types/serviceworker should I use?

0.0.203 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 @types/serviceworker have?

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

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

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