VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/sagernet/sing-shadowtls: vulnerability history, versions and safety

github.com/sagernet/sing-shadowtls 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/sagernet/sing-shadowtls vulnerabilities

Vulert verdict on github.com/sagernet/sing-shadowtls v0.2.1 i

Updated on 23 Oct 2026

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

Package health score 61/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Inactive

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

  • Current release v0.2.1 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 25 i
  • OpenSSF scorecard 2/10 i
  • Last release 5 months ago i
  • Licence GPL-3.0-or-later 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/sagernet/sing-shadowtls, 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.2.2-0.20260928201441-a9c0127d5c99 28 Sep 2026 none GPL-3.0-or-later — Details →
v0.2.1 17 May 2026 none GPL-3.0-or-later — Details →
v0.2.1-0.20250503051639-fcd445d33c11 03 May 2025 none GPL-3.0-or-later — Details →
v0.2.1-0.20250503051550-003819677219 03 May 2025 none GPL-3.0-or-later — Details →
v0.2.1-0.20250503050806-9e2784f9f86e 03 May 2025 none GPL-3.0-or-later — Details →
v0.2.1-0.20250316154757-6f9e732e5056 16 Mar 2025 none GPL-3.0-or-later — Details →
v0.2.1-0.20250316144121-523d05edec1d 16 Mar 2025 none GPL-3.0-or-later — Details →
v0.2.0 06 Feb 2025 none GPL-3.0-or-later — Details →
v0.1.6-0.20241118102914-5fdf816d25ed 18 Nov 2024 none GPL-3.0-or-later — Details →
v0.2.0-alpha.2 18 Nov 2024 none GPL-3.0-or-later — Details →
v0.1.5 18 Nov 2024 none GPL-3.0-or-later — Details →
v0.1.5-0.20241118044812-97f9cf25361a 18 Nov 2024 none GPL-3.0-or-later — Details →
v0.1.5-0.20241117084441-2711c0c857f0 17 Nov 2024 none GPL-3.0-or-later — Details →
v0.1.5-0.20241117084441-320ffbe9f064 17 Nov 2024 none GPL-3.0-or-later — Details →
v0.2.0-alpha.1 17 Nov 2024 none GPL-3.0-or-later — Details →
v0.1.5-0.20241117075149-72e6b3d0fcd7 17 Nov 2024 none GPL-3.0-or-later — Details →
v0.1.5-0.20241117074739-393d0662a5bf 17 Nov 2024 none GPL-3.0-or-later — Details →
v0.1.3-0.20230723061342-fe94df5baf06 23 Jul 2023 none GPL-3.0-or-later — Details →
v0.1.4 23 Jul 2023 none GPL-3.0-or-later — Details →
v0.1.3 23 Jul 2023 none GPL-3.0-or-later — Details →
v0.1.3-0.20230703132509-93bbad3057e4 03 Jul 2023 none GPL-3.0-or-later — Details →
v0.1.2 17 Jun 2023 none GPL-3.0-or-later — Details →
v0.1.2-0.20230617041423-c2ae42ea1264 17 Jun 2023 none GPL-3.0-or-later — Details →
v0.1.2-0.20230531025805-ebadc7615da3 31 May 2023 none GPL-3.0-or-later — Details →
v0.1.2-0.20230417103049-4f682e05f19b 17 Apr 2023 none GPL-3.0-or-later — Details →
v0.1.2-0.20230417095735-2b126f9cc522 17 Apr 2023 none GPL-3.0-or-later — Details →
v0.1.1 14 Apr 2023 none GPL-3.0-or-later — Details →
v0.1.1-0.20230409094821-9abef019436f 09 Apr 2023 none GPL-3.0-or-later — Details →
v0.1.1-0.20230409075415-9858539467a8 09 Apr 2023 none GPL-3.0-or-later — Details →
v0.1.1-0.20230408141548-81d74d2a8661 08 Apr 2023 none GPL-3.0-or-later — Details →
v0.1.0 03 Mar 2023 none GPL-3.0-or-later — Details →
v0.0.0-20230221130515-dac782ca098e 21 Feb 2023 none GPL-3.0-or-later — Details →
v0.0.0-20230221123345-78e50cd7b587 21 Feb 2023 none GPL-3.0-or-later — Details →
v0.0.0-20230221110738-214729669cdc 21 Feb 2023 none GPL-3.0-or-later — Details →
v0.0.0-20230221100347-75f55ea45b99 21 Feb 2023 none GPL-3.0-or-later — Details →
v0.0.0-20230221093358-af0356df4755 21 Feb 2023 none GPL-3.0-or-later — Details →
v0.0.0-20230221081357-574313aaae1d 21 Feb 2023 none GPL-3.0-or-later — Details →
v0.0.0-20230221075551-c5ad05179260 21 Feb 2023 none GPL-3.0-or-later — Details →
v0.0.0-20230221074514-2cd10f129707 21 Feb 2023 none GPL-3.0-or-later — Details →
v0.0.0-20230220055143-e986e9cd9eb9 20 Feb 2023 none GPL-3.0-or-later — Details →
v0.0.0-20230220051631-bca621459349 20 Feb 2023 none GPL-3.0-or-later — Details →
v0.0.0-20230220051159-964e88e4dc1d 20 Feb 2023 none GPL-3.0-or-later — Details →

All 42 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/sagernet/sing-shadowtls

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/sagernet/sing-shadowtls

Is github.com/sagernet/sing-shadowtls safe to use?

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

Vulert scores github.com/sagernet/sing-shadowtls 61/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/sagernet/sing-shadowtls affected?

No. v0.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/sagernet/sing-shadowtls should I use?

v0.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/sagernet/sing-shadowtls have?

0 vulnerabilities are recorded for github.com/sagernet/sing-shadowtls 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/sagernet/sing-shadowtls vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/sagernet/sing-shadowtls 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/sagernet/sing-shadowtls 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/sagernet/sing-shadowtls for upcoming vulnerabilities?

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