Vulnerability Database · PyPI · Package report
thop: vulnerability history, versions and safety
thop is a package in the PyPI ecosystem. Vulert holds no vulnerabilities for it yet.
Nothing recorded for this package in the PyPI ecosystem.
Every vulnerability has a patched version to move to.
No published version shipped hostile code.
Vulert verdict on thop 0.1.1.post2209072238 i
Updated on 23 Oct 2026
Good news: 0.1.1.post2209072238, the version you would install today, has no known vulnerabilities.
- Security No known security issues
- Maintenance Unmaintained
- Popularity Widely used
- Community Active
What to do: Stay on 0.1.1.post2209072238 or newer. This can change: a vulnerability disclosed tomorrow can affect 0.1.1.post2209072238 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release 0.1.1.post2209072238 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Depended on by 204 packages i
- Stars 5,082 i
- Last release 49 months ago i
- Licence MIT i
Version list, release dates, licence and dependants published by PyPI, 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 thop, 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.
- 0.1.1.post2209072238 07 Sep 2022
- 0.1.1.post2207130030 12 Jul 2022
- 0.1.0.post2207010342 30 Jun 2022
- 0.1.0.post2206102148 10 Jun 2022
- 0.0.5.post2206102148 10 Jun 2022
- 0.0.5.post2206100352 09 Jun 2022
- 0.0.5.post2110061705 06 Oct 2021
- 0.0.4.post2110061704 06 Oct 2021
- 0.0.4.post2109101452 10 Sep 2021
- 0.0.4.post2109101449 10 Sep 2021
- 0.0.4.post2108202217 20 Aug 2021
- 0.0.4.post2009191310 19 Sep 2020
- 0.0.4.post2009041907 04 Sep 2020
- 0.0.4.post2007140009 14 Jul 2020
- 0.0.4.post2006111041 11 Jun 2020
- 0.0.4.post2006032126 03 Jun 2020
- 0.0.31.post2005241907 24 May 2020
- 0.0.31.post2005141432 14 May 2020
- 0.0.31.post2005141830 14 May 2020
- 0.0.31.post2004101309 10 Apr 2020
- 0.0.31.post2004070130 07 Apr 2020
- 0.0.31.post2001170342 17 Jan 2020
- 0.0.31.post1912272122 27 Dec 2019
- 0.0.31.post1910280903 28 Oct 2019
- 0.0.31.post1909230639 23 Sep 2019
- 0.0.31.post1909021322 02 Sep 2019
- 0.0.30.post1908302010 30 Aug 2019
- 0.0.30.post1908282117 28 Aug 2019
- 0.0.30.post1908282106 28 Aug 2019
- 0.0.30.post1908282105 28 Aug 2019
- 0.0.30.post1908281655 28 Aug 2019
- 0.0.30.post1908061501 06 Aug 2019
- 0.0.30.post190806 06 Aug 2019
- 0.0.30.post1908061459 06 Aug 2019
- 0.0.23.post1908061459 06 Aug 2019
- 0.0.23.post1908021522 02 Aug 2019
- 0.0.23.post1908021517 02 Aug 2019
- 0.0.23.post1908021457 02 Aug 2019
- 0.0.23.post1907171430 17 Jul 2019
- 0.0.23.post1907171426 17 Jul 2019
- 0.0.23.post1907011323 01 Jul 2019
- 0.0.23.post1906241402 24 Jun 2019
- 0.0.23.post1906241219 24 Jun 2019
- 0.0.23.post1906241153 24 Jun 2019
- 0.0.22.post1906241147 24 Jun 2019
- 0.0.22.post421392844089 24 Jun 2019
- 0.0.22 24 Jun 2019
- 0.0.1-py3.6
- 0.0.21-py3.6
- 0.0.22-py3.6
All 50 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 thop
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 thop
Is thop safe to use?
Vulert has no vulnerabilities on record for thop in PyPI 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 thop's Vulert package health score?
Vulert scores thop 73/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 thop affected?
No. 0.1.1.post2209072238, 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 thop should I use?
0.1.1.post2209072238 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 thop have?
0 vulnerabilities are recorded for thop in the PyPI 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 thop vulnerabilities disclosed?
0 vulnerabilities were recorded for thop 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 thop 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 thop for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the thop version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.