VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/goodrain/rainbond-oam: vulnerability history, versions and safety

github.com/goodrain/rainbond-oam 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.

See all github.com/goodrain/rainbond-oam vulnerabilities

Vulert verdict on github.com/goodrain/rainbond-oam v0.0.0-20260616140235-3b1f45c9b5d6 i

Updated on 23 Oct 2026

Good news: v0.0.0-20260616140235-3b1f45c9b5d6, the version you would install today, has no known vulnerabilities.

Package health score 59/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Inactive

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

  • Current release v0.0.0-20260616140235-3b1f45c9b5d6 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 1 i
  • OpenSSF scorecard 1/10 i
  • Last release 4 months ago 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/goodrain/rainbond-oam, 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-20260616140235-3b1f45c9b5d6 16 Jun 2026 none — — Details →
v0.0.0-20260616124540-440d85174612 16 Jun 2026 none — — Details →
v0.0.0-20260616102325-d00568abe287 16 Jun 2026 none — — Details →
v0.0.0-20260616100721-ed623052242e 16 Jun 2026 none — — Details →
v0.0.0-20260521083744-80b3d3272e1e 21 May 2026 none — — Details →
v0.0.0-20260521080153-b5d11f20dd9a 21 May 2026 none — — Details →
v0.0.0-20260409060429-a00b9f800598 09 Apr 2026 none — — Details →
v0.0.0-20260401060407-6fb558084c9e 01 Apr 2026 none — — Details →
v0.0.0-20260227111231-15eadec18410 27 Feb 2026 none — — Details →
v0.0.0-20260209121625-09bc29b6e336 09 Feb 2026 none — — Details →
v0.0.0-20250305063422-5ff58c5b3f36 05 Mar 2025 none — — Details →
v0.0.0-20241120151145-067f8a6d718a 20 Nov 2024 none — — Details →
v0.0.0-20241120144629-054e5799e57d 20 Nov 2024 none — — Details →
v0.0.0-20241119110708-7a487c13befb 19 Nov 2024 none — — Details →
v0.0.0-20231124034417-c9417f778e7f 24 Nov 2023 none — — Details →
v0.0.0-20231124033014-899776dd207d 24 Nov 2023 none — — Details →
v0.0.0-20231121100954-71965f8b9f9f 21 Nov 2023 none — — Details →
v0.0.0-20231121083231-db3c761e2504 21 Nov 2023 none — — Details →
v0.0.0-20231018121534-c530a1a0918c 18 Oct 2023 none — — Details →
v0.0.0-20230823084937-0067a4cf0912 23 Aug 2023 none — — Details →
v0.0.0-20230324123857-b93cb605a6f5 24 Mar 2023 none — — Details →
v0.0.0-20230117125005-98bcc9233a7f 17 Jan 2023 none — — Details →
v0.0.0-20221115150510-dd668a6d6765 15 Nov 2022 none — — Details →
v0.0.0-20220930022846-0874287dc35d 30 Sep 2022 none — — Details →
v0.0.0-20220929165105-be6653621e55 29 Sep 2022 none — — Details →
v0.0.0-20220908064513-fed01f0e1a1b 08 Sep 2022 none — — Details →
v0.0.0-20210810094229-f1cd639c451a 10 Aug 2021 none — — Details →
v0.0.0-20210721020036-158e1be667dc 21 Jul 2021 none — — Details →
v0.0.0-20210527094216-782b95046e0d 27 May 2021 none — — Details →
v0.0.0-20210206075623-511d0796af43 06 Feb 2021 none — — Details →
v0.0.0-20200918054122-c774fd26ffa1 18 Sep 2020 none — — Details →

All 31 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/goodrain/rainbond-oam

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/goodrain/rainbond-oam

Is github.com/goodrain/rainbond-oam safe to use?

Vulert has no vulnerabilities on record for github.com/goodrain/rainbond-oam 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/goodrain/rainbond-oam's Vulert package health score?

Vulert scores github.com/goodrain/rainbond-oam 59/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/goodrain/rainbond-oam affected?

No. v0.0.0-20260616140235-3b1f45c9b5d6, 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/goodrain/rainbond-oam should I use?

v0.0.0-20260616140235-3b1f45c9b5d6 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/goodrain/rainbond-oam have?

0 vulnerabilities are recorded for github.com/goodrain/rainbond-oam 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/goodrain/rainbond-oam vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/goodrain/rainbond-oam 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/goodrain/rainbond-oam 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/goodrain/rainbond-oam for upcoming vulnerabilities?

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