VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

fvcore: vulnerability history, versions and safety

fvcore is a package in the PyPI ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the PyPI 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.

See all fvcore vulnerabilities

Vulert verdict on fvcore 0.1.5.post20221221 i

Updated on 23 Oct 2026

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

Package health score 69/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Widely used
  • Community Quiet

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

  • Current release 0.1.5.post20221221 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 101 packages i
  • Stars 2,253 i
  • OpenSSF scorecard 4/10 i
  • Last release 46 months ago i
  • Licence Apache-2.0 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 fvcore, 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.1.5.post20221221 21 Dec 2022 none Apache-2.0 — Details →
0.1.5.post20221220 20 Dec 2022 none Apache-2.0 — Details →
0.1.5.post20221213 13 Dec 2022 none Apache-2.0 — Details →
0.1.5.post20221122 22 Nov 2022 none Apache-2.0 — Details →
0.1.5.post20220512 12 May 2022 none Apache-2.0 — Details →
0.1.5.post20220506 06 May 2022 none Apache-2.0 — Details →
0.1.5.post20220504 04 May 2022 none Apache-2.0 — Details →
0.1.5.post20220414 14 Apr 2022 none Apache-2.0 — Details →
0.1.5.post20220305 05 Mar 2022 none Apache-2.0 — Details →
0.1.5.post20220212 12 Feb 2022 none Apache-2.0 — Details →
0.1.5.post20220119 19 Jan 2022 none Apache-2.0 — Details →
0.1.5.post20211023 23 Oct 2021 none Apache-2.0 — Details →
0.1.5.post20211019 19 Oct 2021 none Apache-2.0 — Details →
0.1.5.post20211015 15 Oct 2021 none Apache-2.0 — Details →
0.1.5.post20210924 24 Sep 2021 none Apache-2.0 — Details →
0.1.5.post20210923 23 Sep 2021 none Apache-2.0 — Details →
0.1.5.post20210915 15 Sep 2021 none Apache-2.0 — Details →
0.1.5.post20210825 25 Aug 2021 none Apache-2.0 — Details →
0.1.5.post20210812 12 Aug 2021 none Apache-2.0 — Details →
0.1.5.post20210804 04 Aug 2021 none Apache-2.0 — Details →
0.1.5.post20210730 30 Jul 2021 none Apache-2.0 — Details →
0.1.5.post20210727 27 Jul 2021 none Apache-2.0 — Details →
0.1.5.post20210722 22 Jul 2021 none Apache-2.0 — Details →
0.1.5.post20210719 19 Jul 2021 none Apache-2.0 — Details →
0.1.5.post20210630 30 Jun 2021 none Apache-2.0 — Details →
0.1.5.post20210624 24 Jun 2021 none Apache-2.0 — Details →
0.1.5.post20210623 23 Jun 2021 none Apache-2.0 — Details →
0.1.5.post20210617 17 Jun 2021 none Apache-2.0 — Details →
0.1.5.post20210609 09 Jun 2021 none Apache-2.0 — Details →
0.1.5.post20210604 04 Jun 2021 none Apache-2.0 — Details →
0.1.5.post20210518 18 May 2021 none Apache-2.0 — Details →
0.1.5.post20210515 15 May 2021 none Apache-2.0 — Details →
0.1.5.post20210514 14 May 2021 none Apache-2.0 — Details →
0.1.5.post20210511 11 May 2021 none Apache-2.0 — Details →
0.1.5.post20210508 08 May 2021 none Apache-2.0 — Details →
0.1.5.post20210423 23 Apr 2021 none Apache-2.0 — Details →
0.1.5.post20210415 15 Apr 2021 none Apache-2.0 — Details →
0.1.5.post20210413 13 Apr 2021 none Apache-2.0 — Details →
0.1.5.post20210410 10 Apr 2021 none Apache-2.0 — Details →
0.1.5.post20210402 02 Apr 2021 none Apache-2.0 — Details →
0.1.5.post20210330 30 Mar 2021 none Apache-2.0 — Details →
0.1.5.post20210328 28 Mar 2021 none Apache-2.0 — Details →
0.1.5.post20210327 27 Mar 2021 none Apache-2.0 — Details →
0.1.4.post20210326 26 Mar 2021 none Apache-2.0 — Details →
0.1.4.post20210325 25 Mar 2021 none Apache-2.0 — Details →
0.1.4.post20210324 24 Mar 2021 none Apache-2.0 — Details →
0.1.4.post20210323 23 Mar 2021 none Apache-2.0 — Details →
0.1.4 22 Mar 2021 none Apache-2.0 — Details →
0.1.3.post20210317 17 Mar 2021 none Apache-2.0 — Details →
0.1.3.post20210311 11 Mar 2021 none Apache-2.0 — Details →
0.1.3.post20210310 10 Mar 2021 none Apache-2.0 — Details →
0.1.3.post20210306 06 Mar 2021 none Apache-2.0 — Details →
0.1.3.post20210305 05 Mar 2021 none Apache-2.0 — Details →
0.1.3.post20210227 27 Feb 2021 none Apache-2.0 — Details →
0.1.3.post20210226 26 Feb 2021 none Apache-2.0 — Details →
0.1.3.post20210225 25 Feb 2021 none Apache-2.0 — Details →
0.1.3.post20210224 24 Feb 2021 none Apache-2.0 — Details →
0.1.3.post20210223 23 Feb 2021 none Apache-2.0 — Details →
0.1.3.post20210220 20 Feb 2021 none Apache-2.0 — Details →
0.1.3.post20210219 19 Feb 2021 none Apache-2.0 — Details →
0.1.3.post20210218 18 Feb 2021 none Apache-2.0 — Details →
0.1.3.post20210213 13 Feb 2021 none Apache-2.0 — Details →
0.1.3.post20210204 04 Feb 2021 none Apache-2.0 — Details →
0.1.3.post20210203 03 Feb 2021 none Apache-2.0 — Details →
0.1.2.post20210128 28 Jan 2021 none Apache-2.0 — Details →
0.1.2.post20210127 27 Jan 2021 none Apache-2.0 — Details →
0.1.2.post20210126 26 Jan 2021 none Apache-2.0 — Details →
0.1.2.post20210115 15 Jan 2021 none Apache-2.0 — Details →
0.1.2.post20210113 13 Jan 2021 none Apache-2.0 — Details →
0.1.2.post20210112 12 Jan 2021 none Apache-2.0 — Details →
0.1.2.post20210109 09 Jan 2021 none Apache-2.0 — Details →
0.1.2.post20201218 18 Dec 2020 none Apache-2.0 — Details →
0.1.2.post20201216 16 Dec 2020 none Apache-2.0 — Details →
0.1.2.post20201213 13 Dec 2020 none Apache-2.0 — Details →
0.1.2.post20201212 12 Dec 2020 none Apache-2.0 — Details →
0.1.2.post20201211 11 Dec 2020 none Apache-2.0 — Details →
0.1.2.post20201210 10 Dec 2020 none Apache-2.0 — Details →
0.1.2.post20201209 09 Dec 2020 none Apache-2.0 — Details →
0.1.2.post20201204 04 Dec 2020 none Apache-2.0 — Details →
0.1.2.post20201122 22 Nov 2020 none Apache-2.0 — Details →
0.1.2.post20201111 11 Nov 2020 none Apache-2.0 — Details →
0.1.2.post20201104 04 Nov 2020 none Apache-2.0 — Details →
0.1.2.post20201103 03 Nov 2020 none Apache-2.0 — Details →
0.1.2.post20201030 30 Oct 2020 none Apache-2.0 — Details →
0.1.2.post20201020 20 Oct 2020 none Apache-2.0 — Details →
0.1.2.post20201016 16 Oct 2020 none Apache-2.0 — Details →
0.1.2.post20201013 13 Oct 2020 none Apache-2.0 — Details →
0.1.2.post20201009 09 Oct 2020 none Apache-2.0 — Details →
0.1.2.post20200929 29 Sep 2020 none Apache-2.0 — Details →
0.1.2.post20200926 26 Sep 2020 none Apache-2.0 — Details →
0.1.2.post20200912 12 Sep 2020 none Apache-2.0 — Details →
0.1.2.post20200911 11 Sep 2020 none Apache-2.0 — Details →
0.1.2.post20200910 10 Sep 2020 none Apache-2.0 — Details →
0.1.1.post20200716 16 Jul 2020 none Apache-2.0 — Details →
0.1.1.post20200715 15 Jul 2020 none Apache-2.0 — Details →
0.1.1.post20200711 11 Jul 2020 none Apache-2.0 — Details →
0.1.1.post20200704 04 Jul 2020 none Apache-2.0 — Details →
0.1.1.post20200630 30 Jun 2020 none Apache-2.0 — Details →
0.1.1.post20200623 23 Jun 2020 none Apache-2.0 — Details →
0.1.1.post20200622 22 Jun 2020 none Apache-2.0 — Details →
0.1.1.post20200621 21 Jun 2020 none — — Details →
0.1.1.post20200620 20 Jun 2020 none — — Details →
0.1.1.post20200619 19 Jun 2020 none — — Details →
0.1.1.post20200618 18 Jun 2020 none — — Details →
0.1.1.post20200617 17 Jun 2020 none — — Details →
0.1.1.post20200616 16 Jun 2020 none — — Details →
0.1.1.post20200615 15 Jun 2020 none — — Details →
0.1.1.post20200614 14 Jun 2020 none — — Details →
0.1.1.post20200613 13 Jun 2020 none — — Details →
0.1.1.post20200612 12 Jun 2020 none — — Details →
0.1.1.post20200611 11 Jun 2020 none — — Details →
0.1.1.post20200610 10 Jun 2020 none — — Details →
0.1.1.post20200609 09 Jun 2020 none — — Details →
0.1.1.post20200608 08 Jun 2020 none — — Details →
0.1.1.post20200607 07 Jun 2020 none — — Details →
0.1.1.post20200606 06 Jun 2020 none — — Details →
0.1.1.post20200605 05 Jun 2020 none — — Details →
0.1.1.post20200604 04 Jun 2020 none — — Details →
0.1.1.post20200603 03 Jun 2020 none — — Details →
0.1.1.post20200602 02 Jun 2020 none — — Details →

The newest 120 of 192 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 fvcore

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 fvcore

Is fvcore safe to use?

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

Vulert scores fvcore 69/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 fvcore affected?

No. 0.1.5.post20221221, 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 fvcore should I use?

0.1.5.post20221221 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 fvcore have?

0 vulnerabilities are recorded for fvcore 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 fvcore vulnerabilities disclosed?

0 vulnerabilities were recorded for fvcore 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 fvcore 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 fvcore for upcoming vulnerabilities?

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