VulertSecurity VulertSecurity

Vulnerability Database · RubyGems · Package report

flipper-api: vulnerability history, versions and safety

flipper-api is a package in the RubyGems ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the RubyGems 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 flipper-api vulnerabilities

Vulert verdict on flipper-api 1.4.2 i

Updated on 23 Oct 2026

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

Package health score 90/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

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

  • Current release 1.4.2 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 3,972 i
  • Last release 5 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by RubyGems, 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 flipper-api, 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.4.2 11 May 2026 none MIT — Details →
1.4.1 25 Mar 2026 none MIT — Details →
1.4.0 26 Feb 2026 none MIT — Details →
1.3.6 31 Jul 2025 none MIT — Details →
1.3.5 28 Jun 2025 none MIT — Details →
1.3.4 03 Mar 2025 none MIT — Details →
1.3.3 24 Feb 2025 none MIT — Details →
1.3.2 19 Nov 2024 none MIT — Details →
1.3.1 04 Sep 2024 none MIT — Details →
1.3.0 17 Apr 2024 none MIT — Details →
1.3.0.pre 14 Mar 2024 none MIT — Details →
1.2.2 19 Jan 2024 none MIT — Details →
1.2.1 15 Jan 2024 none MIT — Details →
1.2.0 11 Jan 2024 none MIT — Details →
1.1.2 12 Dec 2023 none MIT — Details →
1.1.1 09 Dec 2023 none MIT — Details →
1.1.0 08 Dec 2023 none MIT — Details →
1.0.0 23 Aug 2023 none MIT — Details →
1.0.0.pre 02 Aug 2023 none MIT — Details →
0.28.3 21 Jul 2023 none MIT — Details →
0.28.2 18 Jul 2023 none MIT — Details →
0.28.1 17 Jul 2023 none MIT — Details →
0.28.0 21 Mar 2023 none MIT — Details →
0.27.1 20 Mar 2023 none MIT — Details →
0.27.0 18 Mar 2023 none MIT — Details →
0.26.2 15 Mar 2023 none MIT — Details →
0.26.1 15 Mar 2023 none MIT — Details →
0.26.0 05 Dec 2022 none MIT — Details →
0.26.0.rc2 16 Nov 2022 none MIT — Details →
0.26.0.rc1 11 Nov 2022 none MIT — Details →
0.25.4 07 Nov 2022 none MIT — Details →
0.25.3 03 Nov 2022 none MIT — Details →
0.25.2 25 Aug 2022 none MIT — Details →
0.25.1 19 Aug 2022 none MIT — Details →
0.25.0 09 Jun 2022 none MIT — Details →
0.24.1 13 Apr 2022 none MIT — Details →
0.24.0 17 Feb 2022 none MIT — Details →
0.23.1 19 Jan 2022 none MIT — Details →
0.23.0 24 Dec 2021 none MIT — Details →
0.22.2 06 Oct 2021 none MIT — Details →
0.22.1 23 Aug 2021 none MIT — Details →
0.22.0 08 Jul 2021 none MIT — Details →
0.21.0 09 May 2021 none MIT — Details →
0.21.0.rc2 08 May 2021 none MIT — Details →
0.21.0.rc1 01 May 2021 none MIT — Details →
0.20.4 06 Mar 2021 none MIT — Details →
0.20.3 10 Jan 2021 none MIT — Details →
0.20.2 08 Jan 2021 none MIT — Details →
0.20.1 31 Dec 2020 none MIT — Details →
0.20.0 20 Dec 2020 none MIT — Details →
0.20.0.beta3 17 Dec 2020 none MIT — Details →
0.20.0.beta2 14 Dec 2020 none MIT — Details →
0.20.0.beta1 11 Dec 2020 none MIT — Details →
0.19.1 04 Dec 2020 none MIT — Details →
0.19.0 25 Sep 2020 none MIT — Details →
0.18.0 25 Jun 2020 none MIT — Details →
0.17.2 04 Jan 2020 none MIT — Details →
0.17.1 14 Sep 2019 none MIT — Details →
0.16.2 20 Apr 2019 none MIT — Details →
0.16.1 05 Feb 2019 none MIT — Details →
0.16.0 01 Aug 2018 none MIT — Details →
0.15.0 12 May 2018 none MIT — Details →
0.14.0 27 Mar 2018 none MIT — Details →
0.13.0 04 Mar 2018 none MIT — Details →
0.13.0.beta1 03 Mar 2018 none MIT — Details →
0.12.2 22 Jan 2018 none MIT — Details →
0.12.1 19 Jan 2018 none MIT — Details →
0.12.0 06 Jan 2018 none MIT — Details →
0.11.0 16 Nov 2017 none MIT — Details →
0.11.0.rc1 04 Nov 2017 none MIT — Details →
0.11.0.beta9 28 Oct 2017 none MIT — Details →
0.11.0.beta8 28 Oct 2017 none MIT — Details →
0.11.0.beta7 26 Jul 2017 none MIT — Details →
0.11.0.beta6 11 Jun 2017 none MIT — Details →
0.11.0.beta5 16 May 2017 none MIT — Details →
0.11.0.beta4 10 May 2017 none MIT — Details →
0.11.0.beta3 10 Apr 2017 none MIT — Details →
0.11.0.beta1 02 Apr 2017 none MIT — Details →
0.10.2 08 Dec 2016 none MIT — Details →
0.10.1 19 Nov 2016 none MIT — Details →
0.10.0 17 Nov 2016 none MIT — Details →
0.9.2 22 Aug 2016 none MIT — Details →
0.9.1 07 Jul 2016 none MIT — Details →
0.9.0 05 Jul 2016 none MIT — Details →
0.9.0.beta1 23 Jun 2016 none MIT — Details →
0.8.0 21 Jun 2016 none MIT — 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.

03 Vulnerabilities

Recorded vulnerabilities for flipper-api

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 flipper-api

Is flipper-api safe to use?

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

Vulert scores flipper-api 90/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 flipper-api affected?

No. 1.4.2, 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 flipper-api should I use?

1.4.2 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 flipper-api have?

0 vulnerabilities are recorded for flipper-api in the RubyGems 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 flipper-api vulnerabilities disclosed?

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

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