VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/cockroachdb/swiss: vulnerability history, versions and safety

github.com/cockroachdb/swiss 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/cockroachdb/swiss vulnerabilities

Vulert verdict on github.com/cockroachdb/swiss v0.0.0-20260820225851-333444432258 i

Updated on 23 Oct 2026

Good news: v0.0.0-20260820225851-333444432258, the version you would install today, has no known vulnerabilities.

Package health score 73/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

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

  • Current release v0.0.0-20260820225851-333444432258 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 480 i
  • OpenSSF scorecard 3/10 i
  • Last release 2 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/cockroachdb/swiss, 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-20260820225851-333444432258 20 Aug 2026 none Apache-2.0 — Details →
v0.0.0-20260820225851-aa852fb3c14e 20 Aug 2026 none Apache-2.0 — Details →
v0.0.0-20251224182025-b0f6560f979b 24 Dec 2025 none Apache-2.0 — Details →
v0.0.0-20251224105920-ba5814f36509 24 Dec 2025 none Apache-2.0 — Details →
v0.0.0-20250624142022-d6e517c1d961 24 Jun 2025 none Apache-2.0 — Details →
v0.0.0-20250327203710-0a8dbaa58e2a 27 Mar 2025 none Apache-2.0 — Details →
v0.0.0-20250327203710-2932b022f6df 27 Mar 2025 none Apache-2.0 — Details →
v0.0.0-20250304010804-34a2c6a59016 04 Mar 2025 none Apache-2.0 — Details →
v0.0.0-20250304002905-9226d3eb96d2 04 Mar 2025 none Apache-2.0 — Details →
v0.0.0-20250228210649-a321086955f2 28 Feb 2025 none Apache-2.0 — Details →
v0.0.0-20250228163838-b0ad90cb6c3c 28 Feb 2025 none Apache-2.0 — Details →
v0.0.0-20250228163838-eb342c9e4973 28 Feb 2025 none Apache-2.0 — Details →
v0.0.0-20240612210725-f4de07ae6964 12 Jun 2024 none Apache-2.0 — Details →
v0.0.0-20240612204417-ed4e59966240 12 Jun 2024 none Apache-2.0 — Details →
v0.0.0-20240605133600-232b93a2b829 05 Jun 2024 none Apache-2.0 — Details →
v0.0.0-20240303172742-c161743eb608 03 Mar 2024 none Apache-2.0 — Details →
v0.0.0-20240229210926-21ec5ae7d7ba 29 Feb 2024 none Apache-2.0 — Details →
v0.0.0-20240228144331-f89e8e34b10c 28 Feb 2024 none Apache-2.0 — Details →
v0.0.0-20240228123450-7b50593e7686 28 Feb 2024 none Apache-2.0 — Details →
v0.0.0-20240227221518-905acbbfe9e5 27 Feb 2024 none Apache-2.0 — Details →
v0.0.0-20240227152458-f151aa5538da 27 Feb 2024 none Apache-2.0 — Details →
v0.0.0-20240227123359-9f7e178aa416 27 Feb 2024 none Apache-2.0 — Details →
v0.0.0-20240226223847-16079ed4d941 26 Feb 2024 none Apache-2.0 — Details →
v0.0.0-20240226205156-e52380ff6dc5 26 Feb 2024 none Apache-2.0 — Details →
v0.0.0-20240226200137-f3dbd236d877 26 Feb 2024 none Apache-2.0 — Details →
v0.0.0-20240218003604-fa7bdb1c8c21 18 Feb 2024 none Apache-2.0 — Details →
v0.0.0-20240213145313-1afdbb24b5e4 13 Feb 2024 none Apache-2.0 — Details →
v0.0.0-20240212231644-b30fdae83c23 12 Feb 2024 none Apache-2.0 — Details →
v0.0.0-20240212150853-a5ef6699cce9 12 Feb 2024 none Apache-2.0 — Details →
v0.0.0-20240212144121-c9adc1994621 12 Feb 2024 none Apache-2.0 — Details →
v0.0.0-20240209150528-60a952feee64 09 Feb 2024 none Apache-2.0 — 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/cockroachdb/swiss

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/cockroachdb/swiss

Is github.com/cockroachdb/swiss safe to use?

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

Vulert scores github.com/cockroachdb/swiss 73/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/cockroachdb/swiss affected?

No. v0.0.0-20260820225851-333444432258, 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/cockroachdb/swiss should I use?

v0.0.0-20260820225851-333444432258 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/cockroachdb/swiss have?

0 vulnerabilities are recorded for github.com/cockroachdb/swiss 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/cockroachdb/swiss vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/cockroachdb/swiss 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/cockroachdb/swiss 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/cockroachdb/swiss for upcoming vulnerabilities?

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