VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/osquery/osquery-go: vulnerability history, versions and safety

github.com/osquery/osquery-go 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/osquery/osquery-go vulnerabilities

Vulert verdict on github.com/osquery/osquery-go v0.0.0-20260630173615-eb39ad3443df i

Updated on 23 Oct 2026

Good news: v0.0.0-20260630173615-eb39ad3443df, 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-20260630173615-eb39ad3443df or newer. This can change: a vulnerability disclosed tomorrow can affect v0.0.0-20260630173615-eb39ad3443df too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release v0.0.0-20260630173615-eb39ad3443df — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 433 i
  • OpenSSF scorecard 3/10 i
  • Last release 3 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/osquery/osquery-go, 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-20260630173615-eb39ad3443df 30 Jun 2026 none MIT — Details →
v0.0.0-20260508130258-3e773449a5d4 08 May 2026 none MIT — Details →
v0.0.0-20260306231408-a88c0766cd0d 06 Mar 2026 none MIT — Details →
v0.0.0-20260226222546-0cc22f415e57 26 Feb 2026 none MIT — Details →
v0.0.0-20260210222056-f77b3a1e15cc 10 Feb 2026 none MIT — Details →
v0.0.0-20260206053959-068ec3a0f8cc 06 Feb 2026 none MIT — Details →
v0.0.0-20260206035819-e4cf7216f1a5 06 Feb 2026 none MIT — Details →
v0.0.0-20250131154556-629f995b6947 31 Jan 2025 none MIT — Details →
v0.0.0-20250129172556-8293fdf5f1ce 29 Jan 2025 none MIT — Details →
v0.0.0-20240910233439-561a72587be6 10 Sep 2024 none MIT — Details →
v0.0.0-20231130195733-61ac79279aaa 30 Nov 2023 none MIT — Details →
v0.0.0-20231108163517-e3cde127e724 08 Nov 2023 none MIT — Details →
v0.0.0-20231108151129-b411f54b8ca2 08 Nov 2023 none MIT — Details →
v0.0.0-20231006172600-d6f325f636a9 06 Oct 2023 none MIT — Details →
v0.0.0-20230707154813-2e4891a0f444 07 Jul 2023 none MIT — Details →
v0.0.0-20230707131658-ad2c25c77a31 07 Jul 2023 none MIT — Details →
v0.0.0-20230707051101-95ef9f34abe9 07 Jul 2023 none MIT — Details →
v0.0.0-20230705162601-dbeefc07d76e 05 Jul 2023 none MIT — Details →
v0.0.0-20230627155640-6bcabfbc94ec 27 Jun 2023 none MIT — Details →
v0.0.0-20230603132358-d2e851b3991b 03 Jun 2023 none MIT — Details →
v0.0.0-20230601143634-21907626d81c 01 Jun 2023 none MIT — Details →
v0.0.0-20230526214746-bb78b44cee71 26 May 2023 none MIT — Details →
v0.0.0-20230525191526-5b6e9f8e0b37 25 May 2023 none MIT — Details →
v0.0.0-20230502201847-c0d96ae4db30 02 May 2023 none MIT — Details →
v0.0.0-20230501171314-2fc54ff75669 01 May 2023 none MIT — Details →
v0.0.0-20230427204930-ff54f5f08296 27 Apr 2023 none MIT — Details →
v0.0.0-20220706183148-4e1f83012b42 06 Jul 2022 none MIT — Details →
v0.0.0-20220407231332-b44b326f5f4d 07 Apr 2022 none MIT — Details →
v0.0.0-20220317165851-954ac78f381f 17 Mar 2022 none MIT — Details →
v0.0.0-20210622151333-99b4efa62ec5 22 Jun 2021 none MIT — Details →
v0.0.0-20210607121309-df1df42c8206 07 Jun 2021 none MIT — Details →
v0.0.0-20180816163454-30c843ecb33a 16 Aug 2018 none MIT — Details →
v0.0.0-20180620170728-d4f3a629e76c 20 Jun 2018 none MIT — Details →
v0.0.0-20180413104856-e17dfe8f44e7 13 Apr 2018 none MIT — Details →
v0.0.0-20171018215502-03a792fcca9a 18 Oct 2017 none MIT — Details →
v0.0.0-20170828204101-8c8fd2cb76a1 28 Aug 2017 none MIT — Details →
v0.0.0-20170801151711-7ceba810d60e 01 Aug 2017 none MIT — Details →

All 37 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/osquery/osquery-go

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/osquery/osquery-go

Is github.com/osquery/osquery-go safe to use?

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

Vulert scores github.com/osquery/osquery-go 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/osquery/osquery-go affected?

No. v0.0.0-20260630173615-eb39ad3443df, 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/osquery/osquery-go should I use?

v0.0.0-20260630173615-eb39ad3443df 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/osquery/osquery-go have?

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

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

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