Vulnerability Database · NuGet · Package report
Topshelf: vulnerability history, versions and safety
Topshelf is a package in the NuGet ecosystem. Vulert holds no vulnerabilities for it yet.
Nothing recorded for this package in the NuGet ecosystem.
Every vulnerability has a patched version to move to.
No published version shipped hostile code.
Vulert verdict on Topshelf 4.3.0 i
Updated on 23 Oct 2026
Good news: 4.3.0, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Unmaintained
- Popularity Key ecosystem project
- Community Quiet
What to do: Stay on 4.3.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 4.3.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release 4.3.0 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 3,586 i
- OpenSSF scorecard 1/10 i
- Last release 70 months ago i
- Licence Apache-2.0 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 Topshelf, 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.
- 4.3.1-develop.253 06 Dec 2020
- 4.3.0 06 Dec 2020
- 4.3.0-develop.250 05 Dec 2020
- 4.3.0-develop.249 05 Dec 2020
- 4.2.1.244-develop 05 Dec 2020
- 4.2.1.218-develop 18 Jul 2019
- 4.2.1 02 Jul 2019
- 4.2.0 12 Jan 2019
- 4.1.0 19 Sep 2018
- 4.0.4 10 Apr 2018
- 4.0.3 16 Oct 2016
- 4.0.2 20 Sep 2016
- 4.0.1 10 May 2016
- 4.0.0 03 May 2016
- 3.3.1 12 Dec 2015
- 3.3.0 03 Dec 2015
- 3.2.0 15 May 2015
- 3.1.4 21 Sep 2014
- 3.1.3 04 Jan 2014
- 3.1.2 10 Nov 2013
- 3.1.1 24 Mar 2013
- 3.1.0 08 Nov 2012
- 3.0.2 14 Sep 2012
- 3.0.1 04 Sep 2012
- 3.0.0 26 Aug 2012
- 2.3.0 07 Mar 2012
- 2.2.3 26 Jan 2012
- 2.2.2 10 Jun 2011
- 2.2.1.2 13 May 2011
- 2.2.1.1 13 Apr 2011
- 2.2.1 01 Apr 2011
- 2.1.0.85 18 Jan 2011
- 4.0.4.148-develop
- 4.0.4.161-develop
- 4.1.0.117-develop
- 4.1.0.167-develop
- 4.1.0.168-develop
- 4.1.0.169-develop
- 4.1.0.170-develop
- 4.1.0.175-develop
- 4.1.0.177-develop
- 4.1.0.180-develop
- 4.1.0.191-develop
- 4.2.0.192-develop
- 4.2.0.196-develop
- 4.2.0.199-develop
- 4.2.0.200-develop
- 4.2.0.202-develop
- 4.2.0.205-develop
- 4.2.0.210-develop
- 4.2.0.212-develop
| Version | Released | Vulert vulnerabilities | Licence | Fix published | Details |
|---|---|---|---|---|---|
| 4.3.1-develop.253 | 06 Dec 2020 | none | Apache-2.0 | — | Details → |
| 4.3.0 | 06 Dec 2020 | none | Apache-2.0 | — | Details → |
| 4.3.0-develop.250 | 05 Dec 2020 | none | Apache-2.0 | — | Details → |
| 4.3.0-develop.249 | 05 Dec 2020 | none | Apache-2.0 | — | Details → |
| 4.2.1.244-develop | 05 Dec 2020 | none | non-standard | — | Details → |
| 4.2.1.218-develop | 18 Jul 2019 | none | non-standard | — | Details → |
| 4.2.1 | 02 Jul 2019 | none | non-standard | — | Details → |
| 4.2.0 | 12 Jan 2019 | none | non-standard | — | Details → |
| 4.1.0 | 19 Sep 2018 | none | non-standard | — | Details → |
| 4.0.4 | 10 Apr 2018 | none | non-standard | — | Details → |
| 4.0.3 | 16 Oct 2016 | none | non-standard | — | Details → |
| 4.0.2 | 20 Sep 2016 | none | non-standard | — | Details → |
| 4.0.1 | 10 May 2016 | none | non-standard | — | Details → |
| 4.0.0 | 03 May 2016 | none | non-standard | — | Details → |
| 3.3.1 | 12 Dec 2015 | none | non-standard | — | Details → |
| 3.3.0 | 03 Dec 2015 | none | non-standard | — | Details → |
| 3.2.0 | 15 May 2015 | none | non-standard | — | Details → |
| 3.1.4 | 21 Sep 2014 | none | non-standard | — | Details → |
| 3.1.3 | 04 Jan 2014 | none | non-standard | — | Details → |
| 3.1.2 | 10 Nov 2013 | none | non-standard | — | Details → |
| 3.1.1 | 24 Mar 2013 | none | non-standard | — | Details → |
| 3.1.0 | 08 Nov 2012 | none | non-standard | — | Details → |
| 3.0.2 | 14 Sep 2012 | none | non-standard | — | Details → |
| 3.0.1 | 04 Sep 2012 | none | non-standard | — | Details → |
| 3.0.0 | 26 Aug 2012 | none | non-standard | — | Details → |
| 2.3.0 | 07 Mar 2012 | none | non-standard | — | Details → |
| 2.2.3 | 26 Jan 2012 | none | non-standard | — | Details → |
| 2.2.2 | 10 Jun 2011 | none | non-standard | — | Details → |
| 2.2.1.2 | 13 May 2011 | none | non-standard | — | Details → |
| 2.2.1.1 | 13 Apr 2011 | none | non-standard | — | Details → |
| 2.2.1 | 01 Apr 2011 | none | non-standard | — | Details → |
| 2.1.0.85 | 18 Jan 2011 | none | non-standard | — | Details → |
| 4.0.4.148-develop | — | none | non-standard | — | Details → |
| 4.0.4.161-develop | — | none | non-standard | — | Details → |
| 4.1.0.117-develop | — | none | non-standard | — | Details → |
| 4.1.0.167-develop | — | none | non-standard | — | Details → |
| 4.1.0.168-develop | — | none | non-standard | — | Details → |
| 4.1.0.169-develop | — | none | non-standard | — | Details → |
| 4.1.0.170-develop | — | none | non-standard | — | Details → |
| 4.1.0.175-develop | — | none | non-standard | — | Details → |
| 4.1.0.177-develop | — | none | non-standard | — | Details → |
| 4.1.0.180-develop | — | none | non-standard | — | Details → |
| 4.1.0.191-develop | — | none | non-standard | — | Details → |
| 4.2.0.192-develop | — | none | non-standard | — | Details → |
| 4.2.0.196-develop | — | none | non-standard | — | Details → |
| 4.2.0.199-develop | — | none | non-standard | — | Details → |
| 4.2.0.200-develop | — | none | non-standard | — | Details → |
| 4.2.0.202-develop | — | none | non-standard | — | Details → |
| 4.2.0.205-develop | — | none | non-standard | — | Details → |
| 4.2.0.210-develop | — | none | non-standard | — | Details → |
| 4.2.0.212-develop | — | none | non-standard | — | Details → |
All 51 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.
Other ways into the data
03 Vulnerabilities
Recorded vulnerabilities for Topshelf
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
Questions
About Topshelf
Is Topshelf safe to use?
Vulert has no vulnerabilities on record for Topshelf 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 Topshelf's Vulert package health score?
Vulert scores Topshelf 59/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 Topshelf affected?
No. 4.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.
Which version of Topshelf should I use?
4.3.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 Topshelf have?
0 vulnerabilities are recorded for Topshelf 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 Topshelf vulnerabilities disclosed?
0 vulnerabilities were recorded for Topshelf 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 Topshelf 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 Topshelf for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the Topshelf version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.