Vulnerability Database · Go · Package report

github.com/devfile/registry-support/registry-library: vulnerability history, versions and safety

github.com/devfile/registry-support/registry-library is a package in the Go ecosystem. Vulert records 2 vulnerabilities for it across 120 releases, from Feb 2024 to Jun 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded M1 U1
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
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/devfile/registry-support/registry-library v0.0.0-20261018021816-4e20d3adfb5b i

Updated on 23 Oct 2026

Careful: v0.0.0-20261018021816-4e20d3adfb5b has 2 known vulnerabilities, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

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

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release v0.0.0-20261018021816-4e20d3adfb5b — affected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 05 Jun 2024 i
  • Highest CVSS 8.0 i
  • With no published fix 1 i
  • Stars 11 i
  • OpenSSF scorecard 6/10 i
  • Last release this month 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/devfile/registry-support/registry-library, 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-20261018021816-4e20d3adfb5b 18 Oct 2026 M1 U1 Apache-2.0 No Details →
v0.0.0-20261015052838-96daeb0e4ee4 15 Oct 2026 M1 U1 Apache-2.0 No Details →
v0.0.0-20261015051810-acb3d4225dc4 15 Oct 2026 M1 U1 Apache-2.0 No Details →
v0.0.0-20261012023552-1007821cf5f3 12 Oct 2026 M1 U1 Apache-2.0 No Details →
v0.0.0-20261002021000-21a67e3d75df 02 Oct 2026 M1 U1 Apache-2.0 No Details →
v0.0.0-20261001175618-b1ca803bcaaa 01 Oct 2026 M1 U1 Apache-2.0 No Details →
v0.0.0-20261001154425-d2970de915f1 01 Oct 2026 M1 U1 Apache-2.0 No Details →
v0.0.0-20260927060838-bf0aebf5d15f 27 Sep 2026 M1 U1 Apache-2.0 No Details →
v0.0.0-20260924070109-78e77badb17b 24 Sep 2026 M1 U1 Apache-2.0 No Details →
v0.0.0-20260920041552-f299e1e13e9e 20 Sep 2026 M1 U1 Apache-2.0 No Details →
v0.0.0-20260918012749-31e4656c9c5b 18 Sep 2026 M1 U1 Apache-2.0 No Details →
v0.0.0-20260917071509-59ff809640ff 17 Sep 2026 M1 U1 Apache-2.0 No Details →
v0.0.0-20260917060748-71854caafc58 17 Sep 2026 M1 U1 Apache-2.0 No Details →
v0.0.0-20260913025219-1d5829026c6c 13 Sep 2026 M1 U1 Apache-2.0 No Details →
v0.0.0-20260906030509-9eeae5aa1b0c 06 Sep 2026 M1 U1 Apache-2.0 No Details →
v0.0.0-20260903142517-341adf3faa86 03 Sep 2026 M1 U1 Apache-2.0 No Details →
v0.0.0-20260903132711-930bbe0bb51f 03 Sep 2026 M1 U1 Apache-2.0 No Details →
v0.0.0-20260830010451-06a3a7146533 30 Aug 2026 M1 U1 Apache-2.0 No Details →
v0.0.0-20260829210935-b9890780c864 29 Aug 2026 M1 U1 Apache-2.0 No Details →
v0.0.0-20260823022945-2db9ab4bd5bc 23 Aug 2026 M1 U1 Apache-2.0 No Details →
v0.0.0-20260821060807-9d05774f6ddc 21 Aug 2026 M1 U1 Apache-2.0 No Details →
v0.0.0-20260817004953-585062dc9253 17 Aug 2026 M1 U1 Apache-2.0 No Details →
v0.0.0-20260813180526-40cdd53d1768 13 Aug 2026 M1 U1 Apache-2.0 No Details →
v0.0.0-20260810134442-def670c9163b 10 Aug 2026 M1 U1 Apache-2.0 No Details →
v0.0.0-20260804140957-4d125e906ea6 04 Aug 2026 M1 U1 Apache-2.0 No Details →
v0.0.0-20260725144019-6fea88b91ca5 25 Jul 2026 M1 U1 Apache-2.0 No Details →
v0.0.0-20260724003105-f36613148425 24 Jul 2026 M1 U1 Apache-2.0 No Details →
v0.0.0-20260723132447-52acc33cb944 23 Jul 2026 M1 U1 Apache-2.0 No Details →
v0.0.0-20260718201812-2bb758e8b3a7 18 Jul 2026 M1 U1 Apache-2.0 No Details →
v0.0.0-20260716211440-f6034af8d385 16 Jul 2026 M1 U1 Apache-2.0 No Details →
v0.0.0-20260715183922-db79d18c0036 15 Jul 2026 M1 U1 Apache-2.0 No Details →
v0.0.0-20260714143453-ed4a90d4f9b1 14 Jul 2026 M1 U1 Apache-2.0 No Details →
v0.0.0-20260713144849-86951ec6bd40 13 Jul 2026 M1 U1 Apache-2.0 No Details →
v0.0.0-20260612211221-d5914fa0818b 12 Jun 2026 M1 U1 Apache-2.0 No Details →
v0.0.0-20260608202855-5de5658dc71c 08 Jun 2026 M1 U1 Apache-2.0 No Details →
v0.0.0-20260601133403-23a1ae3ec431 01 Jun 2026 M1 U1 Apache-2.0 No Details →
v0.0.0-20260504210021-d59185246e72 04 May 2026 M1 U1 Apache-2.0 No Details →
v0.0.0-20260424025531-2be83b59a2b9 24 Apr 2026 M1 U1 Apache-2.0 No Details →
v0.0.0-20260415051950-ee458437f2b9 15 Apr 2026 M1 U1 Apache-2.0 No Details →
v0.0.0-20260415044134-9bc87eca79f6 15 Apr 2026 M1 U1 Apache-2.0 No Details →
v0.0.0-20260412014650-2d64be5df2ae 12 Apr 2026 M1 U1 Apache-2.0 No Details →
v0.0.0-20260405214547-0fa706704010 05 Apr 2026 M1 U1 Apache-2.0 No Details →
v0.0.0-20260327015535-a8050771eff1 27 Mar 2026 M1 U1 Apache-2.0 No Details →
v0.0.0-20260326085549-fe5d5f526a65 26 Mar 2026 M1 U1 Apache-2.0 No Details →
v0.0.0-20260320023350-5758076ff2ea 20 Mar 2026 M1 U1 Apache-2.0 No Details →
v0.0.0-20260318144410-f3a8c06eb525 18 Mar 2026 M1 U1 Apache-2.0 No Details →
v0.0.0-20260313132401-1432baf5df72 13 Mar 2026 M1 U1 Apache-2.0 No Details →
v0.0.0-20260225230820-0c749cf2d783 25 Feb 2026 M1 U1 Apache-2.0 No Details →
v0.0.0-20260225044720-87f5e3bbeb2c 25 Feb 2026 M1 U1 Apache-2.0 No Details →
v0.0.0-20260220204016-cd1f540c02ad 20 Feb 2026 M1 U1 Apache-2.0 No Details →
v0.0.0-20260219225510-1dbad43dde8c 19 Feb 2026 M1 U1 Apache-2.0 No Details →
v0.0.0-20260211150056-51b1eb85b0c1 11 Feb 2026 M1 U1 Apache-2.0 No Details →
v0.0.0-20260210192332-278d9f4a7337 10 Feb 2026 M1 U1 Apache-2.0 No Details →
v0.0.0-20260210150622-5ecc124d1b27 10 Feb 2026 M1 U1 Apache-2.0 No Details →
v0.0.0-20260206051742-f457764950e2 06 Feb 2026 M1 U1 Apache-2.0 No Details →
v0.0.0-20260204164904-fd682ce3ef90 04 Feb 2026 M1 U1 Apache-2.0 No Details →
v0.0.0-20260203205219-d43ddf108c10 03 Feb 2026 M1 U1 Apache-2.0 No Details →
v0.0.0-20260203183145-3a2a13facf08 03 Feb 2026 M1 U1 Apache-2.0 No Details →
v0.0.0-20260203180555-26709486798d 03 Feb 2026 M1 U1 Apache-2.0 No Details →
v0.0.0-20260203163129-5e4c7a06b46d 03 Feb 2026 M1 U1 Apache-2.0 No Details →
v0.0.0-20260114143356-b52d45bd6954 14 Jan 2026 M1 U1 Apache-2.0 No Details →
v0.0.0-20260109043331-9fff38c4fc8d 09 Jan 2026 M1 U1 Apache-2.0 No Details →
v0.0.0-20251224144231-0b6001b14a30 24 Dec 2025 M1 U1 Apache-2.0 No Details →
v0.0.0-20251217043412-21cf64c1cc3a 17 Dec 2025 M1 U1 Apache-2.0 No Details →
v0.0.0-20251212120058-c6ca2d2b9569 12 Dec 2025 M1 U1 Apache-2.0 No Details →
v0.0.0-20251210123230-25ee9004b602 10 Dec 2025 M1 U1 Apache-2.0 No Details →
v0.0.0-20251205043209-7dee125099f4 05 Dec 2025 M1 U1 Apache-2.0 No Details →
v0.0.0-20251203111902-da3eabd4c6fb 03 Dec 2025 M1 U1 Apache-2.0 No Details →
v0.0.0-20251128043549-c19615eddc34 28 Nov 2025 M1 U1 Apache-2.0 No Details →
v0.0.0-20251127031022-511c0868b50a 27 Nov 2025 M1 U1 Apache-2.0 No Details →
v0.0.0-20251121095817-7c3f1401ba75 21 Nov 2025 M1 U1 Apache-2.0 No Details →
v0.0.0-20251119170631-521d0c7ab950 19 Nov 2025 M1 U1 Apache-2.0 No Details →
v0.0.0-20251119092456-b9718c1a2773 19 Nov 2025 M1 U1 Apache-2.0 No Details →
v0.0.0-20251114150755-f7d8acab5871 14 Nov 2025 M1 U1 Apache-2.0 No Details →
v0.0.0-20251114145413-645ea81f32f5 14 Nov 2025 M1 U1 Apache-2.0 No Details →
v0.0.0-20251113142147-d3b8fb5dbea4 13 Nov 2025 M1 U1 Apache-2.0 No Details →
v0.0.0-20251014075717-38f75507e2e2 14 Oct 2025 M1 U1 Apache-2.0 No Details →
v0.0.0-20251010084905-2fa376ed3f19 10 Oct 2025 M1 U1 Apache-2.0 No Details →
v0.0.0-20251007073651-6529e4bf5055 07 Oct 2025 M1 U1 Apache-2.0 No Details →
v0.0.0-20251002043450-26d6cddfb4a7 02 Oct 2025 M1 U1 Apache-2.0 No Details →
v0.0.0-20251001012635-92b8d238a3d8 01 Oct 2025 M1 U1 Apache-2.0 No Details →
v0.0.0-20250930073052-1198aab3547b 30 Sep 2025 M1 U1 Apache-2.0 No Details →
v0.0.0-20250926041224-2da556e5d332 26 Sep 2025 M1 U1 Apache-2.0 No Details →
v0.0.0-20250925044554-363ab39626d4 25 Sep 2025 M1 U1 Apache-2.0 No Details →
v0.0.0-20250924193729-ca676ea8620e 24 Sep 2025 M1 U1 Apache-2.0 No Details →
v0.0.0-20250924062439-99e312870871 24 Sep 2025 M1 U1 Apache-2.0 No Details →
v0.0.0-20250919073824-c66ccb6c9c90 19 Sep 2025 M1 U1 Apache-2.0 No Details →
v0.0.0-20250918142230-3acb3012b9f0 18 Sep 2025 M1 U1 Apache-2.0 No Details →
v0.0.0-20250918135025-6c0e4508b007 18 Sep 2025 M1 U1 Apache-2.0 No Details →
v0.0.0-20250917075322-61a38bdc1bf2 17 Sep 2025 M1 U1 Apache-2.0 No Details →
v0.0.0-20250916135043-7c79b5bc3f60 16 Sep 2025 M1 U1 Apache-2.0 No Details →
v0.0.0-20250912123335-b49c5ddfba87 12 Sep 2025 M1 U1 Apache-2.0 No Details →
v0.0.0-20250911115220-4d68fc92a2f6 11 Sep 2025 M1 U1 Apache-2.0 No Details →
v0.0.0-20250910004814-893fa368e3c5 10 Sep 2025 M1 U1 Apache-2.0 No Details →
v0.0.0-20250909083053-d0ebec77bb61 09 Sep 2025 M1 U1 Apache-2.0 No Details →
v0.0.0-20250909010913-3f907d1748e4 09 Sep 2025 M1 U1 Apache-2.0 No Details →
v0.0.0-20250908202542-baf6f7360db6 08 Sep 2025 M1 U1 Apache-2.0 No Details →
v0.0.0-20250819104712-59dcddfd4478 19 Aug 2025 M1 U1 Apache-2.0 No Details →
v0.0.0-20250805232544-44456dbfc435 05 Aug 2025 M1 U1 Apache-2.0 No Details →
v0.0.0-20250805231342-6bcfef8f31b5 05 Aug 2025 M1 U1 Apache-2.0 No Details →
v0.0.0-20250805230205-97fd5f3bca2d 05 Aug 2025 M1 U1 — No Details →
v0.0.0-20250805174630-7498ab6711f6 05 Aug 2025 M1 U1 — No Details →
v0.0.0-20250730032739-26fa21cd87b1 30 Jul 2025 M1 U1 — No Details →
v0.0.0-20250723152826-c8cc340a5c2d 23 Jul 2025 M1 U1 — No Details →
v0.0.0-20250613024858-196c09f2594c 13 Jun 2025 M1 U1 — No Details →
v0.0.0-20250604093314-74e25e82969e 04 Jun 2025 M1 U1 — No Details →
v0.0.0-20250530213242-57e1b483debf 30 May 2025 M1 U1 — No Details →
v0.0.0-20250517120356-4f8157586727 17 May 2025 M1 U1 — No Details →
v0.0.0-20250514091636-29b85f3ecffe 14 May 2025 M1 U1 — No Details →
v0.0.0-20250512192747-5c5f8c3db330 12 May 2025 M1 U1 — No Details →
v0.0.0-20250509153431-3f0d30522949 09 May 2025 M1 U1 — No Details →
v0.0.0-20250501170128-6175d8e5ab34 01 May 2025 M1 U1 — No Details →
v0.0.0-20250430072243-f0f3849ea603 30 Apr 2025 M1 U1 — No Details →
v0.0.0-20250425204342-ccb2c647ec2e 25 Apr 2025 M1 U1 — No Details →
v0.0.0-20250425141453-ea08b67c1a10 25 Apr 2025 M1 U1 — No Details →
v0.0.0-20250424200831-857491a874eb 24 Apr 2025 M1 U1 — No Details →
v0.0.0-20250424173623-453269888b77 24 Apr 2025 M1 U1 — No Details →
v0.0.0-20250121094327-a43b145b50f6 21 Jan 2025 M1 U1 — No Details →
v0.0.0-20250110204052-5dba01d70304 10 Jan 2025 M1 U1 — No Details →
v0.0.0-20250110194536-ab12a173b096 10 Jan 2025 M1 U1 — No Details →

The newest 120 of 298 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 2

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

03 Vulnerabilities

Recorded vulnerabilities for github.com/devfile/registry-support/registry-library

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 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/devfile/registry-support/registry-library

Is github.com/devfile/registry-support/registry-library safe to use?

Vulert records 2 vulnerabilities for github.com/devfile/registry-support/registry-library in Go: 0 critical, 0 high, 1 medium and 0 low, plus 1 not yet rated. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is github.com/devfile/registry-support/registry-library's Vulert package health score?

Vulert scores github.com/devfile/registry-support/registry-library 60/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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of github.com/devfile/registry-support/registry-library affected?

Yes. v0.0.0-20261018021816-4e20d3adfb5b, the version you would install today, has 2 known vulnerabilities, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

How many vulnerabilities does github.com/devfile/registry-support/registry-library have?

2 vulnerabilities are recorded for github.com/devfile/registry-support/registry-library in the Go ecosystem: 0 critical, 0 high, 1 medium and 0 low, plus 1 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new github.com/devfile/registry-support/registry-library vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/devfile/registry-support/registry-library in the last 12 months, and the oldest entry in this database dates to 14 Feb 2024. 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/devfile/registry-support/registry-library 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/devfile/registry-support/registry-library for upcoming vulnerabilities?

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