Vulnerability Database · Go · Package report

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

github.com/go-sprout/sprout 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/go-sprout/sprout v1.1.2 i

Updated on 23 Oct 2026

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

  • Current release v1.1.2 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 233 i
  • OpenSSF scorecard 4/10 i
  • Last release 1 month 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/go-sprout/sprout, 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
v1.1.3-0.20261003000656-86f3bdf7dab7 03 Oct 2026 none MIT — Details →
v0.0.0-20260916153241-65c1a3c4cb08 16 Sep 2026 none MIT — Details →
v1.1.2 16 Sep 2026 none MIT — Details →
v0.0.0-20260821123935-6b871dcaccf3 21 Aug 2026 none MIT — Details →
v1.1.1 21 Aug 2026 none MIT — Details →
v0.0.0-20260819085338-22a2f2967737 19 Aug 2026 none MIT — Details →
v1.1.1-0.20260819085338-22a2f2967737 19 Aug 2026 none MIT — Details →
v0.0.0-20260818075303-7d5028d609ce 18 Aug 2026 none MIT — Details →
v1.1.1-0.20260818075303-7d5028d609ce 18 Aug 2026 none MIT — Details →
v1.1.0 16 Aug 2026 none MIT — Details →
v1.0.4-0.20260815180955-0b5774c48e74 15 Aug 2026 none MIT — Details →
v1.0.4-0.20260815104027-f0c578c27f7e 15 Aug 2026 none MIT — Details →
v0.0.0-20260326182052-4315ea292a28 26 Mar 2026 none MIT — Details →
v1.0.4-0.20260326182052-4315ea292a28 26 Mar 2026 none MIT — Details →
v1.0.4-0.20260218003310-3b77ce5490dd 18 Feb 2026 none MIT — Details →
v1.0.3 26 Dec 2025 none MIT — Details →
v1.0.2 28 Aug 2025 none MIT — Details →
v1.0.1 11 Jun 2025 none MIT — Details →
v1.0.0 16 Jan 2025 none MIT — Details →
v1.0.0-rc.3 18 Dec 2024 none MIT — Details →
v1.0.0-rc.2.0.20241212234201-1fb3882b28e0 12 Dec 2024 none MIT — Details →
v1.0.0-rc.2.0.20241208164011-fe39cc7fabfb 08 Dec 2024 none MIT — Details →
v1.0.0-rc.2.0.20241206101953-f62ee092955d 06 Dec 2024 none MIT — Details →
v1.0.0-rc.2.0.20241205232910-95c16673e7a4 05 Dec 2024 none MIT — Details →
v1.0.0-rc.2.0.20241201151221-aba61cb36108 01 Dec 2024 none MIT — Details →
v1.0.0-rc.2.0.20241130040317-f0d1fd94e856 30 Nov 2024 none MIT — Details →
v1.0.0-rc.2.0.20241127213425-138eddd58c8a 27 Nov 2024 none MIT — Details →
v1.0.0-rc.2.0.20241105234232-1f75760319f5 05 Nov 2024 none MIT — Details →
v1.0.0-rc.1.0.20241105100038-3d7dee5f7bab 05 Nov 2024 none MIT — Details →
v1.0.0-rc.2 05 Nov 2024 none MIT — Details →
v1.0.0-rc.1.0.20241105091307-1c34c3a29743 05 Nov 2024 none MIT — Details →
v0.6.1-0.20241008093628-5047910cab19 08 Oct 2024 none MIT — Details →
v1.0.0-rc.1 08 Oct 2024 none MIT — Details →
v0.6.1-0.20240917000654-c2734d8c203b 17 Sep 2024 none MIT — Details →
v0.6.0 16 Sep 2024 none MIT — Details →
v0.5.2-0.20240908005441-b254ec18bf73 08 Sep 2024 none MIT — Details →
v0.6.0-rc1 08 Sep 2024 none MIT — Details →
v0.5.2-0.20240823133819-e72ad31a2107 23 Aug 2024 none MIT — Details →
v0.5.2-0.20240819151713-13fe589dfb21 19 Aug 2024 none MIT — Details →
v0.5.2-0.20240818152912-3b929022e32b 18 Aug 2024 none MIT — Details →
v0.5.1 18 Aug 2024 none MIT — Details →
v0.5.0 15 Aug 2024 none MIT — Details →
v0.4.2-0.20240617180313-aca5c32cd0f8 17 Jun 2024 none MIT — Details →
v0.4.1 17 Jun 2024 none MIT — Details →
v0.3.1-0.20240516012120-c8121ebebfd0 16 May 2024 none MIT — Details →
v0.4.0 16 May 2024 none MIT — Details →
v0.3.1-0.20240510210334-9d4a544518d7 10 May 2024 none MIT — Details →
v0.2.1-0.20240509193031-edab50f75f6c 09 May 2024 none MIT — Details →
v0.3.0 09 May 2024 none MIT — Details →
v0.2.1-0.20240509183747-34d6c06c7316 09 May 2024 none MIT — Details →

All 50 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/go-sprout/sprout

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

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

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

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

No. v1.1.2, 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/go-sprout/sprout should I use?

v1.1.2 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/go-sprout/sprout have?

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

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

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