VulertSecurity VulertSecurity

Vulnerability Database · RubyGems · Package report

moodle2cc: vulnerability history, versions and safety

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

Vulert verdict on moodle2cc 0.2.47 i

Updated on 23 Oct 2026

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

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

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

  • Current release 0.2.47 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Last release 12 months ago i
  • Licence AGPL-3.0 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 moodle2cc, 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
0.2.47 02 Oct 2025 none AGPL-3.0 — Details →
0.2.46 09 Apr 2024 none AGPL-3.0 — Details →
0.2.45 26 Mar 2024 none AGPL-3.0 — Details →
0.2.44 30 Jan 2024 none AGPL-3.0 — Details →
0.2.43 25 Jan 2024 none AGPL-3.0 — Details →
0.2.42 24 Oct 2023 none AGPL-3.0 — Details →
0.2.41 11 May 2018 none AGPL-3.0 — Details →
0.2.40 09 May 2018 none AGPL-3.0 — Details →
0.2.39 27 Oct 2017 none AGPL-3.0 — Details →
0.2.38 18 May 2017 none AGPL-3.0 — Details →
0.2.37 20 Dec 2016 none AGPL-3.0 — Details →
0.2.36.1 22 Sep 2016 none AGPL-3.0 — Details →
0.2.36 22 Sep 2016 none AGPL-3.0 — Details →
0.2.35 28 Jul 2016 none AGPL-3.0 — Details →
0.2.34 12 Jul 2016 none AGPL-3.0 — Details →
0.2.33 07 Jun 2016 none AGPL-3.0 — Details →
0.2.32.1 18 May 2016 none AGPL-3.0 — Details →
0.2.32 17 May 2016 none AGPL-3.0 — Details →
0.2.31 29 Apr 2016 none AGPL-3.0 — Details →
0.2.30 28 Mar 2016 none AGPL-3.0 — Details →
0.2.29 16 Mar 2016 none AGPL-3.0 — Details →
0.2.28 18 Nov 2015 none AGPL-3.0 — Details →
0.2.27 21 Oct 2015 none AGPL-3.0 — Details →
0.2.26 23 Sep 2015 none AGPL-3.0 — Details →
0.2.25 04 Aug 2015 none AGPL-3.0 — Details →
0.2.24 31 Jul 2015 none AGPL-3.0 — Details →
0.2.23 27 Jul 2015 none AGPL-3.0 — Details →
0.2.22 24 Jul 2015 none AGPL-3.0 — Details →
0.2.21 10 Jun 2015 none AGPL-3.0 — Details →
0.2.20 20 May 2015 none AGPL-3.0 — Details →
0.2.19 11 May 2015 none AGPL-3.0 — Details →
0.2.18 13 Apr 2015 none AGPL-3.0 — Details →
0.2.17 04 Mar 2015 none AGPL-3.0 — Details →
0.2.16 17 Sep 2014 none AGPL-3.0 — Details →
0.2.15 19 Aug 2014 none AGPL-3.0 — Details →
0.2.14 21 Jul 2014 none AGPL-3.0 — Details →
0.2.12 15 Jul 2014 none AGPL-3.0 — Details →
0.2.11 14 Jul 2014 none AGPL-3.0 — Details →
0.2.10 19 Jun 2014 none AGPL-3.0 — Details →
0.2.9 05 Jun 2014 none AGPL-3.0 — Details →
0.2.8 27 May 2014 none AGPL-3.0 — Details →
0.2.7 09 May 2014 none AGPL-3.0 — Details →
0.2.6 28 Apr 2014 none AGPL-3.0 — Details →
0.2.5 16 Apr 2014 none AGPL-3.0 — Details →
0.2.4 09 Apr 2014 none AGPL-3.0 — Details →
0.2.3 09 Apr 2014 none AGPL-3.0 — Details →
0.2.2 03 Apr 2014 none AGPL-3.0 — Details →
0.2.1 02 Apr 2014 none AGPL-3.0 — Details →
0.2.0 01 Apr 2014 none AGPL-3.0 — Details →
0.1.12 28 Feb 2014 none — — Details →
0.1.11 21 Jan 2014 none — — Details →
0.1.10 15 Aug 2013 none — — Details →
0.1.9 01 Aug 2013 none — — Details →
0.1.8 02 Jul 2013 none — — Details →
0.1.7 27 Jun 2013 none — — Details →
0.1.6 07 Dec 2012 none — — Details →
0.1.5 21 Aug 2012 none — — Details →
0.1.4 15 Aug 2012 none — — Details →
0.1.3 06 Aug 2012 none — — Details →
0.1.2 03 Aug 2012 none — — Details →
0.1.1 26 Jul 2012 none — — Details →
0.1.0 24 Jul 2012 none — — Details →
0.0.1 23 Jul 2012 none — — Details →

All 63 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 moodle2cc

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 moodle2cc

Is moodle2cc safe to use?

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

Vulert scores moodle2cc 94/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 moodle2cc affected?

No. 0.2.47, 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 moodle2cc should I use?

0.2.47 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 moodle2cc have?

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

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

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