VulertSecurity VulertSecurity

Vulnerability Database · RubyGems · Package report

activerecord-import: vulnerability history, versions and safety

activerecord-import 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 activerecord-import vulnerabilities

Vulert verdict on activerecord-import 3.0.0 i

Updated on 23 Oct 2026

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

Package health score 100/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Not enough data
  • Community Not enough data

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

  • Current release 3.0.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 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 activerecord-import, 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
3.0.0 17 Oct 2026 none MIT — Details →
2.3.0 15 Aug 2026 none MIT — Details →
2.2.0 27 May 2025 none MIT — Details →
2.1.0 03 Feb 2025 none MIT — Details →
2.0.0 10 Dec 2024 none MIT — Details →
1.8.1 06 Sep 2024 none MIT — Details →
1.8.0 23 Aug 2024 none MIT — Details →
1.7.0 17 May 2024 none MIT — Details →
1.6.0 15 Mar 2024 none MIT — Details →
1.5.1 18 Nov 2023 none MIT — Details →
1.5.0 21 Aug 2023 none MIT — Details →
1.4.1 07 Oct 2022 none MIT — Details →
1.4.0 31 Mar 2022 none MIT — Details →
1.3.0 17 Dec 2021 none MIT — Details →
1.2.0 17 Jul 2021 none MIT — Details →
1.1.0 15 May 2021 none MIT — Details →
1.0.8 20 Feb 2021 none MIT — Details →
1.0.7 15 Oct 2020 none MIT — Details →
1.0.6 01 Aug 2020 none MIT — Details →
1.0.5 19 May 2020 none MIT — Details →
1.0.4 24 Dec 2019 none Ruby — Details →
1.0.3 09 Oct 2019 none Ruby — Details →
1.0.2 01 Jun 2019 none Ruby — Details →
1.0.1 25 Feb 2019 none Ruby — Details →
1.0.0 30 Jan 2019 none Ruby — Details →
0.28.2 29 Jan 2019 none Ruby — Details →
0.28.1 04 Jan 2019 none Ruby — Details →
0.28.0 28 Dec 2018 none Ruby — Details →
0.27.0 09 Oct 2018 none Ruby — Details →
0.26.0 05 Oct 2018 none Ruby — Details →
0.25.0 10 Jul 2018 none Ruby — Details →
0.24.0 17 Jun 2018 none Ruby — Details →
0.23.0 04 May 2018 none Ruby — Details →
0.22.0 22 Jan 2018 none Ruby — Details →
0.21.0 21 Nov 2017 none Ruby — Details →
0.20.2 02 Oct 2017 none Ruby — Details →
0.20.1 19 Sep 2017 none Ruby — Details →
0.20.0 12 Sep 2017 none Ruby — Details →
0.19.1 20 Jul 2017 none Ruby — Details →
0.19.0 13 Jun 2017 none Ruby — Details →
0.18.3 10 May 2017 none Ruby — Details →
0.18.2 05 May 2017 none Ruby — Details →
0.18.1 18 Apr 2017 none Ruby — Details →
0.18.0 18 Apr 2017 none Ruby — Details →
0.17.2 14 Mar 2017 none Ruby — Details →
0.17.1 06 Feb 2017 none Ruby — Details →
0.17.0 17 Jan 2017 none Ruby — Details →
0.16.2 17 Nov 2016 none Ruby — Details →
0.16.1 11 Oct 2016 none Ruby — Details →
0.16.0 10 Oct 2016 none Ruby — Details →
0.15.0 04 Jul 2016 none Ruby — Details →
0.14.1 22 Jun 2016 none Ruby — Details →
0.14.0 22 Jun 2016 none Ruby — Details →
0.13.0 01 Apr 2016 none Ruby — Details →
0.12.0 26 Feb 2016 none Ruby — Details →
0.11.0 23 Jan 2016 none Ruby — Details →
0.10.0 08 Jul 2015 none Ruby — Details →
0.9.0 22 Jun 2015 none Ruby — Details →
0.8.0 18 May 2015 none Ruby — Details →
0.7.0 22 Dec 2014 none Ruby — Details →
0.6.0 08 Oct 2014 none Ruby — Details →
0.5.0 13 Mar 2014 none Ruby — Details →
0.4.1 22 Jul 2013 none — — Details →
0.4.0 17 Jul 2013 none — — Details →
0.3.1 16 Feb 2013 none — — Details →
0.3.0 25 Jan 2013 none — — Details →
0.2.11 14 Sep 2012 none — — Details →
0.2.10 06 Aug 2012 none — — Details →
0.2.9 20 Jan 2012 none — — Details →
0.2.8 14 Aug 2011 none — — Details →
0.2.8.rc3 13 Jul 2011 none — — Details →
0.2.8.rc2 23 Jun 2011 none — — Details →
0.2.8.rc1 23 Jun 2011 none — — Details →
0.2.7 29 Apr 2011 none — — Details →
0.2.6 06 Apr 2011 none — — Details →
0.2.5 12 Jan 2011 none — — Details →
0.2.4 06 Jan 2011 none — — Details →
0.2.3 03 Nov 2010 none — — Details →
0.2.2 06 Oct 2010 none — — Details →
0.2.1 05 Oct 2010 none — — Details →
0.2.0 27 Sep 2010 none — — Details →
0.1.0 11 Aug 2010 none — — Details →

All 82 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 activerecord-import

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 activerecord-import

Is activerecord-import safe to use?

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

Vulert scores activerecord-import 100/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 activerecord-import affected?

No. 3.0.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.

How many vulnerabilities does activerecord-import have?

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

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

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