Vulnerability Database · Go · Package report

github.com/openark/orchestrator: vulnerability history, versions and safety

github.com/openark/orchestrator is a package in the Go ecosystem. Vulert records 1 vulnerability for it across 63 releases, first recorded in May 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded M1
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 github.com/openark/orchestrator v3.2.5+incompatible i

Updated on 23 Oct 2026

Action needed: v3.2.5+incompatible has 1 known vulnerability, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 71/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Key ecosystem project
  • Community Moderate

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 v3.2.5+incompatible — affected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 24 May 2022 i
  • Highest CVSS 6.1 i
  • With no published fix 0 i
  • Stars 5,775 i
  • OpenSSF scorecard 3/10 i
  • Last release 64 months ago i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by the Go module proxy, 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 github.com/openark/orchestrator, 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
v0.0.0-20250201180234-730db91f7034 01 Feb 2025 M1 Apache-2.0 Yes Details →
v0.0.0-20230228142011-f0d685e03253 28 Feb 2023 M1 Apache-2.0 Yes Details →
v0.0.0-20211026042331-f3ed38314b76 26 Oct 2021 M1 Apache-2.0 Yes Details →
v0.0.0-20210728055945-dabfb16fd891 28 Jul 2021 M1 Apache-2.0 Yes Details →
v0.0.0-20210727082307-c846d4366823 27 Jul 2021 M1 Apache-2.0 Yes Details →
v0.0.0-20210727064402-fd9918e43108 27 Jul 2021 M1 Apache-2.0 Yes Details →
v3.2.6-0.20210630100558-c7387314d2f3+incompatible 30 Jun 2021 M1 Apache-2.0 Yes Details →
v3.2.6-0.20210629063318-5817b9254a78+incompatible 29 Jun 2021 M1 Apache-2.0 Yes Details →
v3.2.6-0.20210624150003-5347e58301c5+incompatible 24 Jun 2021 M1 Apache-2.0 Yes Details →
v3.2.6-0.20210616061833-88867e684eb6+incompatible 16 Jun 2021 M1 Apache-2.0 Yes Details →
v3.2.6-0.20210604075601-dddec836a64e+incompatible 04 Jun 2021 M1 Apache-2.0 Yes Details →
v3.2.6-0.20210531070546-8dda751c5797+incompatible 31 May 2021 M1 Apache-2.0 Yes Details →
v3.2.5+incompatible 27 May 2021 M1 Apache-2.0 Yes Details →
v3.2.5-0.20210420103304-f818d8a13566+incompatible 20 Apr 2021 M1 Apache-2.0 Yes Details →
v3.2.5-0.20210413153221-96533fd2c4ea+incompatible 13 Apr 2021 M1 Apache-2.0 Yes Details →
v3.2.5-0.20210318051324-de1b1ecd3f65+incompatible 18 Mar 2021 M1 Apache-2.0 Yes Details →
v3.2.5-0.20210316073819-aaf9ea89a342+incompatible 16 Mar 2021 M1 Apache-2.0 Yes Details →
v0.0.0-20210221101858-340578e0d74b 21 Feb 2021 M1 Apache-2.0 Yes Details →
v3.2.4+incompatible 21 Feb 2021 M1 Apache-2.0 Yes Details →
v3.2.4-0.20210204142419-1fc4bb8dbf8f+incompatible 04 Feb 2021 M1 Apache-2.0 Yes Details →
v3.2.4-0.20210113172842-b3877d48f7a9+incompatible 13 Jan 2021 M1 Apache-2.0 Yes Details →
v3.2.4-0.20201211172652-3a63659e8ab4+incompatible 11 Dec 2020 M1 Apache-2.0 Yes Details →
v3.2.4-0.20201119124123-4b95079a0c5d+incompatible 19 Nov 2020 M1 Apache-2.0 Yes Details →
v3.2.4-0.20201101111606-b254d72e87fb+incompatible 01 Nov 2020 M1 Apache-2.0 Yes Details →
v3.2.4-0.20201002054741-fc5bb72f2050+incompatible 02 Oct 2020 M1 Apache-2.0 Yes Details →
v3.2.3+incompatible 04 Aug 2020 M1 Apache-2.0 Yes Details →
v3.2.3-0.20200708131538-fa49c3fe984c+incompatible 08 Jul 2020 M1 Apache-2.0 Yes Details →
v3.2.3-0.20200708124208-407cef918c4b+incompatible 08 Jul 2020 M1 Apache-2.0 Yes Details →
v3.2.2+incompatible 21 Jun 2020 M1 Apache-2.0 Yes Details →
v3.1.5-0.20200608125021-7c4c637b6a0a+incompatible 08 Jun 2020 M1 Apache-2.0 Yes Details →
v3.1.5-0.20200503130320-10f43b947384+incompatible 03 May 2020 M1 Apache-2.0 Yes Details →
v3.1.5-0.20200306100624-f7958637683a+incompatible 06 Mar 2020 M1 Apache-2.0 Yes Details →
v3.1.5-0.20200202110514-2c85642f73e8+incompatible 02 Feb 2020 M1 Apache-2.0 Yes Details →
v3.1.4+incompatible 26 Jan 2020 M1 Apache-2.0 Yes Details →
v3.1.3+incompatible 04 Dec 2019 M1 Apache-2.0 Yes Details →
v3.1.2+incompatible 25 Aug 2019 M1 Apache-2.0 Yes Details →
v3.1.1+incompatible 07 Jul 2019 M1 Apache-2.0 Yes Details →
v3.1.0+incompatible 02 Jul 2019 M1 Apache-2.0 Yes Details →
v3.0.14+incompatible 16 Jan 2019 M1 Apache-2.0 Yes Details →
v0.0.0-20190106063651-a2315bb61d5e 06 Jan 2019 M1 Apache-2.0 Yes Details →
v3.0.13+incompatible 28 Oct 2018 M1 Apache-2.0 Yes Details →
v3.0.12+incompatible 29 Aug 2018 M1 Apache-2.0 Yes Details →
v3.0.11+incompatible 22 May 2018 M1 Apache-2.0 Yes Details →
v3.0.10+incompatible 16 Apr 2018 M1 Apache-2.0 Yes Details →
v3.0.9+incompatible 12 Mar 2018 M1 Apache-2.0 Yes Details →
v3.0.8+incompatible 22 Feb 2018 M1 Apache-2.0 Yes Details →
v3.0.7+incompatible 18 Feb 2018 M1 Apache-2.0 Yes Details →
v3.0.6+incompatible 28 Jan 2018 M1 Apache-2.0 Yes Details →
v3.0.5+incompatible 17 Jan 2018 M1 Apache-2.0 Yes Details →
v3.0.3+incompatible 16 Nov 2017 M1 Apache-2.0 Yes Details →
v3.0.2+incompatible 12 Sep 2017 M1 Apache-2.0 Yes Details →
v2.1.6-0.20170815084310-441642b25392+incompatible 15 Aug 2017 M1 Apache-2.0 Yes Details →
v2.1.6-0.20170803070920-cfaef7b2eb1b+incompatible 03 Aug 2017 M1 Apache-2.0 Yes Details →
v2.1.5+incompatible 28 Jun 2017 M1 Apache-2.0 Yes Details →
v2.1.4+incompatible 11 Jun 2017 M1 Apache-2.0 Yes Details →
v2.1.2+incompatible 20 Apr 2017 M1 Apache-2.0 Yes Details →
v0.0.0-20170328095134-0aa62d8d0407 28 Mar 2017 M1 Apache-2.0 Yes Details →
v2.1.1-BETA+incompatible 28 Mar 2017 M1 Apache-2.0 Yes Details →
v2.1.0+incompatible 21 Mar 2017 M1 Apache-2.0 Yes Details →
v2.0.3+incompatible 07 Mar 2017 M1 Apache-2.0 Yes Details →
v2.0.2+incompatible 09 Feb 2017 M1 Apache-2.0 Yes Details →
v2.0.1+incompatible 07 Dec 2016 M1 Apache-2.0 Yes Details →
v2.0.0+incompatible 03 Dec 2016 M1 Apache-2.0 Yes 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

  • 2022 1

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

03 Vulnerabilities

Recorded vulnerabilities for github.com/openark/orchestrator

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →

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 github.com/openark/orchestrator

Is github.com/openark/orchestrator safe to use?

Vulert records 1 vulnerabilities for github.com/openark/orchestrator in Go: 0 critical, 0 high, 1 medium and 0 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 github.com/openark/orchestrator's Vulert package health score?

Vulert scores github.com/openark/orchestrator 71/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 github.com/openark/orchestrator affected?

Yes. v3.2.5+incompatible, the version you would install today, has 1 known vulnerability, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of github.com/openark/orchestrator should I use?

v3.2.5+incompatible 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 github.com/openark/orchestrator have?

1 vulnerability is recorded for github.com/openark/orchestrator in the Go ecosystem: 0 critical, 0 high, 1 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 github.com/openark/orchestrator vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/openark/orchestrator in the last 12 months, and the oldest entry in this database dates to 24 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 github.com/openark/orchestrator 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 github.com/openark/orchestrator for upcoming vulnerabilities?

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