Vulnerability Database · RubyGems · Package report
activerecord-pg-extensions: vulnerability history, versions and safety
activerecord-pg-extensions is a package in the RubyGems ecosystem. Vulert holds no vulnerabilities for it yet.
Nothing recorded for this package in the RubyGems ecosystem.
Every vulnerability has a patched version to move to.
No published version shipped hostile code.
Vulert verdict on activerecord-pg-extensions 0.8.1 i
Updated on 23 Oct 2026
Good news: 0.8.1, the version you would install today, has no known vulnerabilities.
- Security No known security issues
- Maintenance Sustainable
- Popularity Not enough data
- Community Not enough data
What to do: Stay on 0.8.1 or newer. This can change: a vulnerability disclosed tomorrow can affect 0.8.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release 0.8.1 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Last release 2 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 activerecord-pg-extensions, 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.
- 0.8.1 11 Aug 2026
- 0.8.0 16 Jul 2026
- 0.7.1 16 Jul 2026
- 0.7.0 09 Jul 2026
- 0.6.0 04 Dec 2024
- 0.5.4 05 Oct 2023
- 0.5.3 11 Sep 2023
- 0.5.2 07 Sep 2023
- 0.5.1 07 Sep 2023
- 0.5.0 06 Sep 2023
- 0.4.4 18 Mar 2022
- 0.4.3 11 Feb 2022
- 0.4.2 07 Oct 2021
- 0.4.1 30 Sep 2021
- 0.4.0 30 Sep 2021
- 0.3.0 09 Sep 2021
- 0.2.3 22 Jun 2021
- 0.2.2 22 Jun 2021
- 0.2.1 22 Jun 2021
- 0.2.0 07 Jun 2021
- 0.1.1 07 Jun 2021
| Version | Released | Vulert vulnerabilities | Licence | Fix published | Details |
|---|---|---|---|---|---|
| 0.8.1 | 11 Aug 2026 | none | MIT | — | Details → |
| 0.8.0 | 16 Jul 2026 | none | MIT | — | Details → |
| 0.7.1 | 16 Jul 2026 | none | MIT | — | Details → |
| 0.7.0 | 09 Jul 2026 | none | MIT | — | Details → |
| 0.6.0 | 04 Dec 2024 | none | MIT | — | Details → |
| 0.5.4 | 05 Oct 2023 | none | MIT | — | Details → |
| 0.5.3 | 11 Sep 2023 | none | MIT | — | Details → |
| 0.5.2 | 07 Sep 2023 | none | MIT | — | Details → |
| 0.5.1 | 07 Sep 2023 | none | MIT | — | Details → |
| 0.5.0 | 06 Sep 2023 | none | MIT | — | Details → |
| 0.4.4 | 18 Mar 2022 | none | MIT | — | Details → |
| 0.4.3 | 11 Feb 2022 | none | MIT | — | Details → |
| 0.4.2 | 07 Oct 2021 | none | MIT | — | Details → |
| 0.4.1 | 30 Sep 2021 | none | MIT | — | Details → |
| 0.4.0 | 30 Sep 2021 | none | MIT | — | Details → |
| 0.3.0 | 09 Sep 2021 | none | MIT | — | Details → |
| 0.2.3 | 22 Jun 2021 | none | MIT | — | Details → |
| 0.2.2 | 22 Jun 2021 | none | MIT | — | Details → |
| 0.2.1 | 22 Jun 2021 | none | MIT | — | Details → |
| 0.2.0 | 07 Jun 2021 | none | MIT | — | Details → |
| 0.1.1 | 07 Jun 2021 | none | MIT | — | Details → |
All 21 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-pg-extensions
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
Questions
About activerecord-pg-extensions
Is activerecord-pg-extensions safe to use?
Vulert has no vulnerabilities on record for activerecord-pg-extensions 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-pg-extensions's Vulert package health score?
Vulert scores activerecord-pg-extensions 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-pg-extensions affected?
No. 0.8.1, 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 activerecord-pg-extensions should I use?
0.8.1 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 activerecord-pg-extensions have?
0 vulnerabilities are recorded for activerecord-pg-extensions 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-pg-extensions vulnerabilities disclosed?
0 vulnerabilities were recorded for activerecord-pg-extensions 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-pg-extensions 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-pg-extensions for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the activerecord-pg-extensions version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.