Vulnerability Database · NuGet · Package report

StyleCop.Analyzers: vulnerability history, versions and safety

StyleCop.Analyzers is a package in the NuGet ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the NuGet 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 StyleCop.Analyzers 1.1.118 i

Updated on 23 Oct 2026

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

Package health score 67/100
  • Security No known security issues
  • Maintenance Unmaintained
  • Popularity Not enough data
  • Community Not enough data

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

  • Current release 1.1.118 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Last release 89 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by NuGet, 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 StyleCop.Analyzers, 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
1.3.151-beta 21 Oct 2026 none MIT — Details →
1.3.149-beta 20 Oct 2026 none MIT — Details →
1.3.133-beta 19 Oct 2026 none MIT — Details →
1.3.109-beta 17 Oct 2026 none MIT — Details →
1.3.98-beta 16 Oct 2026 none MIT — Details →
1.3.82-beta 15 Oct 2026 none MIT — Details →
1.3.79-beta 14 Oct 2026 none MIT — Details →
1.3.18-beta 13 Oct 2026 none MIT — Details →
1.3.1-beta 12 Oct 2026 none MIT — Details →
1.2.0-beta.556 20 Dec 2023 none MIT — Details →
1.2.0-beta.507 21 Jun 2023 none MIT — Details →
1.2.0-beta.435 03 May 2022 none MIT — Details →
1.2.0-beta.406 28 Jan 2022 none MIT — Details →
1.2.0-beta.376 09 Dec 2021 none MIT — Details →
1.2.0-beta.354 17 Jun 2021 none MIT — Details →
1.2.0-beta.333 11 Mar 2021 none MIT — Details →
1.2.0-beta.321 31 Dec 2020 none MIT — Details →
1.2.0-beta.312 08 Dec 2020 none MIT — Details →
1.2.0-beta.304 05 Dec 2020 none MIT — Details →
1.2.0-beta.261 01 Nov 2020 none MIT — Details →
1.2.0-beta.205 30 Jul 2020 none MIT — Details →
1.2.0-beta.164 14 Feb 2020 none Apache-2.0 — Details →
1.2.0-beta.113 08 Nov 2019 none Apache-2.0 — Details →
1.2.0-beta.66 03 Sep 2019 none Apache-2.0 — Details →
1.1.118 29 Apr 2019 none Apache-2.0 — Details →
1.1.1-rc.114 02 Mar 2019 none Apache-2.0 — Details →
1.1.1-rc.108 20 Feb 2019 none Apache-2.0 — Details →
1.1.1-rc.101 15 Feb 2019 none non-standard — Details →
1.1.1-rc.94 06 Feb 2019 none non-standard — Details →
1.1.1-beta.61 15 Nov 2018 none non-standard — Details →
1.1.0-beta.47 29 Oct 2018 none non-standard — Details →
1.1.0-beta009 05 Sep 2018 none non-standard — Details →
1.1.0-beta008 13 Jun 2018 none non-standard — Details →
1.1.0-beta007 09 May 2018 none non-standard — Details →
1.1.0-beta006 29 Jan 2018 none non-standard — Details →
1.1.0-beta004 24 Jun 2017 none non-standard — Details →
1.1.0-beta003 15 Jun 2017 none non-standard — Details →
1.1.0-beta002 15 Jun 2017 none non-standard — Details →
1.0.2 29 May 2017 none non-standard — Details →
1.1.0-beta001 23 Nov 2016 none non-standard — Details →
1.0.0 28 Jan 2016 none non-standard — Details →
1.0.0-rc3 28 Dec 2015 none non-standard — Details →
1.0.0-rc2 07 Dec 2015 none non-standard — Details →
1.0.0-rc1 01 Dec 2015 none non-standard — Details →
1.0.0-beta017 26 Nov 2015 none non-standard — Details →
1.0.0-beta016 19 Nov 2015 none non-standard — Details →
1.0.0-beta015 25 Oct 2015 none non-standard — Details →
1.0.0-beta014 16 Oct 2015 none non-standard — Details →
1.0.0-beta013 27 Sep 2015 none non-standard — Details →
1.0.0-beta012 18 Sep 2015 none non-standard — Details →
1.0.0-beta011 11 Sep 2015 none non-standard — Details →
1.0.0-beta010 09 Sep 2015 none non-standard — Details →
1.0.0-beta009 30 Aug 2015 none non-standard — Details →
1.0.0-beta008 17 Aug 2015 none non-standard — Details →
1.0.0-beta007 16 Aug 2015 none non-standard — Details →
1.0.0-beta006 13 Aug 2015 none non-standard — Details →
1.0.0-beta005 08 Aug 2015 none non-standard — Details →
1.0.0-beta004 07 Aug 2015 none non-standard — Details →
1.0.0-beta003 29 Jul 2015 none non-standard — Details →
1.0.0-beta002 28 Jul 2015 none non-standard — Details →
1.0.0-beta001 20 Jul 2015 none non-standard — Details →
1.0.0-alpha011 20 Jul 2015 none non-standard — Details →
1.0.0-alpha010 31 May 2015 none non-standard — Details →
1.0.0-alpha009 30 May 2015 none non-standard — Details →
1.0.0-alpha008 27 May 2015 none non-standard — Details →
1.0.0-alpha007 25 May 2015 none non-standard — Details →
1.0.0-alpha006 03 May 2015 none non-standard — Details →
1.0.0-alpha005 25 Apr 2015 none non-standard — Details →
1.0.0-alpha004 26 Feb 2015 none non-standard — Details →
1.0.0-alpha003 09 Feb 2015 none non-standard — Details →
1.0.0-alpha002 09 Feb 2015 none non-standard — Details →
1.0.0-alpha001 21 Jan 2015 none non-standard — Details →
1.0.1 — none non-standard — Details →
1.1.0-beta005 — none non-standard — Details →
1.1.1-rc.92 — none non-standard — Details →
1.2.0-beta.553 — none MIT — Details →

All 76 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 StyleCop.Analyzers

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 StyleCop.Analyzers

Is StyleCop.Analyzers safe to use?

Vulert has no vulnerabilities on record for StyleCop.Analyzers in NuGet 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 StyleCop.Analyzers's Vulert package health score?

Vulert scores StyleCop.Analyzers 67/100, which reads as usable, but worth attention. 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 StyleCop.Analyzers affected?

No. 1.1.118, 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 StyleCop.Analyzers should I use?

1.1.118 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 StyleCop.Analyzers have?

0 vulnerabilities are recorded for StyleCop.Analyzers in the NuGet 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 StyleCop.Analyzers vulnerabilities disclosed?

0 vulnerabilities were recorded for StyleCop.Analyzers 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 StyleCop.Analyzers 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 StyleCop.Analyzers for upcoming vulnerabilities?

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