Vulnerability Database · npm · Package report

@swc/plugin-styled-components: vulnerability history, versions and safety

@swc/plugin-styled-components 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 @swc/plugin-styled-components 17.0.0 i

Updated on 23 Oct 2026

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

Package health score 82/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Moderate

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

  • Current release 17.0.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 387 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 @swc/plugin-styled-components, 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
17.0.0 06 Oct 2026 none Apache-2.0 — Details →
16.0.0 06 Oct 2026 none Apache-2.0 — Details →
15.0.0 27 Sep 2026 none Apache-2.0 — Details →
14.0.0 04 Sep 2026 none Apache-2.0 — Details →
13.0.0 15 Aug 2026 none Apache-2.0 — Details →
12.19.0 12 Aug 2026 none Apache-2.0 — Details →
12.15.0 06 Jul 2026 none Apache-2.0 — Details →
12.14.1 01 Jul 2026 none Apache-2.0 — Details →
12.14.0 21 Jun 2026 none Apache-2.0 — Details →
12.13.0 17 Jun 2026 none Apache-2.0 — Details →
12.12.1 31 May 2026 none Apache-2.0 — Details →
12.12.0 30 May 2026 none Apache-2.0 — Details →
12.11.0 27 May 2026 none Apache-2.0 — Details →
12.10.0 21 May 2026 none Apache-2.0 — Details →
12.9.0 27 Apr 2026 none Apache-2.0 — Details →
12.8.0 03 Apr 2026 none Apache-2.0 — Details →
12.7.0 26 Feb 2026 none Apache-2.0 — Details →
12.6.0 17 Feb 2026 none Apache-2.0 — Details →
12.5.0 27 Jan 2026 none Apache-2.0 — Details →
12.4.0 23 Jan 2026 none Apache-2.0 — Details →
12.3.0 26 Dec 2025 none Apache-2.0 — Details →
12.2.0 25 Dec 2025 none Apache-2.0 — Details →
12.1.0 18 Dec 2025 none Apache-2.0 — Details →
12.0.1 27 Nov 2025 none Apache-2.0 — Details →
12.0.0 24 Nov 2025 none Apache-2.0 — Details →
11.1.0 19 Nov 2025 none Apache-2.0 — Details →
11.0.0 04 Nov 2025 none Apache-2.0 — Details →
10.0.0 29 Oct 2025 none Apache-2.0 — Details →
9.5.0 23 Oct 2025 none Apache-2.0 — Details →
9.1.0 02 Sep 2025 none Apache-2.0 — Details →
9.0.4 02 Sep 2025 none Apache-2.0 — Details →
9.0.3 05 Aug 2025 none Apache-2.0 — Details →
9.0.2 31 Jul 2025 none Apache-2.0 — Details →
9.0.0 18 Jul 2025 none Apache-2.0 — Details →
8.0.4 16 Jul 2025 none Apache-2.0 — Details →
8.0.3 07 Jul 2025 none Apache-2.0 — Details →
8.0.2 19 Jun 2025 none Apache-2.0 — Details →
8.0.1 18 Jun 2025 none Apache-2.0 — Details →
8.0.0 10 Jun 2025 none Apache-2.0 — Details →
7.1.5 12 May 2025 none Apache-2.0 — Details →
7.1.4 06 May 2025 none Apache-2.0 — Details →
7.1.3 14 Apr 2025 none Apache-2.0 — Details →
7.1.2 08 Apr 2025 none Apache-2.0 — Details →
7.1.1 04 Apr 2025 none Apache-2.0 — Details →
7.1.0 12 Mar 2025 none Apache-2.0 — Details →
7.0.0 24 Feb 2025 none Apache-2.0 — Details →
6.8.2 21 Feb 2025 none Apache-2.0 — Details →
6.7.0 29 Jan 2025 none Apache-2.0 — Details →
6.6.0 28 Jan 2025 none Apache-2.0 — Details →
6.5.0 26 Jan 2025 none Apache-2.0 — Details →
6.4.0 26 Jan 2025 none Apache-2.0 — Details →
6.3.0 24 Jan 2025 none Apache-2.0 — Details →
6.1.0 24 Jan 2025 none Apache-2.0 — Details →
6.0.4 16 Jan 2025 none Apache-2.0 — Details →
6.0.3 07 Jan 2025 none Apache-2.0 — Details →
6.0.2 09 Dec 2024 none Apache-2.0 — Details →
6.0.1 04 Dec 2024 none Apache-2.0 — Details →
5.0.2 04 Dec 2024 none Apache-2.0 — Details →
5.0.0 06 Nov 2024 none Apache-2.0 — Details →
4.0.0 01 Nov 2024 none Apache-2.0 — Details →
3.0.3 14 Oct 2024 none Apache-2.0 — Details →
3.0.2 25 Sep 2024 none Apache-2.0 — Details →
3.0.1 02 Sep 2024 none Apache-2.0 — Details →
3.0.0 26 Aug 2024 none Apache-2.0 — Details →
2.0.12 18 Aug 2024 none Apache-2.0 — Details →
2.0.11 06 Aug 2024 none Apache-2.0 — Details →
2.0.10 18 Jul 2024 none Apache-2.0 — Details →
2.0.9 01 Jul 2024 none Apache-2.0 — Details →
2.0.8 15 Jun 2024 none Apache-2.0 — Details →
2.0.7 07 Jun 2024 none Apache-2.0 — Details →
2.0.6 14 May 2024 none Apache-2.0 — Details →
2.0.5 08 May 2024 none Apache-2.0 — Details →
2.0.4 08 May 2024 none Apache-2.0 — Details →
2.0.3 07 May 2024 none Apache-2.0 — Details →
2.0.2 29 Apr 2024 none Apache-2.0 — Details →
2.0.1 27 Apr 2024 none Apache-2.0 — Details →
2.0.0 24 Apr 2024 none Apache-2.0 — Details →
1.5.122 28 Mar 2024 none Apache-2.0 — Details →
1.5.121 26 Mar 2024 none Apache-2.0 — Details →
1.5.119 18 Mar 2024 none Apache-2.0 — Details →
1.5.118 08 Feb 2024 none Apache-2.0 — Details →
1.5.117 07 Feb 2024 none Apache-2.0 — Details →
1.5.116 05 Feb 2024 none Apache-2.0 — Details →
1.5.115 24 Jan 2024 none Apache-2.0 — Details →
1.5.114 21 Jan 2024 none Apache-2.0 — Details →
1.5.113 21 Jan 2024 none Apache-2.0 — Details →
1.5.111 20 Jan 2024 none Apache-2.0 — Details →
1.5.110 18 Jan 2024 none Apache-2.0 — Details →
1.5.109 18 Jan 2024 none Apache-2.0 — Details →
1.5.108 21 Dec 2023 none Apache-2.0 — Details →
1.5.105 28 Nov 2023 none Apache-2.0 — Details →
1.5.104 26 Nov 2023 none Apache-2.0 — Details →
1.5.103 26 Nov 2023 none Apache-2.0 — Details →
1.5.102 25 Nov 2023 none Apache-2.0 — Details →
1.5.101 25 Nov 2023 none Apache-2.0 — Details →
1.5.100 23 Nov 2023 none Apache-2.0 — Details →
1.5.99 22 Nov 2023 none Apache-2.0 — Details →
1.5.98 14 Nov 2023 none Apache-2.0 — Details →
1.5.97 07 Nov 2023 none Apache-2.0 — Details →
1.5.96 30 Oct 2023 none Apache-2.0 — Details →
1.5.95 30 Oct 2023 none — — Details →
1.5.94 25 Oct 2023 none — — Details →
1.5.93 24 Oct 2023 none — — Details →
1.5.92 16 Oct 2023 none — — Details →
1.5.87 25 Sep 2023 none — — Details →
1.5.86 21 Sep 2023 none — — Details →
1.5.84 21 Sep 2023 none — — Details →
1.5.83 15 Sep 2023 none — — Details →
1.5.82 14 Sep 2023 none — — Details →
1.5.81 13 Sep 2023 none — — Details →
1.5.80 12 Sep 2023 none — — Details →
1.5.78 12 Sep 2023 none — — Details →
1.5.77 11 Sep 2023 none — — Details →
1.5.76 05 Sep 2023 none — — Details →
1.5.75 01 Sep 2023 none — — Details →
1.5.74 28 Aug 2023 none — — Details →
1.5.73 25 Aug 2023 none — — Details →
1.5.72 23 Aug 2023 none — — Details →
1.5.71 14 Aug 2023 none — — Details →
1.5.70 20 Jul 2023 none — — Details →

The newest 120 of 207 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 @swc/plugin-styled-components

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 @swc/plugin-styled-components

Is @swc/plugin-styled-components safe to use?

Vulert has no vulnerabilities on record for @swc/plugin-styled-components 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 @swc/plugin-styled-components's Vulert package health score?

Vulert scores @swc/plugin-styled-components 82/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 @swc/plugin-styled-components affected?

No. 17.0.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.

Which version of @swc/plugin-styled-components should I use?

17.0.0 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 @swc/plugin-styled-components have?

0 vulnerabilities are recorded for @swc/plugin-styled-components 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 @swc/plugin-styled-components vulnerabilities disclosed?

0 vulnerabilities were recorded for @swc/plugin-styled-components 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 @swc/plugin-styled-components 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 @swc/plugin-styled-components for upcoming vulnerabilities?

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