Vulnerability Database · Go · Package report

github.com/openshift/build-machinery-go: vulnerability history, versions and safety

github.com/openshift/build-machinery-go is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the Go 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.

Vulert verdict on github.com/openshift/build-machinery-go v0.0.0-20260902143904-520f675c892b i

Updated on 23 Oct 2026

Good news: v0.0.0-20260902143904-520f675c892b, the version you would install today, has no known vulnerabilities.

Package health score 68/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Quiet

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

  • Current release v0.0.0-20260902143904-520f675c892b — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 15 i
  • OpenSSF scorecard 3/10 i
  • Last release 1 month 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/openshift/build-machinery-go, 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-20260902143904-520f675c892b 02 Sep 2026 none Apache-2.0 — Details →
v0.0.0-20260629141115-154a2b810491 29 Jun 2026 none Apache-2.0 — Details →
v0.0.0-20260625204636-d138cd032dd0 25 Jun 2026 none Apache-2.0 — Details →
v0.0.0-20260427155009-b879704ce51f 27 Apr 2026 none Apache-2.0 — Details →
v0.0.0-20260417161732-3aa8f237837a 17 Apr 2026 none Apache-2.0 — Details →
v0.0.0-20260417131728-a8fff83d4169 17 Apr 2026 none Apache-2.0 — Details →
v0.0.0-20251023084048-5d77c1a5e5af 23 Oct 2025 none Apache-2.0 — Details →
v0.0.0-20251020112516-49aa9f5db6d8 20 Oct 2025 none Apache-2.0 — Details →
v0.0.0-20251017080826-c3556e1a76a5 17 Oct 2025 none Apache-2.0 — Details →
v0.0.0-20250806130835-622c0378eb0d 06 Aug 2025 none Apache-2.0 — Details →
v0.0.0-20250602125535-1b6d00b8c37c 02 Jun 2025 none Apache-2.0 — Details →
v0.0.0-20250530140348-dc5b2804eeee 30 May 2025 none Apache-2.0 — Details →
v0.0.0-20250530114742-9e4b4051a948 30 May 2025 none Apache-2.0 — Details →
v0.0.0-20250414185254-3ce8e800ceda 14 Apr 2025 none Apache-2.0 — Details →
v0.0.0-20250211133638-a00a772ae1a2 11 Feb 2025 none Apache-2.0 — Details →
v0.0.0-20250102153059-e85a1a7ecb5c 02 Jan 2025 none Apache-2.0 — Details →
v0.0.0-20250102145759-935dfeae1c07 02 Jan 2025 none Apache-2.0 — Details →
v0.0.0-20241126220845-0de670012c09 26 Nov 2024 none Apache-2.0 — Details →
v0.0.0-20241031155326-6ae126a9cb72 31 Oct 2024 none Apache-2.0 — Details →
v0.0.0-20241030130011-ee12ed0f0273 30 Oct 2024 none Apache-2.0 — Details →
v0.0.0-20241025131534-5f3bc3c56265 25 Oct 2024 none Apache-2.0 — Details →
v0.0.0-20240910153727-5725581bdf8f 10 Sep 2024 none Apache-2.0 — Details →
v0.0.0-20240613134546-bcaa8bad8316 13 Jun 2024 none Apache-2.0 — Details →
v0.0.0-20240613134303-8359781da660 13 Jun 2024 none Apache-2.0 — Details →
v0.0.0-20240613123942-8486cae47c70 13 Jun 2024 none Apache-2.0 — Details →
v0.0.0-20240419090851-af9c868bcf52 19 Apr 2024 none Apache-2.0 — Details →
v0.0.0-20231128094528-1e9b1b0595c8 28 Nov 2023 none Apache-2.0 — Details →
v0.0.0-20231127184514-b383cb525fcf 27 Nov 2023 none Apache-2.0 — Details →
v0.0.0-20231127145712-329a66664813 27 Nov 2023 none Apache-2.0 — Details →
v0.0.0-20231127142359-2e12006955db 27 Nov 2023 none Apache-2.0 — Details →
v0.0.0-20230824093055-6a18da01283c 24 Aug 2023 none Apache-2.0 — Details →
v0.0.0-20230816154005-5a38e1bfd880 16 Aug 2023 none Apache-2.0 — Details →
v0.0.0-20230816093341-5f3a4e14f972 16 Aug 2023 none Apache-2.0 — Details →
v0.0.0-20230306181456-d321ffa04533 06 Mar 2023 none Apache-2.0 — Details →
v0.0.0-20230301101616-cc7b88a966e2 01 Mar 2023 none Apache-2.0 — Details →
v0.0.0-20230228230858-4cd708338479 28 Feb 2023 none Apache-2.0 — Details →
v0.0.0-20220913142420-e25cf57ea46d 13 Sep 2022 none Apache-2.0 — Details →
v0.0.0-20220909124648-e003344f49e8 09 Sep 2022 none Apache-2.0 — Details →
v0.0.0-20220908181933-829eaaa6b38c 08 Sep 2022 none Apache-2.0 — Details →
v0.0.0-20220720161851-9b4f0386f6b0 20 Jul 2022 none Apache-2.0 — Details →
v0.0.0-20220720160021-c879521fd345 20 Jul 2022 none Apache-2.0 — Details →
v0.0.0-20220714103123-0a8c0ac8828b 14 Jul 2022 none Apache-2.0 — Details →
v0.0.0-20220705175737-d0a947e624f9 05 Jul 2022 none Apache-2.0 — Details →
v0.0.0-20220429084610-baff9f8d23b3 29 Apr 2022 none Apache-2.0 — Details →
v0.0.0-20220121085309-f94edc2d6874 21 Jan 2022 none Apache-2.0 — Details →
v0.0.0-20220119125426-d173f95c14a6 19 Jan 2022 none Apache-2.0 — Details →
v0.0.0-20211221232219-d4aa007f5295 21 Dec 2021 none Apache-2.0 — Details →
v0.0.0-20211221165021-8d8fec7ad2c7 21 Dec 2021 none Apache-2.0 — Details →
v0.0.0-20211221164819-4024613928f1 21 Dec 2021 none Apache-2.0 — Details →
v0.0.0-20211221163156-70201ca58bc0 21 Dec 2021 none Apache-2.0 — Details →
v0.0.0-20211221160956-02e5d5c59eb9 21 Dec 2021 none Apache-2.0 — Details →
v0.0.0-20211213093930-7e33a7eb4ce3 13 Dec 2021 none Apache-2.0 — Details →
v0.0.0-20210922160744-a9caf93aef90 22 Sep 2021 none Apache-2.0 — Details →
v0.0.0-20210806203541-4ea9b6da3a37 06 Aug 2021 none Apache-2.0 — Details →
v0.0.0-20210806170459-ca2f2eb8b4ab 06 Aug 2021 none Apache-2.0 — Details →
v0.0.0-20210712174854-1bb7fd1518d3 12 Jul 2021 none Apache-2.0 — Details →
v0.0.0-20210712160054-9e7d294fa80c 12 Jul 2021 none Apache-2.0 — Details →
v0.0.0-20210712153124-aa83de7d90e3 12 Jul 2021 none Apache-2.0 — Details →
v0.0.0-20210702090207-9c7b89e8633a 02 Jul 2021 none Apache-2.0 — Details →
v0.0.0-20210701182933-efa47ed39f2e 01 Jul 2021 none Apache-2.0 — Details →
v0.0.0-20210701084444-6ed14425650f 01 Jul 2021 none Apache-2.0 — Details →
v0.0.0-20210629154307-e2e0f5a32472 29 Jun 2021 none Apache-2.0 — Details →
v0.0.0-20210629142708-5d932f98a3fc 29 Jun 2021 none Apache-2.0 — Details →
v0.0.0-20210628133618-bd58a901bbfe 28 Jun 2021 none Apache-2.0 — Details →
v0.0.0-20210614124016-792d61687197 14 Jun 2021 none Apache-2.0 — Details →
v0.0.0-20210611103944-dea4bddc5a01 11 Jun 2021 none Apache-2.0 — Details →
v0.0.0-20210609183145-fa67b3b43004 09 Jun 2021 none Apache-2.0 — Details →
v0.0.0-20210423112049-9415d7ebd33e 23 Apr 2021 none Apache-2.0 — Details →
v0.0.0-20210422090345-375a97024506 22 Apr 2021 none Apache-2.0 — Details →
v0.0.0-20210413112106-60cf6ea633f9 13 Apr 2021 none Apache-2.0 — Details →
v0.0.0-20210412141922-56d6e6c51074 12 Apr 2021 none Apache-2.0 — Details →
v0.0.0-20210409131504-b1828cc0cdad 09 Apr 2021 none Apache-2.0 — Details →
v0.0.0-20210209125900-0da259a2c359 09 Feb 2021 none Apache-2.0 — Details →
v0.0.0-20210202172015-e79b2a6f0d96 02 Feb 2021 none Apache-2.0 — Details →
v0.0.0-20210115170933-e575b44a7a94 15 Jan 2021 none Apache-2.0 — Details →
v0.0.0-20200917070002-f171684f77ab 17 Sep 2020 none Apache-2.0 — Details →
v0.0.0-20200819073603-48aa266c95f7 19 Aug 2020 none Apache-2.0 — Details →
v0.0.0-20200731024703-cd7e6e844b55 31 Jul 2020 none Apache-2.0 — Details →
v0.0.0-20200713135615-1f43d26dccc7 13 Jul 2020 none Apache-2.0 — Details →
v0.0.0-20200512074546-3744767c4131 12 May 2020 none Apache-2.0 — Details →
v0.0.0-20200503165909-aca6df7a454a 03 May 2020 none Apache-2.0 — Details →
v0.0.0-20200424080330-082bf86082cc 24 Apr 2020 none Apache-2.0 — Details →
v0.0.0-20200211121458-5e3d6e570160 11 Feb 2020 none Apache-2.0 — Details →
v0.0.0-20200211091036-26d0e15cfbd5 11 Feb 2020 none Apache-2.0 — Details →
v0.0.0-20200210090402-3b072832771e 10 Feb 2020 none Apache-2.0 — Details →
v0.0.0-20200206145628-a8567613b05c 06 Feb 2020 none Apache-2.0 — Details →
v0.0.0-20200206103427-bda5bbfa8747 06 Feb 2020 none Apache-2.0 — Details →
v0.0.0-20200206102057-f4a4e4ec78a4 06 Feb 2020 none Apache-2.0 — Details →
v0.0.0-20200205161356-ef115f5adc73 05 Feb 2020 none Apache-2.0 — Details →
v0.0.0-20200203214626-abcaf13a2e71 03 Feb 2020 none Apache-2.0 — Details →

All 90 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 github.com/openshift/build-machinery-go

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 github.com/openshift/build-machinery-go

Is github.com/openshift/build-machinery-go safe to use?

Vulert has no vulnerabilities on record for github.com/openshift/build-machinery-go in Go 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 github.com/openshift/build-machinery-go's Vulert package health score?

Vulert scores github.com/openshift/build-machinery-go 68/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 github.com/openshift/build-machinery-go affected?

No. v0.0.0-20260902143904-520f675c892b, 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 github.com/openshift/build-machinery-go should I use?

v0.0.0-20260902143904-520f675c892b 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/openshift/build-machinery-go have?

0 vulnerabilities are recorded for github.com/openshift/build-machinery-go in the Go 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 github.com/openshift/build-machinery-go vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/openshift/build-machinery-go 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 github.com/openshift/build-machinery-go 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/openshift/build-machinery-go for upcoming vulnerabilities?

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