VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/rootless-containers/rootlesskit/v2: vulnerability history, versions and safety

github.com/rootless-containers/rootlesskit/v2 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/rootless-containers/rootlesskit/v2 vulnerabilities

Vulert verdict on github.com/rootless-containers/rootlesskit/v2 v2.3.6 i

Updated on 23 Oct 2026

Good news: v2.3.6, the version you would install today, has no known vulnerabilities.

Package health score 78/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

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

  • Current release v2.3.6 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 1,311 i
  • OpenSSF scorecard 4/10 i
  • Last release 10 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/rootless-containers/rootlesskit/v2, 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
v2.3.6 18 Dec 2025 none Apache-2.0 — Details →
v2.3.6-0.20250508055847-e83d7635183e 08 May 2025 none Apache-2.0 — Details →
v2.3.5 08 May 2025 none Apache-2.0 — Details →
v2.3.5-0.20250319135527-530859a92629 19 Mar 2025 none Apache-2.0 — Details →
v2.3.5-0.20250310021448-c6df51d796f1 10 Mar 2025 none Apache-2.0 — Details →
v2.3.4 10 Mar 2025 none Apache-2.0 — Details →
v2.3.4-0.20250310010131-9c7773eadf45 10 Mar 2025 none Apache-2.0 — Details →
v2.3.3 10 Mar 2025 none Apache-2.0 — Details →
v2.3.3-0.20250120021654-4b6f1b8bd4e1 20 Jan 2025 none Apache-2.0 — Details →
v2.3.2 20 Jan 2025 none Apache-2.0 — Details →
v2.3.2-0.20241204171854-9c9049ac7864 04 Dec 2024 none Apache-2.0 — Details →
v2.3.2-0.20240918232406-baa8876d2bed 18 Sep 2024 none Apache-2.0 — Details →
v2.3.2-0.20240823072125-264f23eb1063 23 Aug 2024 none Apache-2.0 — Details →
v2.3.2-0.20240817192704-b160eea1a013 17 Aug 2024 none Apache-2.0 — Details →
v2.3.1 17 Aug 2024 none Apache-2.0 — Details →
v2.3.0 17 Aug 2024 none Apache-2.0 — Details →
v2.2.1-0.20240717025626-75f183f58b4b 17 Jul 2024 none Apache-2.0 — Details →
v2.2.0 16 Jul 2024 none Apache-2.0 — Details →
v2.1.1-0.20240708074834-4fb2e2cb80bf 08 Jul 2024 none Apache-2.0 — Details →
v2.1.1-0.20240604172558-71f54dfbe44b 04 Jun 2024 none Apache-2.0 — Details →
v2.1.1-0.20240527020052-d942cd588009 27 May 2024 none Apache-2.0 — Details →
v2.1.1-0.20240514081724-e484dd6aec1d 14 May 2024 none Apache-2.0 — Details →
v2.1.1-0.20240426013235-443ac4a10396 26 Apr 2024 none Apache-2.0 — Details →
v2.1.0 26 Apr 2024 none Apache-2.0 — Details →
v2.0.3-0.20240305221821-97ea64c19ae9 05 Mar 2024 none Apache-2.0 — Details →
v2.0.2 05 Mar 2024 none Apache-2.0 — Details →
v2.0.2-0.20240207171025-efee459a225b 07 Feb 2024 none Apache-2.0 — Details →
v2.0.2-0.20240206024348-de6f288df0b8 06 Feb 2024 none Apache-2.0 — Details →
v2.0.1 06 Feb 2024 none Apache-2.0 — Details →
v2.0.1-0.20240124232726-c2f647c842c7 24 Jan 2024 none Apache-2.0 — Details →
v2.0.1-0.20240115010900-cb0091290621 15 Jan 2024 none Apache-2.0 — Details →
v2.0.0 15 Jan 2024 none Apache-2.0 — Details →
v2.0.0-beta.0.0.20240111051114-00814e28f579 11 Jan 2024 none Apache-2.0 — Details →
v2.0.0-beta.0 10 Jan 2024 none Apache-2.0 — Details →
v2.0.0-alpha.2.0.20231204180304-bc231c47bfd0 04 Dec 2023 none Apache-2.0 — Details →
v2.0.0-alpha.2.0.20231204133323-fbca95e28631 04 Dec 2023 none Apache-2.0 — Details →
v2.0.0-alpha.2 04 Dec 2023 none Apache-2.0 — Details →
v2.0.0-alpha.1.0.20231011223915-a0a48d566f34 11 Oct 2023 none Apache-2.0 — Details →
v2.0.0-alpha.1.0.20231008231111-b77a58a42934 08 Oct 2023 none Apache-2.0 — Details →
v2.0.0-alpha.1 08 Oct 2023 none Apache-2.0 — Details →
v2.0.0-alpha.0.0.20230629144855-5410f69cf58d 29 Jun 2023 none Apache-2.0 — Details →
v2.0.0-alpha.0 29 Jun 2023 none Apache-2.0 — Details →

All 42 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/rootless-containers/rootlesskit/v2

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/rootless-containers/rootlesskit/v2

Is github.com/rootless-containers/rootlesskit/v2 safe to use?

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

Vulert scores github.com/rootless-containers/rootlesskit/v2 78/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/rootless-containers/rootlesskit/v2 affected?

No. v2.3.6, 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/rootless-containers/rootlesskit/v2 should I use?

v2.3.6 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/rootless-containers/rootlesskit/v2 have?

0 vulnerabilities are recorded for github.com/rootless-containers/rootlesskit/v2 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/rootless-containers/rootlesskit/v2 vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/rootless-containers/rootlesskit/v2 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/rootless-containers/rootlesskit/v2 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/rootless-containers/rootlesskit/v2 for upcoming vulnerabilities?

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