Vulnerability Database · Go · Package report

github.com/ajstarks/svgo: vulnerability history, versions and safety

github.com/ajstarks/svgo 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/ajstarks/svgo v0.0.0-20211024235047-1546f124cd8b i

Updated on 23 Oct 2026

Good news: v0.0.0-20211024235047-1546f124cd8b, the version you would install today, has no known vulnerabilities.

Package health score 58/100
  • Security Minor issues
  • Maintenance Unmaintained
  • Popularity Key ecosystem project
  • Community Quiet

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

  • Current release v0.0.0-20211024235047-1546f124cd8b — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 2,254 i
  • OpenSSF scorecard 1/10 i
  • Last release 59 months ago i
  • Licence CC-BY-4.0 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/ajstarks/svgo, 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-20211024235047-1546f124cd8b 24 Oct 2021 none CC-BY-4.0 — Details →
v0.0.0-20210927141636-6d70534b1098 27 Sep 2021 none CC-BY-4.0 — Details →
v0.0.0-20210923152817-c3b6e2f0c527 23 Sep 2021 none CC-BY-4.0 — Details →
v0.0.0-20210406150507-75cfd577ce75 06 Apr 2021 none CC-BY-4.0 — Details →
v0.0.0-20200725142600-7a3c8b57fecb 25 Jul 2020 none CC-BY-4.0 — Details →
v0.0.0-20200320125537-f189e35d30ca 20 Mar 2020 none CC-BY-4.0 — Details →
v0.0.0-20200204031535-0cbcf57ea1d8 04 Feb 2020 none CC-BY-SA-3.0 — Details →
v0.0.0-20200203192613-2cf4f7976cd7 03 Feb 2020 none — — Details →
v0.0.0-20191124160048-bd5c74aaa11c 24 Nov 2019 none MIT — Details →
v0.0.0-20190826172357-de52242f3d65 26 Aug 2019 none — — Details →
v0.0.0-20190823151146-34b58fba38f5 23 Aug 2019 none — — Details →
v0.0.0-20190822155414-606e053e08af 22 Aug 2019 none — — Details →
v0.0.0-20190820155441-07834c060b06 20 Aug 2019 none — — Details →
v0.0.0-20190820131727-1cb896ff21bc 20 Aug 2019 none — — Details →
v0.0.0-20181006003313-6ce6a3bcf6cd 06 Oct 2018 none — — Details →
v0.0.0-20180830174826-7338bd80e790 30 Aug 2018 none — — Details →
v0.0.0-20180226025133-644b8db467af 26 Feb 2018 none — — Details →
v0.0.0-20171111115224-f9be02f22f2c 11 Nov 2017 none — — Details →
v0.0.0-20171025010315-ac8788947811 25 Oct 2017 none — — Details →
v0.0.0-20170524223713-fec71ff44529 24 May 2017 none — — Details →
v0.0.0-20170517002956-19107c66f5c6 17 May 2017 none — — Details →
v0.0.0-20170507103333-2489f1e6d405 07 May 2017 none — — Details →
v0.0.0-20161216231020-9f597be83ea4 16 Dec 2016 none — — Details →
v0.0.0-20160325115536-672fe547df4e 25 Mar 2016 none — — Details →
v0.0.0-20160207120024-2940f7a14f00 07 Feb 2016 none — — Details →
v0.0.0-20160115013651-71796db343b0 15 Jan 2016 none — — Details →
v0.0.0-20160103110308-544086e8a54d 03 Jan 2016 none — — Details →
v0.0.0-20151117013546-fd2151ebabde 17 Nov 2015 none — — Details →
v0.0.0-20151104111212-99831a8cf957 04 Nov 2015 none — — Details →
v0.0.0-20151013221959-a7778b8b562e 13 Oct 2015 none — — Details →
v0.0.0-20150813015907-77292617dc6b 13 Aug 2015 none — — Details →
v0.0.0-20150525211320-6bd3ede812fd 25 May 2015 none — — Details →
v0.0.0-20150517144954-df4829b0388f 17 May 2015 none — — Details →
v0.0.0-20141219144718-47ca2bbf2293 19 Dec 2014 none — — Details →
v0.0.0-20141128134208-2bb710842b05 28 Nov 2014 none — — Details →
v0.0.0-20141004211159-89e3ac64b5b3 04 Oct 2014 none — — Details →
v0.0.0-20140830115033-77777309eda9 30 Aug 2014 none — — Details →
v0.0.0-20140502122257-deded4bac90a 02 May 2014 none — — Details →
v0.0.0-20130404020640-33ea549ec36a 04 Apr 2013 none — — Details →
v0.0.0-20120208033236-d91d3105f1ea 08 Feb 2012 none — — Details →
v0.0.0-20111214232956-9585619f1c5c 14 Dec 2011 none — — Details →
v0.0.0-20111115024553-402bb84a3740 15 Nov 2011 none — — Details →
v0.0.0-20110903135730-74508cd9ff1e 03 Sep 2011 none — — Details →
v0.0.0-20110728001118-cbcb75b68a21 28 Jul 2011 none — — Details →
v0.0.0-20110330224643-1f539d4af8d2 30 Mar 2011 none — — Details →
v0.0.0-20100417024450-64a287b60380 17 Apr 2010 none — — Details →
v0.0.0-20100305233030-cef040923f96 05 Mar 2010 none — — 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/ajstarks/svgo

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/ajstarks/svgo

Is github.com/ajstarks/svgo safe to use?

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

Vulert scores github.com/ajstarks/svgo 58/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/ajstarks/svgo affected?

No. v0.0.0-20211024235047-1546f124cd8b, 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/ajstarks/svgo should I use?

v0.0.0-20211024235047-1546f124cd8b 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/ajstarks/svgo have?

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

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

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