Vulnerability Database · Maven · Package report

com.coravy.hudson.plugins.github:github: vulnerability history, versions and safety

com.coravy.hudson.plugins.github:github is a package in the Maven ecosystem. Vulert records 5 vulnerabilities for it across 95 releases, from May 2022 to Oct 2023. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
5 vulnerabilities recorded H2 M2 L1
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.

Vulert verdict on com.coravy.hudson.plugins.github:github 0.2 i

Updated on 23 Oct 2026

Action needed: 0.2 has 5 known vulnerabilities, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 56/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Little adoption
  • Community Quiet

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release 0.2 — affected i
  • Vulnerabilities on record 5 over 1 year · 0 in the last year i
  • Latest disclosure 25 Oct 2023 i
  • Highest CVSS 8.8 i
  • With no published fix 0 i
  • Stars 300 i
  • OpenSSF scorecard 3/10 i
  • Last release 197 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by Maven Central, 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 com.coravy.hudson.plugins.github:github, 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.47.0 10 Jun 2026 none MIT — Details →
1.46.0.1 22 Apr 2026 none MIT — Details →
1.46.0 12 Feb 2026 none MIT — Details →
1.45.0 06 Sep 2025 none MIT — Details →
1.44.0 20 Jul 2025 none MIT — Details →
1.43.0 28 Mar 2025 none MIT — Details →
1.42.0 21 Feb 2025 none MIT — Details →
1.41.0 23 Jan 2025 none MIT — Details →
1.40.0 09 Aug 2024 none MIT — Details →
1.39.0 16 May 2024 none MIT — Details →
1.22.0 13 Feb 2024 H2 M2 L1 MIT Yes Details →
1.22.3 13 Feb 2024 H2 M2 L1 MIT Yes Details →
1.15.0 13 Feb 2024 H2 M2 L1 Apache-2.0 Yes Details →
1.37.2 13 Feb 2024 H1 MIT Yes Details →
1.7 13 Feb 2024 H2 M2 L1 — Yes Details →
0.3 13 Feb 2024 H2 M2 L1 — Yes Details →
1.1 13 Feb 2024 H2 M2 L1 — Yes Details →
1.13.2 13 Feb 2024 H2 M2 L1 Apache-2.0 Yes Details →
1.13.3 13 Feb 2024 H2 M2 L1 Apache-2.0 Yes Details →
1.14.2 13 Feb 2024 H2 M2 L1 Apache-2.0 Yes Details →
1.36.0 13 Feb 2024 H1 MIT Yes Details →
0.5 13 Feb 2024 H2 M2 L1 — Yes Details →
0.9 13 Feb 2024 H2 M2 L1 — Yes Details →
1.13.0-alpha-1 13 Feb 2024 H2 M2 L1 Apache-2.0 Yes Details →
1.18.2 13 Feb 2024 H2 M2 L1 MIT Yes Details →
1.19.0 13 Feb 2024 H2 M2 L1 MIT Yes Details →
1.19.2 13 Feb 2024 H2 M2 L1 MIT Yes Details →
1.22.2 13 Feb 2024 H2 M2 L1 MIT Yes Details →
1.22.4 13 Feb 2024 H2 M2 L1 MIT Yes Details →
1.34.5 13 Feb 2024 H1 MIT Yes Details →
1.35.0 13 Feb 2024 H1 MIT Yes Details →
1.9.1 13 Feb 2024 H2 M2 L1 — Yes Details →
1.23.0 13 Feb 2024 H2 M2 L1 MIT Yes Details →
1.26.2 13 Feb 2024 H2 M2 L1 MIT Yes Details →
1.29.2 13 Feb 2024 H1 L1 MIT Yes Details →
1.30.0 13 Feb 2024 H1 L1 MIT Yes Details →
1.34.1.1 13 Feb 2024 H1 L1 MIT Yes Details →
1.4 13 Feb 2024 H2 M2 L1 — Yes Details →
1.12.0 13 Feb 2024 H2 M2 L1 Apache-2.0 Yes Details →
1.18.0 13 Feb 2024 H2 M2 L1 MIT Yes Details →
1.14.0-alpha-1 13 Feb 2024 H2 M2 L1 Apache-2.0 Yes Details →
1.20.0 13 Feb 2024 H2 M2 L1 MIT Yes Details →
1.31.0 13 Feb 2024 H1 L1 MIT Yes Details →
1.11.3 13 Feb 2024 H2 M2 L1 Apache-2.0 Yes Details →
1.25.1 13 Feb 2024 H2 M2 L1 MIT Yes Details →
1.36.1 13 Feb 2024 H1 MIT Yes Details →
1.38.0 13 Feb 2024 none MIT — Details →
0.4 13 Feb 2024 H2 M2 L1 — Yes Details →
1.13.0-alpha-2 13 Feb 2024 H2 M2 L1 Apache-2.0 Yes Details →
1.19.1 13 Feb 2024 H2 M2 L1 MIT Yes Details →
1.29.0 13 Feb 2024 H2 M2 L1 MIT Yes Details →
1.29.3 13 Feb 2024 H1 L1 MIT Yes Details →
1.29.5 13 Feb 2024 H1 L1 MIT Yes Details →
1.37.3 13 Feb 2024 H1 MIT Yes Details →
1.10 13 Feb 2024 H2 M2 L1 Apache-2.0 Yes Details →
1.16.0 13 Feb 2024 H2 M2 L1 Apache-2.0 Yes Details →
1.17.0 13 Feb 2024 H2 M2 L1 Apache-2.0 Yes Details →
1.21.0 13 Feb 2024 H2 M2 L1 MIT Yes Details →
1.23.1 13 Feb 2024 H2 M2 L1 MIT Yes Details →
1.26.1 13 Feb 2024 H2 M2 L1 MIT Yes Details →
1.28.0 13 Feb 2024 H2 M2 L1 MIT Yes Details →
1.28.1 13 Feb 2024 H2 M2 L1 MIT Yes Details →
1.34.3 13 Feb 2024 H1 L1 MIT Yes Details →
1.21.1 13 Feb 2024 H2 M2 L1 MIT Yes Details →
1.32.0 13 Feb 2024 H1 L1 MIT Yes Details →
1.33.1 13 Feb 2024 H1 L1 MIT Yes Details →
1.34.3.1 13 Feb 2024 H1 L1 MIT Yes Details →
1.37.1 13 Feb 2024 H1 MIT Yes Details →
1.9 13 Feb 2024 H2 M2 L1 — Yes Details →
0.6 13 Feb 2024 H2 M2 L1 — Yes Details →
1.13.0 13 Feb 2024 H2 M2 L1 Apache-2.0 Yes Details →
1.14.0-alpha-2 13 Feb 2024 H2 M2 L1 Apache-2.0 Yes Details →
1.24.0 13 Feb 2024 H2 M2 L1 MIT Yes Details →
1.8 13 Feb 2024 H2 M2 L1 — Yes Details →
0.7 13 Feb 2024 H2 M2 L1 — Yes Details →
1.17.1 13 Feb 2024 H2 M2 L1 Apache-2.0 Yes Details →
1.26.0 13 Feb 2024 H2 M2 L1 MIT Yes Details →
1.29.1 13 Feb 2024 H2 L1 MIT Yes Details →
1.34.1 13 Feb 2024 H1 L1 MIT Yes Details →
1.34.2 13 Feb 2024 H1 L1 MIT Yes Details →
1.11.1 13 Feb 2024 H2 M2 L1 Apache-2.0 Yes Details →
1.6 13 Feb 2024 H2 M2 L1 — Yes Details →
1.19.3 13 Feb 2024 H2 M2 L1 MIT Yes Details →
1.37.3.1 13 Feb 2024 none MIT — Details →
1.0 13 Feb 2024 H2 M2 L1 — Yes Details →
1.18.1 13 Feb 2024 H2 M2 L1 MIT Yes Details →
1.22.1 13 Feb 2024 H2 M2 L1 MIT Yes Details →
1.29.4 13 Feb 2024 H1 L1 MIT Yes Details →
1.3 13 Feb 2024 H2 M2 L1 — Yes Details →
1.11.2 13 Feb 2024 H2 M2 L1 Apache-2.0 Yes Details →
1.14.1 13 Feb 2024 H2 M2 L1 Apache-2.0 Yes Details →
1.34.4 13 Feb 2024 H1 L1 MIT Yes Details →
1.37.0 13 Feb 2024 H1 MIT Yes Details →
1.11 13 Feb 2024 H2 M2 L1 Apache-2.0 Yes Details →
1.12.1 13 Feb 2024 H2 M2 L1 Apache-2.0 Yes Details →
1.2 13 Feb 2024 H2 M2 L1 — Yes Details →
1.33.0 13 Feb 2024 H1 L1 MIT Yes Details →
1.14.0 13 Feb 2024 H2 M2 L1 Apache-2.0 Yes Details →
1.25.0 13 Feb 2024 H2 M2 L1 MIT Yes Details →
1.12.0-alpha-1 13 Feb 2024 H2 M2 L1 Apache-2.0 Yes Details →
1.5 13 Feb 2024 H2 M2 L1 — Yes Details →
1.13.1 13 Feb 2024 H2 M2 L1 — Yes Details →
1.27.0 13 Feb 2024 H2 M2 L1 — Yes Details →
0.8 13 Feb 2024 H2 M2 L1 — Yes Details →
1.34.0 13 Feb 2024 H1 L1 — Yes Details →
0.1 20 May 2010 H2 M2 L1 — Yes Details →
0.2 20 May 2010 H2 M2 L1 — Yes Details →

All 107 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 4
  • 2023 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 5 were recorded in the last 12 months.

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 com.coravy.hudson.plugins.github:github

Is com.coravy.hudson.plugins.github:github safe to use?

Vulert records 5 vulnerabilities for com.coravy.hudson.plugins.github:github in Maven: 0 critical, 2 high, 2 medium and 1 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is com.coravy.hudson.plugins.github:github's Vulert package health score?

Vulert scores com.coravy.hudson.plugins.github:github 56/100, which reads as usable, but worth attention. 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 com.coravy.hudson.plugins.github:github affected?

Yes. 0.2, the version you would install today, has 5 known vulnerabilities, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of com.coravy.hudson.plugins.github:github should I use?

1.47.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 com.coravy.hudson.plugins.github:github have?

5 vulnerabilities are recorded for com.coravy.hudson.plugins.github:github in the Maven ecosystem: 0 critical, 2 high, 2 medium and 1 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new com.coravy.hudson.plugins.github:github vulnerabilities disclosed?

0 vulnerabilities were recorded for com.coravy.hudson.plugins.github:github in the last 12 months, and the oldest entry in this database dates to 13 May 2022. 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 com.coravy.hudson.plugins.github:github 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 com.coravy.hudson.plugins.github:github for upcoming vulnerabilities?

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