Vulnerability Database · Go · Package report

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

github.com/armosec/utils-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.

Vulert verdict on github.com/armosec/utils-go v0.0.58 i

Updated on 23 Oct 2026

Good news: v0.0.58, the version you would install today, has no known vulnerabilities.

Package health score 58/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Little adoption
  • Community Inactive

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

  • Current release v0.0.58 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • OpenSSF scorecard 3/10 i
  • Last release 23 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/armosec/utils-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.58 04 Nov 2024 none Apache-2.0 — Details →
v0.0.58-0.20241104145829-8d0a46e0a90e 04 Nov 2024 none Apache-2.0 — Details →
v0.0.58-0.20241101071240-9e4af7404c7a 01 Nov 2024 none Apache-2.0 — Details →
v0.0.58-0.20241010161239-67327efc22ac 10 Oct 2024 none Apache-2.0 — Details →
v0.0.58-0.20241010155611-c5a67310fa32 10 Oct 2024 none Apache-2.0 — Details →
v0.0.58-0.20241010155208-be39dc566eb2 10 Oct 2024 none Apache-2.0 — Details →
v0.0.58-0.20241010150310-e627947c8452 10 Oct 2024 none Apache-2.0 — Details →
v0.0.58-0.20241010144131-a7d9f9b07902 10 Oct 2024 none Apache-2.0 — Details →
v0.0.58-0.20241010075313-dfd979210a87 10 Oct 2024 none Apache-2.0 — Details →
v0.0.58-0.20241010073435-a542d56dfb3d 10 Oct 2024 none Apache-2.0 — Details →
v0.0.58-0.20241009091159-a6b056c6880a 09 Oct 2024 none Apache-2.0 — Details →
v0.0.57 26 Feb 2024 none Apache-2.0 — Details →
v0.0.57-0.20240226080224-90f586b0b38e 26 Feb 2024 none Apache-2.0 — Details →
v0.0.56 22 Nov 2023 none Apache-2.0 — Details →
v0.0.56-0.20231122071653-25556bc4d27b 22 Nov 2023 none Apache-2.0 — Details →
v0.0.55 22 Nov 2023 none Apache-2.0 — Details →
v0.0.54 21 Nov 2023 none Apache-2.0 — Details →
v0.0.53 21 Nov 2023 none Apache-2.0 — Details →
v0.0.52 21 Nov 2023 none Apache-2.0 — Details →
v0.0.51 20 Nov 2023 none Apache-2.0 — Details →
v0.0.51-0.20231120120013-341d74c6ec9f 20 Nov 2023 none Apache-2.0 — Details →
v0.0.50 20 Nov 2023 none Apache-2.0 — Details →
v0.0.45 16 Nov 2023 none Apache-2.0 — Details →
v0.0.45-0.20231116125411-cca6cf73d83a 16 Nov 2023 none Apache-2.0 — Details →
v0.0.44 16 Nov 2023 none Apache-2.0 — Details →
v0.0.43 14 Nov 2023 none Apache-2.0 — Details →
v0.0.43-0.20231114134827-3ebf6907aead 14 Nov 2023 none Apache-2.0 — Details →
v0.0.42 13 Nov 2023 none Apache-2.0 — Details →
v0.0.41 12 Nov 2023 none Apache-2.0 — Details →
v0.0.41-0.20231112072558-54326137d01b 12 Nov 2023 none Apache-2.0 — Details →
v0.0.41-0.20231112060425-30d0bf3cb979 12 Nov 2023 none Apache-2.0 — Details →
v0.0.40 18 Sep 2023 none Apache-2.0 — Details →
v0.0.40-0.20230918072643-809674a98a3f 18 Sep 2023 none Apache-2.0 — Details →
v0.0.37-0.20230914114222-7d6495ddeeee 14 Sep 2023 none Apache-2.0 — Details →
v0.0.39 14 Sep 2023 none Apache-2.0 — Details →
v0.0.37-0.20230914110756-1f110e5373d6 14 Sep 2023 none Apache-2.0 — Details →
v0.0.36 14 Sep 2023 none Apache-2.0 — Details →
v0.0.35 07 Sep 2023 none Apache-2.0 — Details →
v0.0.35-0.20230907155056-b43f0667caab 07 Sep 2023 none Apache-2.0 — Details →
v0.0.34 05 Sep 2023 none Apache-2.0 — Details →
v0.0.34-0.20230905110848-7a73855f344a 05 Sep 2023 none Apache-2.0 — Details →
v0.0.33 28 Aug 2023 none Apache-2.0 — Details →
v0.0.33-0.20230828133120-242f8d4642e7 28 Aug 2023 none Apache-2.0 — Details →
v0.0.29-0.20230824060308-0507bd869807 24 Aug 2023 none Apache-2.0 — Details →
v0.0.32 24 Aug 2023 none Apache-2.0 — Details →
v0.0.28 23 Aug 2023 none Apache-2.0 — Details →
v0.0.28-0.20230823044406-a8a935d921e6 23 Aug 2023 none Apache-2.0 — Details →
v0.0.28-0.20230823044330-64cdd22ff06e 23 Aug 2023 none Apache-2.0 — Details →
v0.0.27 08 Aug 2023 none Apache-2.0 — Details →
v0.0.27-0.20230808103210-63ad85d786b2 08 Aug 2023 none Apache-2.0 — Details →
v0.0.26 03 Aug 2023 none Apache-2.0 — Details →
v0.0.26-0.20230803121904-7acba9c302d2 03 Aug 2023 none Apache-2.0 — Details →
v0.0.25 02 Aug 2023 none Apache-2.0 — Details →
v0.0.25-0.20230802112502-c94cae590131 02 Aug 2023 none Apache-2.0 — Details →
v0.0.24 02 Aug 2023 none Apache-2.0 — Details →
v0.0.24-0.20230802064153-23ac2b3efd48 02 Aug 2023 none Apache-2.0 — Details →
v0.0.23 01 Aug 2023 none Apache-2.0 — Details →
v0.0.23-0.20230801111956-495ba7c65aea 01 Aug 2023 none Apache-2.0 — Details →
v0.0.22 01 Aug 2023 none Apache-2.0 — Details →
v0.0.21-0.20230801083312-5a4deed27159 01 Aug 2023 none Apache-2.0 — Details →
v0.0.21-0.20230801081418-118258b13996 01 Aug 2023 none Apache-2.0 — Details →
v0.0.21-0.20230801075805-458462faaf14 01 Aug 2023 none Apache-2.0 — Details →
v0.0.20 30 Jul 2023 none Apache-2.0 — Details →
v0.0.20-0.20230730110019-0e3ea7e36301 30 Jul 2023 none Apache-2.0 — Details →
v0.0.19 26 Jul 2023 none Apache-2.0 — Details →
v0.0.19-0.20230726070419-14a165d42037 26 Jul 2023 none Apache-2.0 — Details →
v0.0.18 25 Jul 2023 none Apache-2.0 — Details →
v0.0.17 20 Jul 2023 none Apache-2.0 — Details →
v0.0.16 03 May 2023 none Apache-2.0 — Details →
v0.0.16-0.20230503100324-10f12a679774 03 May 2023 none Apache-2.0 — Details →
v0.0.15 27 Apr 2023 none Apache-2.0 — Details →
v0.0.15-0.20230426093224-9bb0bc76d172 26 Apr 2023 none Apache-2.0 — Details →
v0.0.14 01 Feb 2023 none Apache-2.0 — Details →
v0.0.13 27 Jan 2023 none Apache-2.0 — Details →
v0.0.12 09 Aug 2022 none Apache-2.0 — Details →
v0.0.11 09 Aug 2022 none Apache-2.0 — Details →
v0.0.10 08 Aug 2022 none Apache-2.0 — Details →
v0.0.9 04 Aug 2022 none Apache-2.0 — Details →
v0.0.8 21 Jul 2022 none Apache-2.0 — Details →
v0.0.7 26 Jun 2022 none — — Details →
v0.0.6 23 Jun 2022 none — — Details →
v0.0.5 17 Apr 2022 none — — Details →
v0.0.4 17 Apr 2022 none — — Details →
v0.0.3 12 Oct 2021 none — — Details →
v0.0.2 12 Oct 2021 none — — Details →
v0.0.0-20211010082120-73c512585ce3 10 Oct 2021 none — — Details →

All 86 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/armosec/utils-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/armosec/utils-go

Is github.com/armosec/utils-go safe to use?

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

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

No. v0.0.58, 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/armosec/utils-go should I use?

v0.0.58 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/armosec/utils-go have?

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

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

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/armosec/utils-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.