VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/lmittmann/tint: vulnerability history, versions and safety

github.com/lmittmann/tint 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/lmittmann/tint vulnerabilities

Vulert verdict on github.com/lmittmann/tint v1.2.1 i

Updated on 23 Oct 2026

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

Package health score 77/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

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

  • Current release v1.2.1 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 1,364 i
  • OpenSSF scorecard 2/10 i
  • Last release this month 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/lmittmann/tint, 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.2.1 02 Oct 2026 none MIT — Details →
v1.2.0 12 Jul 2026 none MIT — Details →
v1.1.4-0.20260209221614-dcba16d07a7d 09 Feb 2026 none MIT — Details →
v1.1.4-0.20260203123140-ccd13bcc86ba 03 Feb 2026 none MIT — Details →
v1.1.3 02 Feb 2026 none MIT — Details →
v1.1.2 07 Jun 2025 none MIT — Details →
v1.1.2-0.20250607094151-401cb97c7812 07 Jun 2025 none MIT — Details →
v1.1.1 27 May 2025 none MIT — Details →
v1.1.1-0.20250527205515-30257b8aa108 27 May 2025 none MIT — Details →
v1.1.1-0.20250526204149-ebaca5f41819 26 May 2025 none MIT — Details →
v1.1.0 19 May 2025 none MIT — Details →
v1.0.8-0.20250317101113-926f731a644a 17 Mar 2025 none MIT — Details →
v1.0.7 28 Jan 2025 none MIT — Details →
v1.0.6 16 Dec 2024 none MIT — Details →
v1.0.6-0.20241210092753-de437d07ca45 10 Dec 2024 none MIT — Details →
v1.0.6-0.20240910141457-7c923ea37095 10 Sep 2024 none MIT — Details →
v1.0.5 10 Jul 2024 none MIT — Details →
v1.0.5-0.20240710160440-368de753ea2a 10 Jul 2024 none MIT — Details →
v1.0.5-0.20240616095052-069f95f67402 16 Jun 2024 none MIT — Details →
v1.0.5-0.20240118221531-c4b42929a2f8 18 Jan 2024 none MIT — Details →
v1.0.4 18 Jan 2024 none MIT — Details →
v1.0.3 29 Oct 2023 none MIT — Details →
v1.0.2 14 Sep 2023 none MIT — Details →
v1.0.2-0.20230913212014-f895639af836 13 Sep 2023 none MIT — Details →
v1.0.1 21 Aug 2023 none MIT — Details →
v1.0.1-0.20230821131734-8c0ec83f53dc 21 Aug 2023 none MIT — Details →
v1.0.1-0.20230820113947-3be6284b2d94 20 Aug 2023 none MIT — Details →
v1.0.1-0.20230814074740-d74d683d9906 14 Aug 2023 none MIT — Details →
v1.0.1-0.20230813111950-42cbc13e2259 13 Aug 2023 none MIT — Details →
v1.0.0 08 Aug 2023 none MIT — Details →
v0.3.5-0.20230717080047-984efd4d6cde 17 Jul 2023 none MIT — Details →
v0.3.5-0.20230705205352-681f12a50de3 05 Jul 2023 none MIT — Details →
v0.3.5-0.20230622084016-7c2115a5c2f2 22 Jun 2023 none MIT — Details →
v0.3.5-0.20230605133438-661beec5cb47 05 Jun 2023 none MIT — Details →
v0.3.4 23 May 2023 none MIT — Details →
v0.3.3 11 May 2023 none MIT — Details →
v0.3.2 21 Apr 2023 none MIT — Details →
v0.3.1 18 Apr 2023 none MIT — Details →
v0.3.0 15 Apr 2023 none MIT — Details →
v0.2.0 12 Apr 2023 none MIT — Details →
v0.1.2 04 Apr 2023 none MIT — Details →
v0.1.1 03 Apr 2023 none MIT — Details →
v0.1.1-0.20230327214716-ec75932abc31 27 Mar 2023 none MIT — Details →
v0.1.0 27 Mar 2023 none MIT — Details →
v0.0.0-20230326213142-ad3abb0c487f 26 Mar 2023 none MIT — Details →
v0.0.0-20230324173940-b7a73f4aaaf8 24 Mar 2023 none MIT — Details →
v0.0.0-20230323213316-c02ed30614a0 23 Mar 2023 none MIT — Details →

All 47 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/lmittmann/tint

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/lmittmann/tint

Is github.com/lmittmann/tint safe to use?

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

Vulert scores github.com/lmittmann/tint 77/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/lmittmann/tint affected?

No. v1.2.1, 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/lmittmann/tint should I use?

v1.2.1 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/lmittmann/tint have?

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

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

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