Vulnerability Database · Go · Package report

github.com/sanity-io/litter: vulnerability history, versions and safety

github.com/sanity-io/litter 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/sanity-io/litter v1.5.8 i

Updated on 23 Oct 2026

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

Package health score 70/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Widely used
  • Community Quiet

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

  • Current release v1.5.8 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 1,653 i
  • OpenSSF scorecard 3/10 i
  • Last release 20 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/sanity-io/litter, 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-20260504104730-2ddefc21bc33 04 May 2026 none MIT — Details →
v1.5.9-0.20260504104730-2ddefc21bc33 04 May 2026 none MIT — Details →
v0.0.0-20250704095629-a7065ec929fb 04 Jul 2025 none MIT — Details →
v1.5.9-0.20250704095629-a7065ec929fb 04 Jul 2025 none MIT — Details →
v1.5.9-0.20250704095629-f99a985203c9 04 Jul 2025 none MIT — Details →
v1.5.8 15 Feb 2025 none MIT — Details →
v1.5.7 12 Feb 2025 none MIT — Details →
v1.5.7-0.20250212100939-61ca8aa20ab3 12 Feb 2025 none MIT — Details →
v1.5.6 23 Nov 2024 none MIT — Details →
v1.5.6-0.20241123161940-7e132579048a 23 Nov 2024 none MIT — Details →
v1.5.6-0.20240909113056-4486f74f4cea 09 Sep 2024 none MIT — Details →
v0.0.0-20220428091810-f2ba02b77978 28 Apr 2022 none MIT — Details →
v1.5.5 28 Apr 2022 none MIT — Details →
v1.5.5-0.20220428091810-f2ba02b77978 28 Apr 2022 none MIT — Details →
v1.5.4 14 Mar 2022 none MIT — Details →
v1.5.3-0.20220314102524-cfce9160a045 14 Mar 2022 none MIT — Details →
v1.5.4-0.20220314102524-cfce9160a045 14 Mar 2022 none MIT — Details →
v1.5.2-0.20220106174435-65e672ecd4d7 06 Jan 2022 none MIT — Details →
v1.5.3 06 Jan 2022 none MIT — Details →
v1.5.3-0.20220106174435-65e672ecd4d7 06 Jan 2022 none MIT — Details →
v1.5.2 21 May 2021 none MIT — Details →
v1.5.2-0.20210521155524-5286198afa2b 21 May 2021 none MIT — Details →
v1.5.2-0.20210520105730-0e8422676e75 20 May 2021 none MIT — Details →
v1.5.2-0.20210520105730-51df90805fc0 20 May 2021 none MIT — Details →
v1.5.2-0.20210520105730-eee44b093193 20 May 2021 none MIT — Details →
v1.5.1 13 May 2021 none MIT — Details →
v1.5.0 04 Feb 2021 none MIT — Details →
v1.4.0 03 Feb 2021 none MIT — Details →
v1.3.1-0.20210203031756-27e9ea81901c 03 Feb 2021 none MIT — Details →
v1.3.1-0.20210130213500-5a0455f9d427 30 Jan 2021 none MIT — Details →
v1.3.1-0.20201023140029-6da87dada9b5 23 Oct 2020 none MIT — Details →
v1.3.1-0.20200805135822-9a4d13ca8fb9 05 Aug 2020 none MIT — Details →
v1.3.0 05 Aug 2020 none MIT — Details →
v1.2.1-0.20200805131907-1504df9c4067 05 Aug 2020 none MIT — Details →
v1.2.1-0.20200123172006-4e33bf367cf0 23 Jan 2020 none MIT — Details →
v1.2.1-0.20200123172006-b3546bd0a12c 23 Jan 2020 none MIT — Details →
v1.1.1-0.20190814225852-6d3310f9743f 14 Aug 2019 none MIT — Details →
v1.2.0 14 Aug 2019 none MIT — Details →
v1.1.1-0.20190814225827-6ae0620d71c2 14 Aug 2019 none MIT — Details →
v0.0.0-20190603170123-89eabd1bc229 03 Jun 2019 none MIT — Details →
v1.1.1-0.20190603170123-89eabd1bc229 03 Jun 2019 none MIT — Details →
v1.1.1-0.20190331173446-01639073401d 31 Mar 2019 none MIT — Details →
v0.0.0-20181128153236-d0cf0b7ed080 28 Nov 2018 none MIT — Details →
v1.1.1-0.20181128153236-d0cf0b7ed080 28 Nov 2018 none MIT — Details →
v0.0.0-20181009143221-cdb60d0035dc 09 Oct 2018 none MIT — Details →
v1.1.1-0.20181009143221-cdb60d0035dc 09 Oct 2018 none MIT — Details →
v1.1.1-0.20181009140454-cdaffa659bdb 09 Oct 2018 none MIT — Details →
v1.1.1-0.20181004194725-ceb5b572cea0 04 Oct 2018 none MIT — Details →
v0.0.0-20180714121731-09e3a73d5b65 14 Jul 2018 none MIT — Details →
v1.1.1-0.20180714121731-09e3a73d5b65 14 Jul 2018 none MIT — Details →
v0.0.0-20171129085111-f8fd6a57e929 29 Nov 2017 none MIT — Details →
v1.1.1-0.20171129085111-f8fd6a57e929 29 Nov 2017 none MIT — Details →
v1.1.1-0.20171129084628-882b76465edc 29 Nov 2017 none MIT — Details →
v1.1.1-0.20171128185017-2802b722dba1 28 Nov 2017 none MIT — Details →
v1.1.1-0.20171124081957-f375e3b24f75 24 Nov 2017 none MIT — Details →
v1.1.1-0.20171113190057-f055f4e7128a 13 Nov 2017 none MIT — Details →
v1.1.1-0.20171101185143-25178444957e 01 Nov 2017 none MIT — Details →
v1.1.0 01 Nov 2017 none MIT — Details →
v1.0.1-0.20171101183848-1cf0b7eeb0f7 01 Nov 2017 none MIT — Details →
v1.0.0 29 Oct 2017 none MIT — Details →
v0.0.0-20171027092855-09e1cc3164be 27 Oct 2017 none MIT — Details →
v0.0.0-20171015203530-ca0745f0c394 15 Oct 2017 none MIT — Details →
v0.0.0-20171015200115-c9d1f2b1d66f 15 Oct 2017 none MIT — Details →
v0.0.0-20171013103916-73d2c4f5560a 13 Oct 2017 none MIT — Details →
v0.0.0-20171012192131-70515198d56b 12 Oct 2017 none MIT — Details →
v0.0.0-20171011154944-3ea49217dff0 11 Oct 2017 none MIT — Details →
v0.0.0-20171011020533-06db0b3f9389 11 Oct 2017 none — — Details →
v0.0.0-20170330150907-088f787b2d74 30 Mar 2017 none — — Details →
v0.0.0-20170321144126-26d52ab9742c 21 Mar 2017 none — — Details →
v0.0.0-20170320160539-2683c08dbd02 20 Mar 2017 none — — Details →

All 70 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/sanity-io/litter

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/sanity-io/litter

Is github.com/sanity-io/litter safe to use?

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

Vulert scores github.com/sanity-io/litter 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/sanity-io/litter affected?

No. v1.5.8, 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/sanity-io/litter should I use?

v1.5.8 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/sanity-io/litter have?

0 vulnerabilities are recorded for github.com/sanity-io/litter 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/sanity-io/litter vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/sanity-io/litter 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/sanity-io/litter 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/sanity-io/litter for upcoming vulnerabilities?

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