Vulnerability Database · Go · Package report

github.com/creachadair/tomledit: vulnerability history, versions and safety

github.com/creachadair/tomledit 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/creachadair/tomledit v0.0.29 i

Updated on 23 Oct 2026

Good news: v0.0.29, the version you would install today, has no known vulnerabilities.

Package health score 65/100
  • Security No known security issues
  • Maintenance Maintaining
  • Popularity Little adoption
  • Community Inactive

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

  • Current release v0.0.29 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 10 i
  • Last release 13 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/creachadair/tomledit, 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.30-0.20251023215135-3d76b2bf6165 23 Oct 2025 none MIT — Details →
v0.0.30-0.20251002031859-ff54adef1bed 02 Oct 2025 none MIT — Details →
v0.0.29 21 Sep 2025 none MIT — Details →
v0.0.29-0.20250901153213-e852672233df 01 Sep 2025 none MIT — Details →
v0.0.29-0.20250825180856-2b388a6ddb91 25 Aug 2025 none MIT — Details →
v0.0.28 15 Mar 2025 none MIT — Details →
v0.0.27 05 Jan 2025 none MIT — Details →
v0.0.27-0.20241211163244-3e7f1df29b38 11 Dec 2024 none MIT — Details →
v0.0.27-0.20241202163308-6477d84880cb 02 Dec 2024 none MIT — Details →
v0.0.27-0.20241116020011-faf38cc9e9c3 16 Nov 2024 none MIT — Details →
v0.0.27-0.20241113154907-c6f6c50e230c 13 Nov 2024 none MIT — Details →
v0.0.27-0.20241111194916-827f40791b03 11 Nov 2024 none MIT — Details →
v0.0.27-0.20240908150144-5bca07a27009 08 Sep 2024 none MIT — Details →
v0.0.27-0.20240902152704-38093c594940 02 Sep 2024 none MIT — Details →
v0.0.27-0.20240817033631-b1bd09aea99b 17 Aug 2024 none MIT — Details →
v0.0.27-0.20240330210706-a840c4c866fc 30 Mar 2024 none MIT — Details →
v0.0.26 17 Mar 2024 none MIT — Details →
v0.0.26-0.20240317161937-f152318edf2b 17 Mar 2024 none MIT — Details →
v0.0.26-0.20240229221509-8ada88e20431 29 Feb 2024 none MIT — Details →
v0.0.26-0.20240213164506-2f7165707123 13 Feb 2024 none MIT — Details →
v0.0.26-0.20240128034625-5cc456de3ce8 28 Jan 2024 none MIT — Details →
v0.0.26-0.20231211041337-2bacfc66264a 11 Dec 2023 none MIT — Details →
v0.0.25 24 Aug 2023 none MIT — Details →
v0.0.25-0.20230824154849-ce5ac3f9e1af 24 Aug 2023 none MIT — Details →
v0.0.25-0.20230601202804-cb1e1931eb36 01 Jun 2023 none MIT — Details →
v0.0.25-0.20230117012720-813f0a0223ae 17 Jan 2023 none MIT — Details →
v0.0.25-0.20230110233814-b6660485e202 10 Jan 2023 none MIT — Details →
v0.0.24 25 Oct 2022 none MIT — Details →
v0.0.24-0.20220810231020-3f99bb6461d6 10 Aug 2022 none MIT — Details →
v0.0.23 23 Jul 2022 none MIT — Details →
v0.0.22 10 May 2022 none MIT — Details →
v0.0.21 10 May 2022 none MIT — Details →
v0.0.20 10 May 2022 none MIT — Details →
v0.0.20-0.20220429041657-9f9039fa9b9e 29 Apr 2022 none MIT — Details →
v0.0.19 28 Apr 2022 none MIT — Details →
v0.0.19-0.20220426235503-d1160a474bfb 26 Apr 2022 none MIT — Details →
v0.0.19-0.20220426165607-56f28f4ea0d3 26 Apr 2022 none MIT — Details →
v0.0.19-0.20220424073728-3b8b38027417 24 Apr 2022 none MIT — Details →
v0.0.19-0.20220422004740-409951b69961 22 Apr 2022 none MIT — Details →
v0.0.19-0.20220422000628-26acca1df827 22 Apr 2022 none MIT — Details →
v0.0.18 21 Apr 2022 none MIT — Details →
v0.0.18-0.20220421190640-1ab2c8d654dd 21 Apr 2022 none MIT — Details →
v0.0.18-0.20220421184322-643b27c8f481 21 Apr 2022 none MIT — Details →
v0.0.17 21 Apr 2022 none MIT — Details →
v0.0.17-0.20220419003145-874d88f9a47f 19 Apr 2022 none MIT — Details →
v0.0.17-0.20220416203012-0791eac0d2e2 16 Apr 2022 none MIT — Details →
v0.0.17-0.20220416190544-c2119f311c0d 16 Apr 2022 none MIT — Details →
v0.0.17-0.20220414001140-5752b2e5f6e4 14 Apr 2022 none MIT — Details →
v0.0.16 13 Apr 2022 none MIT — Details →
v0.0.16-0.20220413041321-955df82f019e 13 Apr 2022 none MIT — Details →
v0.0.15 11 Apr 2022 none MIT — Details →
v0.0.14 11 Apr 2022 none MIT — Details →
v0.0.13 11 Apr 2022 none MIT — Details →
v0.0.12 11 Apr 2022 none MIT — Details →
v0.0.11 10 Apr 2022 none MIT — Details →
v0.0.10 10 Apr 2022 none MIT — Details →
v0.0.10-0.20220410182138-b31dd47d8e6f 10 Apr 2022 none MIT — Details →
v0.0.10-0.20220410160759-376a383e0cfd 10 Apr 2022 none MIT — Details →
v0.0.10-0.20220410061151-d2042f1ab1a6 10 Apr 2022 none MIT — Details →
v0.0.9 09 Apr 2022 none MIT — Details →
v0.0.8 09 Apr 2022 none MIT — Details →
v0.0.7 09 Apr 2022 none MIT — Details →
v0.0.7-0.20220409153546-f8834cd5fe7a 09 Apr 2022 none MIT — Details →
v0.0.6 09 Apr 2022 none MIT — Details →
v0.0.6-0.20220408233120-16adb1d6da12 08 Apr 2022 none MIT — Details →
v0.0.5 08 Apr 2022 none MIT — Details →
v0.0.4 08 Apr 2022 none MIT — Details →
v0.0.4-0.20220408023504-eb60fb78b9b1 08 Apr 2022 none MIT — Details →
v0.0.3 07 Apr 2022 none MIT — Details →
v0.0.2 07 Apr 2022 none MIT — Details →
v0.0.2-0.20220407001013-02c69834baa9 07 Apr 2022 none MIT — Details →
v0.0.1 06 Apr 2022 none MIT — Details →
v0.0.0-20220406203155-3d1c2df4e6eb 06 Apr 2022 none MIT — Details →

All 73 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/creachadair/tomledit

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/creachadair/tomledit

Is github.com/creachadair/tomledit safe to use?

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

Vulert scores github.com/creachadair/tomledit 65/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/creachadair/tomledit affected?

No. v0.0.29, 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/creachadair/tomledit should I use?

v0.0.29 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/creachadair/tomledit have?

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

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

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