Vulnerability Database · Hex · Package report

floki: vulnerability history, versions and safety

Q: How do I monitor floki for upcoming vulnerabilities?

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

floki is a package in the Hex ecosystem. Vulert holds no vulnerabilities for it yet.

0 vulnerabilities recorded

Nothing recorded for this package in the Hex ecosystem.

0 with no fix published

Every vulnerability has a patched version to move to.

0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →

0 malicious-package vulnerabilities

No published version shipped hostile code.

See all floki vulnerabilities

Vulert verdict on floki 0.38.4 i

Updated on 23 Oct 2026

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

Package health score 96/100

Security No known security issues
Maintenance Sustainable
Popularity Key ecosystem project
Community Not enough data

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

Current release 0.38.4 — unaffected i
Vulnerabilities on record 0 i
Highest CVSS n/a i
With no published fix 0 i
Depended on by 53,893,859 packages i
Last release 4 months ago i

Version list, release dates, licence and dependants published by hex.pm, 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.

Scan your app free →

01 Versions

Which versions are affected

Every version Vulert tracks for floki, 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.

Version	Released	Vulert vulnerabilities	Licence	Fix published	Details
0.38.4	16 Jun 2026	none	—	—	Details →
0.38.3	21 May 2026	none	—	—	Details →
0.38.2	19 May 2026	none	—	—	Details →
0.38.1	17 Mar 2026	none	—	—	Details →
0.38.0	15 Jun 2025	none	—	—	Details →
0.37.1	22 Mar 2025	none	—	—	Details →
0.37.0	06 Dec 2024	none	—	—	Details →
0.36.3	21 Oct 2024	none	—	—	Details →
0.36.2	26 Apr 2024	none	—	—	Details →
0.36.1	18 Mar 2024	none	—	—	Details →
0.36.0	01 Mar 2024	none	—	—	Details →
0.35.4	20 Feb 2024	none	—	—	Details →
0.35.3	25 Jan 2024	none	—	—	Details →
0.35.2	25 Oct 2023	none	—	—	Details →
0.35.1	16 Oct 2023	none	—	—	Details →
0.35.0	13 Oct 2023	none	—	—	Details →
0.34.3	02 Jun 2023	none	—	—	Details →
0.34.2	24 Feb 2023	none	—	—	Details →
0.34.1	11 Feb 2023	none	—	—	Details →
0.34.0	03 Nov 2022	none	—	—	Details →
0.33.1	28 Jun 2022	none	—	—	Details →
0.33.0	28 Jun 2022	none	—	—	Details →
0.32.1	24 Mar 2022	none	—	—	Details →
0.32.0	18 Oct 2021	none	—	—	Details →
0.31.0	11 Jun 2021	none	—	—	Details →
0.30.1	29 Mar 2021	none	—	—	Details →
0.30.0	06 Feb 2021	none	—	—	Details →
0.29.0	02 Oct 2020	none	—	—	Details →
0.28.0	26 Aug 2020	none	—	—	Details →
0.27.0	07 Jul 2020	none	—	—	Details →
0.26.0	18 Feb 2020	none	—	—	Details →
0.25.0	26 Jan 2020	none	—	—	Details →
0.24.0	02 Jan 2020	none	—	—	Details →
0.23.1	01 Dec 2019	none	—	—	Details →
0.23.0	12 Sep 2019	none	—	—	Details →
0.22.0	22 Aug 2019	none	—	—	Details →
0.21.0	18 Apr 2019	none	—	—	Details →
0.20.4	24 Sep 2018	none	—	—	Details →
0.20.3	22 Jun 2018	none	—	—	Details →
0.20.2	10 May 2018	none	—	—	Details →
0.20.1	06 Apr 2018	none	—	—	Details →
0.20.0	06 Feb 2018	none	—	—	Details →
0.19.3	25 Jan 2018	none	—	—	Details →
0.19.2	22 Dec 2017	none	—	—	Details →
0.19.1	04 Dec 2017	none	—	—	Details →
0.19.0	11 Nov 2017	none	—	—	Details →
0.18.1	13 Oct 2017	none	—	—	Details →
0.18.0	05 Aug 2017	none	—	—	Details →
0.17.2	25 May 2017	none	—	—	Details →
0.17.1	22 May 2017	none	—	—	Details →
0.17.0	13 Apr 2017	none	—	—	Details →
0.16.0	05 Apr 2017	none	—	—	Details →
0.15.0	14 Mar 2017	none	—	—	Details →
0.14.0	08 Feb 2017	none	—	—	Details →
0.13.2	08 Feb 2017	none	—	—	Details →
0.13.1	22 Jan 2017	none	—	—	Details →
0.13.0	22 Jan 2017	none	—	—	Details →
0.12.1	20 Jan 2017	none	—	—	Details →
0.12.0	29 Dec 2016	none	—	—	Details →
0.11.0	12 Oct 2016	none	—	—	Details →
0.10.1	28 Aug 2016	none	—	—	Details →
0.10.0	05 Aug 2016	none	—	—	Details →
0.9.0	17 Jun 2016	none	—	—	Details →
0.8.1	20 May 2016	none	—	—	Details →
0.8.0	06 Mar 2016	none	—	—	Details →
0.7.2	23 Feb 2016	none	—	—	Details →
0.7.1	15 Nov 2015	none	—	—	Details →
0.7.0	04 Nov 2015	none	—	—	Details →
0.6.1	12 Oct 2015	none	—	—	Details →
0.6.0	08 Oct 2015	none	—	—	Details →
0.5.0	27 Sep 2015	none	—	—	Details →
0.4.1	18 Sep 2015	none	—	—	Details →
0.4.0	17 Sep 2015	none	—	—	Details →
0.3.3	23 Aug 2015	none	—	—	Details →
0.3.2	27 Jun 2015	none	—	—	Details →
0.3.1	22 Jun 2015	none	—	—	Details →
0.3.0	07 Jun 2015	none	—	—	Details →
0.2.1	04 Jun 2015	none	—	—	Details →
0.2.0	03 May 2015	none	—	—	Details →
0.1.1	25 Mar 2015	none	—	—	Details →
0.1.0	15 Feb 2015	none	—	—	Details →
0.0.5	21 Dec 2014	none	—	—	Details →
0.0.4	11 Nov 2014	none	—	—	Details →
0.0.3	09 Nov 2014	none	—	—	Details →
0.0.2	03 Nov 2014	none	—	—	Details →
0.0.1	02 Nov 2014	none	—	—	Details →

All 86 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 floki

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 floki

Is floki safe to use?

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

Vulert scores floki 96/100, which reads as healthy. 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 floki affected?

No. 0.38.4, 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.

How many vulnerabilities does floki have?

0 vulnerabilities are recorded for floki in the Hex 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 floki vulnerabilities disclosed?

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

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