VulertSecurity VulertSecurity

Vulnerability Database · RubyGems · Package report

bullet: vulnerability history, versions and safety

bullet 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 bullet vulnerabilities

Vulert verdict on bullet 8.3.0 i

Updated on 23 Oct 2026

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

Package health score 83/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Quiet

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

  • Current release 8.3.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 7,338 i
  • OpenSSF scorecard 3/10 i
  • Last release this month 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 bullet, 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
8.3.0 10 Oct 2026 none MIT — Details →
8.2.0 29 Aug 2026 none MIT — Details →
8.1.3 02 Jun 2026 none MIT — Details →
8.1.2 25 May 2026 none MIT — Details →
8.1.1 23 Apr 2026 none MIT — Details →
8.1.0 23 Oct 2025 none MIT — Details →
8.1.0.beta1 16 Oct 2025 none MIT — Details →
8.0.8 30 May 2025 none MIT — Details →
8.0.7 15 May 2025 none MIT — Details →
8.0.6 07 May 2025 none MIT — Details →
8.0.5 21 Apr 2025 none MIT — Details →
8.0.4 18 Apr 2025 none MIT — Details →
8.0.3 04 Apr 2025 none MIT — Details →
8.0.2 02 Apr 2025 none MIT — Details →
8.0.1 10 Feb 2025 none MIT — Details →
8.0.0 10 Nov 2024 none MIT — Details →
7.2.0 12 Jul 2024 none MIT — Details →
7.1.6 16 Jan 2024 none MIT — Details →
7.1.5 05 Jan 2024 none MIT — Details →
7.1.4 17 Nov 2023 none MIT — Details →
7.1.3 05 Nov 2023 none MIT — Details →
7.1.2 13 Oct 2023 none MIT — Details →
7.1.1 07 Oct 2023 none MIT — Details →
7.1.0 06 Oct 2023 none MIT — Details →
7.0.7 03 Jan 2023 none MIT — Details →
7.0.6 03 Jan 2023 none MIT — Details →
7.0.5 01 Jan 2023 none MIT — Details →
7.0.4 28 Nov 2022 none MIT — Details →
7.0.3 13 Aug 2022 none MIT — Details →
7.0.2 31 May 2022 none MIT — Details →
7.0.1 15 Jan 2022 none MIT — Details →
7.0.0 18 Dec 2021 none MIT — Details →
6.1.5 16 Aug 2021 none MIT — Details →
6.1.4 26 Feb 2021 none MIT — Details →
6.1.3 20 Jan 2021 none MIT — Details →
6.1.2 12 Dec 2020 none MIT — Details →
6.1.1 12 Dec 2020 none MIT — Details →
6.1.0 28 Dec 2019 none MIT — Details →
6.0.2 20 Aug 2019 none MIT — Details →
6.0.1 26 Jun 2019 none MIT — Details →
6.0.0 25 Apr 2019 none MIT — Details →
5.9.0 11 Nov 2018 none MIT — Details →
5.8.1 30 Oct 2018 none MIT — Details →
5.8.0 29 Oct 2018 none MIT — Details →
5.7.6 15 Aug 2018 none MIT — Details →
5.7.5 12 Mar 2018 none MIT — Details →
5.7.4 10 Mar 2018 none MIT — Details →
5.7.3 17 Feb 2018 none MIT — Details →
5.7.2 18 Jan 2018 none MIT — Details →
5.7.1 07 Jan 2018 none MIT — Details →
5.7.0 03 Dec 2017 none MIT — Details →
5.6.1 01 Aug 2017 none MIT — Details →
5.6.0 16 Jul 2017 none MIT — Details →
5.5.1 01 Mar 2017 none MIT — Details →
5.5.0 30 Dec 2016 none MIT — Details →
5.4.3 13 Dec 2016 none MIT — Details →
5.4.2 27 Sep 2016 none MIT — Details →
5.4.1 26 Sep 2016 none MIT — Details →
5.4.0 10 Sep 2016 none MIT — Details →
5.3.0 15 Aug 2016 none MIT — Details →
5.2.1 12 Aug 2016 none MIT — Details →
5.2.0 26 Jul 2016 none MIT — Details →
5.1.1 30 Jun 2016 none MIT — Details →
5.1.0 22 May 2016 none MIT — Details →
5.0.0 05 Jan 2016 none MIT — Details →
4.14.10 23 Oct 2015 none MIT — Details →
4.14.9 12 Oct 2015 none MIT — Details →
4.14.8 12 Oct 2015 none MIT — Details →
4.14.7 09 May 2015 none MIT — Details →
4.14.6 04 May 2015 none MIT — Details →
4.14.5 19 Apr 2015 none MIT — Details →
4.14.4 03 Feb 2015 none MIT — Details →
4.14.3 01 Feb 2015 none MIT — Details →
4.14.2 20 Jan 2015 none MIT — Details →
4.14.0 03 Oct 2014 none MIT — Details →
4.13.2 06 Sep 2014 none MIT — Details →
4.13.1 03 Aug 2014 none MIT — Details →
4.13.0 19 Jul 2014 none MIT — Details →
4.12.0 13 Jul 2014 none MIT — Details →
4.11.3 29 Jun 2014 none MIT — Details →
4.11.2 27 Jun 2014 none MIT — Details →
4.11.1 25 Jun 2014 none MIT — Details →
4.11.0 24 Jun 2014 none MIT — Details →
4.10.0 06 Jun 2014 none MIT — Details →
4.9.0 30 Apr 2014 none — — Details →
4.8.0 16 Feb 2014 none — — Details →
4.7.1 03 Nov 2013 none — — Details →
4.7.0 03 Nov 2013 none — — Details →
4.6.0 17 Apr 2013 none — — Details →
4.5.0 24 Mar 2013 none — — Details →
4.4.0 15 Mar 2013 none — — Details →
4.3.1 01 Mar 2013 none — — Details →
4.3.0 28 Dec 2012 none — — Details →
4.2.0 28 Sep 2012 none — — Details →
4.1.6 17 Aug 2012 none — — Details →
4.1.5 24 Jul 2012 none — — Details →
4.1.4 23 Jun 2012 none — — Details →
4.1.3 09 Jun 2012 none — — Details →
4.1.2 07 Jun 2012 none — — Details →
4.1.1 06 Jun 2012 none — — Details →
4.1.0 30 May 2012 none — — Details →
4.0.0 09 May 2012 none — — Details →
2.3.1 02 Apr 2012 none — — Details →
2.3.0 25 Mar 2012 none — — Details →
2.2.1 11 Mar 2012 none — — Details →
2.2.0 05 Mar 2012 none — — Details →
2.1.0 11 Dec 2011 none — — Details →
2.0.1 19 Nov 2010 none — — Details →
2.0.0 19 Nov 2010 none — — Details →
2.0.0.rc3 02 Nov 2010 none — — Details →
2.0.0.rc2 07 Oct 2010 none — — Details →
2.0.0.rc1 10 Aug 2010 none — — Details →
2.0.0.beta.4 10 Aug 2010 none — — Details →
2.0.0.beta.3 14 Jul 2010 none — — Details →
2.0.0.beta.2 07 Mar 2010 none — — Details →
2.0.0.beta.1 07 Mar 2010 none — — Details →
1.7.6 07 Mar 2010 none — — Details →
1.7.5 12 Feb 2010 none — — Details →
1.7.4 16 Jan 2010 none — — Details →
1.7.3 01 Jan 2010 none — — Details →

The newest 120 of 124 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 bullet

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 bullet

Is bullet safe to use?

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

Vulert scores bullet 83/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 bullet affected?

No. 8.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 bullet should I use?

8.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 bullet have?

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

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

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