VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/lithammer/dedent: vulnerability history, versions and safety

github.com/lithammer/dedent 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/lithammer/dedent vulnerabilities

Vulert verdict on github.com/lithammer/dedent v1.1.0 i

Updated on 23 Oct 2026

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

Package health score 50/100
  • Security Minor issues
  • Maintenance Unmaintained
  • Popularity Niche
  • Community Inactive

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

  • Current release v1.1.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 122 i
  • OpenSSF scorecard 3/10 i
  • Last release 93 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/lithammer/dedent, 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.1-0.20260801175126-c4ebb33feb25 01 Aug 2026 none MIT — Details →
v1.1.1-0.20260101112750-04ba52d0db79 01 Jan 2026 none MIT — Details →
v1.1.1-0.20251001135651-29b9889e1278 01 Oct 2025 none MIT — Details →
v1.1.1-0.20250602080513-7e3d79e648ca 02 Jun 2025 none MIT — Details →
v1.1.1-0.20250602080021-0d1434ff5ea6 02 Jun 2025 none MIT — Details →
v1.1.1-0.20240601112521-5c4fe775cec8 01 Jun 2024 none MIT — Details →
v1.1.1-0.20240301123614-2b3e80305fd2 01 Mar 2024 none MIT — Details →
v1.1.1-0.20240101120252-0572153f5f8b 01 Jan 2024 none MIT — Details →
v1.1.1-0.20231001120919-366dff7d87e3 01 Oct 2023 none MIT — Details →
v1.1.1-0.20230901120101-984376ad91a5 01 Sep 2023 none MIT — Details →
v1.1.1-0.20230701125800-0660afccc1fc 01 Jul 2023 none MIT — Details →
v1.1.1-0.20230401121214-c855d971dc15 01 Apr 2023 none MIT — Details →
v1.1.1-0.20230401115638-2d15204e5ba3 01 Apr 2023 none MIT — Details →
v1.1.1-0.20230201111501-33c5ba70706a 01 Feb 2023 none MIT — Details →
v1.1.1-0.20221201110444-34fbaaf5bf32 01 Dec 2022 none MIT — Details →
v1.1.1-0.20221101114516-802bd2baef5e 01 Nov 2022 none MIT — Details →
v1.1.1-0.20220601124816-dbd7d3c3442a 01 Jun 2022 none MIT — Details →
v1.1.1-0.20220601113519-aab5539ac8f8 01 Jun 2022 none MIT — Details →
v1.1.1-0.20220523064612-216405d74ad6 23 May 2022 none MIT — Details →
v1.1.1-0.20220523064506-1e244e9f64c6 23 May 2022 none MIT — Details →
v1.1.1-0.20220401113346-c59315e45109 01 Apr 2022 none MIT — Details →
v1.1.1-0.20220301111856-4be21c4c687a 01 Mar 2022 none MIT — Details →
v1.1.1-0.20220101112210-f4cc02010b3e 01 Jan 2022 none MIT — Details →
v1.1.1-0.20220101110153-0660bec67abd 01 Jan 2022 none MIT — Details →
v1.1.1-0.20211005091920-0a135f7d9e02 05 Oct 2021 none MIT — Details →
v1.1.1-0.20210901110126-9185f85166e5 01 Sep 2021 none MIT — Details →
v1.1.1-0.20210316202958-5940d91a4ead 16 Mar 2021 none MIT — Details →
v1.1.1-0.20210316202715-0e9c4f3c722b 16 Mar 2021 none MIT — Details →
v1.1.1-0.20200414195415-793783774541 14 Apr 2020 none MIT — Details →
v1.1.1-0.20200130155137-baaeddb12551 30 Jan 2020 none MIT — Details →
v1.1.1-0.20191209085553-fd94d2e10bde 09 Dec 2019 none MIT — Details →
v1.1.1-0.20191209085303-cf5b4609aa1a 09 Dec 2019 none MIT — Details →
v1.1.1-0.20190124093549-bacd562a6875 24 Jan 2019 none MIT — Details →
v0.0.0-20190106220057-8478954c3bc8 06 Jan 2019 none MIT — Details →
v1.1.0 06 Jan 2019 none MIT — Details →
v1.0.1-0.20181002143321-664402034531 02 Oct 2018 none MIT — Details →
v1.0.1-0.20180618074828-3b5f93832f26 18 Jun 2018 none MIT — Details →
v1.0.1-0.20180305212856-bb25b1f617cf 05 Mar 2018 none MIT — Details →
v0.0.0-20150819195903-020d11c3b9c0 19 Aug 2015 none MIT — Details →
v1.0.1-0.20150819195903-020d11c3b9c0 19 Aug 2015 none MIT — Details →
v1.0.1-0.20150803070300-48ba5c3007b1 03 Aug 2015 none MIT — Details →
v1.0.0 17 May 2015 none MIT — Details →
v0.0.0-20150328091002-18d4495e675a 28 Mar 2015 none MIT — Details →
v0.0.0-20150325201122-00b083907f0d 25 Mar 2015 none MIT — Details →

All 44 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/lithammer/dedent

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/lithammer/dedent

Is github.com/lithammer/dedent safe to use?

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

Vulert scores github.com/lithammer/dedent 50/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/lithammer/dedent affected?

No. v1.1.0, 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/lithammer/dedent should I use?

v1.1.0 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/lithammer/dedent have?

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

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

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