VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

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

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

Vulert verdict on github.com/motemen/go-nuts v0.0.0-20251105153347-936c09797748 i

Updated on 23 Oct 2026

Good news: v0.0.0-20251105153347-936c09797748, the version you would install today, has no known vulnerabilities.

Package health score 61/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Inactive

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

  • Current release v0.0.0-20251105153347-936c09797748 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 18 i
  • OpenSSF scorecard 2/10 i
  • Last release 11 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/motemen/go-nuts, 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-20251105153347-936c09797748 05 Nov 2025 none MIT — Details →
v0.0.0-20230307001945-455ea3acd1ea 07 Mar 2023 none MIT — Details →
v0.0.0-20220604134737-2658d0104f31 04 Jun 2022 none MIT — Details →
v0.0.0-20220604133202-348ca5c35272 04 Jun 2022 none MIT — Details →
v0.0.0-20210915132349-615a782f2c69 15 Sep 2021 none MIT — Details →
v0.0.0-20210718141713-347ff8a12a40 18 Jul 2021 none MIT — Details →
v0.0.0-20210718124417-77c0a171bc58 18 Jul 2021 none MIT — Details →
v0.0.0-20210715150014-545aa451d82c 15 Jul 2021 none MIT — Details →
v0.0.0-20210715140759-c4c3752c8471 15 Jul 2021 none MIT — Details →
v0.0.0-20210715140518-967e9b3d802f 15 Jul 2021 none MIT — Details →
v0.0.0-20210715124540-12439c3b276e 15 Jul 2021 none MIT — Details →
v0.0.0-20210713001525-066052246994 13 Jul 2021 none MIT — Details →
v0.0.0-20210609140242-c2fed52ea4d1 09 Jun 2021 none MIT — Details →
v0.0.0-20210602141927-d5e38ddf0bc6 02 Jun 2021 none MIT — Details →
v0.0.0-20210601053339-7d8b4b754d9e 01 Jun 2021 none MIT — Details →
v0.0.0-20210601045738-0927e07d1ecb 01 Jun 2021 none MIT — Details →
v0.0.0-20210531135531-9e886ac56150 31 May 2021 none MIT — Details →
v0.0.0-20210531132517-26736fc735ef 31 May 2021 none MIT — Details →
v0.0.0-20210531132151-35063c1e7fb1 31 May 2021 none MIT — Details →
v0.0.0-20210531131957-df8cdd210b74 31 May 2021 none MIT — Details →
v0.0.0-20210531130838-054b78cd7ef0 31 May 2021 none MIT — Details →
v0.0.0-20210520132109-e1e973eb64cc 20 May 2021 none MIT — Details →
v0.0.0-20210519135428-0d423d0aeb70 19 May 2021 none MIT — Details →
v0.0.0-20210519132452-663d2eef5171 19 May 2021 none MIT — Details →
v0.0.0-20210517135100-03913da5054f 17 May 2021 none MIT — Details →
v0.0.0-20210516043807-f51fa80cba41 16 May 2021 none MIT — Details →
v0.0.0-20200601065735-3df31f16cb2f 01 Jun 2020 none MIT — Details →
v0.0.0-20200528124917-216e3a4a7a00 28 May 2020 none MIT — Details →
v0.0.0-20200521134403-de26cfb00bc6 21 May 2020 none MIT — Details →
v0.0.0-20190725124253-1d2432db96b0 25 Jul 2019 none MIT — Details →
v0.0.0-20190721155003-2ee9077389ff 21 Jul 2019 none MIT — Details →
v0.0.0-20180315145558-42c35bdb11c2 15 Mar 2018 none MIT — Details →
v0.0.0-20170829002634-49f2fd6dca14 29 Aug 2017 none MIT — Details →
v0.0.0-20170531040205-d9d22c657fba 31 May 2017 none — — Details →
v0.0.0-20161031050620-d23566d798a0 31 Oct 2016 none — — Details →

All 35 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/motemen/go-nuts

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/motemen/go-nuts

Is github.com/motemen/go-nuts safe to use?

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

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

No. v0.0.0-20251105153347-936c09797748, 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/motemen/go-nuts should I use?

v0.0.0-20251105153347-936c09797748 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/motemen/go-nuts have?

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

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

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