VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/aquasecurity/table: vulnerability history, versions and safety

github.com/aquasecurity/table 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/aquasecurity/table vulnerabilities

Vulert verdict on github.com/aquasecurity/table v1.11.0 i

Updated on 23 Oct 2026

Good news: v1.11.0, the version you would install today, has no known vulnerabilities.

Package health score 70/100
  • Security No known security issues
  • Maintenance Maintaining
  • Popularity Niche
  • Community Inactive

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

  • Current release v1.11.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 133 i
  • Last release 15 months ago i
  • Licence MIT 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/aquasecurity/table, 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-20250713114227-303272d80b80 13 Jul 2025 none MIT — Details →
v1.11.0 13 Jul 2025 none MIT — Details →
v1.10.0 02 May 2025 none MIT — Details →
v1.9.0 28 Apr 2025 none MIT — Details →
v1.7.3-0.20220815143132-5c61310b1898 15 Aug 2022 none MIT — Details →
v1.7.3-0.20220815141603-41d2cf9bf8f4 15 Aug 2022 none MIT — Details →
v1.7.3-0.20220815140151-fce553e80017 15 Aug 2022 none MIT — Details →
v1.8.0 15 Aug 2022 none MIT — Details →
v1.7.2 20 Jul 2022 none MIT — Details →
v1.7.1 19 Jul 2022 none MIT — Details →
v1.7.0 05 Jul 2022 none MIT — Details →
v1.6.0 28 Jun 2022 none MIT — Details →
v1.5.1 13 May 2022 none MIT — Details →
v1.5.0 13 May 2022 none MIT — Details →
v1.4.1 13 May 2022 none MIT — Details →
v1.4.0 13 May 2022 none MIT — Details →
v1.3.0 13 May 2022 none — — Details →
v1.2.0 13 May 2022 none — — Details →
v1.1.0 12 May 2022 none — — Details →
v1.0.0 12 May 2022 none — — Details →

All 20 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/aquasecurity/table

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/aquasecurity/table

Is github.com/aquasecurity/table safe to use?

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

Vulert scores github.com/aquasecurity/table 70/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/aquasecurity/table affected?

No. v1.11.0, 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/aquasecurity/table should I use?

v1.11.0 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/aquasecurity/table have?

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

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

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