VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/srwiley/oksvg: vulnerability history, versions and safety

github.com/srwiley/oksvg 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/srwiley/oksvg vulnerabilities

Vulert verdict on github.com/srwiley/oksvg v0.0.0-20221011165216-be6e8873101c i

Updated on 23 Oct 2026

Good news: v0.0.0-20221011165216-be6e8873101c, the version you would install today, has no known vulnerabilities.

Package health score 55/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Niche
  • Community Inactive

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

  • Current release v0.0.0-20221011165216-be6e8873101c — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 185 i
  • OpenSSF scorecard 1/10 i
  • Last release 48 months ago i
  • Licence BSD-3-Clause 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/srwiley/oksvg, 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-20221011165216-be6e8873101c 11 Oct 2022 none BSD-3-Clause — Details →
v0.0.0-20221002174631-3742d547bf3c 02 Oct 2022 none BSD-3-Clause — Details →
v0.0.0-20220904191616-8889df18e8f4 04 Sep 2022 none BSD-3-Clause — Details →
v0.0.0-20220731023508-a61f04f16b76 31 Jul 2022 none BSD-3-Clause — Details →
v0.0.0-20220731023443-ded15b7bd12e 31 Jul 2022 none BSD-3-Clause — Details →
v0.0.0-20220731022459-dd853b67852c 31 Jul 2022 none BSD-3-Clause — Details →
v0.0.0-20220128195007-1f435e4c2b44 28 Jan 2022 none BSD-3-Clause — Details →
v0.0.0-20211120171407-1837d6608d8c 20 Nov 2021 none BSD-3-Clause — Details →
v0.0.0-20211104221756-aeb4ca2c1505 04 Nov 2021 none BSD-3-Clause — Details →
v0.0.0-20211104221156-6cb48ac352a1 04 Nov 2021 none BSD-3-Clause — Details →
v0.0.0-20211104181251-208db556fb2a 04 Nov 2021 none BSD-3-Clause — Details →
v0.0.0-20210519022825-9fc0c575d5fe 19 May 2021 none BSD-3-Clause — Details →
v0.0.0-20210320200257-875f767ac39a 20 Mar 2021 none BSD-3-Clause — Details →
v0.0.0-20210320192256-169ac1008df2 20 Mar 2021 none BSD-3-Clause — Details →
v0.0.0-20210209000435-a757b9cbd472 09 Feb 2021 none BSD-3-Clause — Details →
v0.0.0-20200311192757-870daf9aa564 11 Mar 2020 none BSD-3-Clause — Details →
v0.0.0-20200311183851-7dc61e67a43a 11 Mar 2020 none BSD-3-Clause — Details →
v0.0.0-20190829233741-58e08c8fe40e 29 Aug 2019 none BSD-3-Clause — Details →
v0.0.0-20190414003808-c520f0a6c5cc 14 Apr 2019 none BSD-3-Clause — Details →
v0.0.0-20190413181956-8b9472843d1e 13 Apr 2019 none BSD-3-Clause — Details →
v0.0.0-20190310040902-7a13f3532235 10 Mar 2019 none BSD-3-Clause — Details →
v0.0.0-20190306153453-90a6e0899d91 06 Mar 2019 none BSD-3-Clause — Details →
v0.0.0-20190105194046-ccbc7673cdf3 05 Jan 2019 none BSD-3-Clause — Details →
v0.0.0-20190103232948-bc8e13fe89ab 03 Jan 2019 none BSD-3-Clause — Details →
v0.0.0-20181204230515-738c2688bcb3 04 Dec 2018 none BSD-3-Clause — Details →

All 25 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/srwiley/oksvg

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/srwiley/oksvg

Is github.com/srwiley/oksvg safe to use?

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

Vulert scores github.com/srwiley/oksvg 55/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/srwiley/oksvg affected?

No. v0.0.0-20221011165216-be6e8873101c, 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/srwiley/oksvg should I use?

v0.0.0-20221011165216-be6e8873101c 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/srwiley/oksvg have?

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

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

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