VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/theckman/yacspin: vulnerability history, versions and safety

github.com/theckman/yacspin 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/theckman/yacspin vulnerabilities

Vulert verdict on github.com/theckman/yacspin v0.13.12 i

Updated on 23 Oct 2026

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

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

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

  • Current release v0.13.12 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 456 i
  • OpenSSF scorecard 2/10 i
  • Last release 57 months ago i
  • Licence Apache-2.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/theckman/yacspin, 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.13.13-0.20220103063505-94bad55b3354 03 Jan 2022 none Apache-2.0 — Details →
v0.13.13-0.20220103050930-49cd3995d263 03 Jan 2022 none Apache-2.0 — Details →
v0.13.13-0.20220102003941-543027681bfd 02 Jan 2022 none Apache-2.0 — Details →
v0.13.13-0.20220102002225-85d2c04ded10 02 Jan 2022 none Apache-2.0 — Details →
v0.13.13-0.20220102001946-336a861eb144 02 Jan 2022 none Apache-2.0 — Details →
v0.13.13-0.20211231101627-b9b3c0f153ff 31 Dec 2021 none Apache-2.0 — Details →
v0.13.13-0.20211231101430-2fcc2a1af49a 31 Dec 2021 none Apache-2.0 — Details →
v0.13.13-0.20211231100743-039341e9e3e7 31 Dec 2021 none Apache-2.0 — Details →
v0.13.12 31 Dec 2021 none Apache-2.0 — Details →
v0.13.11 30 Dec 2021 none Apache-2.0 — Details →
v0.13.10 30 Dec 2021 none Apache-2.0 — Details →
v0.13.9 30 Dec 2021 none Apache-2.0 — Details →
v0.13.9-0.20211230025822-c465bed1e195 30 Dec 2021 none Apache-2.0 — Details →
v0.13.8 29 Dec 2021 none Apache-2.0 — Details →
v0.13.7 28 Dec 2021 none Apache-2.0 — Details →
v0.13.7-0.20211228214118-324fd5ba182a 28 Dec 2021 none Apache-2.0 — Details →
v0.13.6 21 Dec 2021 none Apache-2.0 — Details →
v0.13.5 17 Dec 2021 none Apache-2.0 — Details →
v0.13.4 15 Dec 2021 none Apache-2.0 — Details →
v0.13.3 15 Dec 2021 none Apache-2.0 — Details →
v0.13.2 12 Dec 2021 none Apache-2.0 — Details →
v0.13.1 12 Dec 2021 none Apache-2.0 — Details →
v0.13.0 11 Dec 2021 none Apache-2.0 — Details →
v0.12.1-0.20211211214017-94aed01885b1 11 Dec 2021 none Apache-2.0 — Details →
v0.12.0 11 Dec 2021 none Apache-2.0 — Details →
v0.11.1 11 Dec 2021 none Apache-2.0 — Details →
v0.11.1-0.20211211071720-93f927d0ea51 11 Dec 2021 none Apache-2.0 — Details →
v0.11.0 11 Dec 2021 none Apache-2.0 — Details →
v0.10.0 11 Dec 2021 none Apache-2.0 — Details →
v0.9.1-0.20211211024313-27f7396fc4c5 11 Dec 2021 none Apache-2.0 — Details →
v0.9.1-0.20211210234459-d816730eb606 10 Dec 2021 none Apache-2.0 — Details →
v0.9.1-0.20211210085220-1649dba552ff 10 Dec 2021 none Apache-2.0 — Details →
v0.9.0 10 Dec 2021 none Apache-2.0 — Details →
v0.8.1-0.20200323012429-20917646fa64 23 Mar 2020 none Apache-2.0 — Details →
v0.8.0 22 Mar 2020 none Apache-2.0 — Details →
v0.7.0 18 Mar 2020 none Apache-2.0 — Details →
v0.6.0 18 Mar 2020 none Apache-2.0 — Details →
v0.5.0 17 Mar 2020 none Apache-2.0 — Details →
v0.4.0 30 Dec 2019 none Apache-2.0 — Details →
v0.3.0 29 Dec 2019 none Apache-2.0 — Details →
v0.2.0 29 Dec 2019 none Apache-2.0 — Details →
v0.1.3 29 Dec 2019 none Apache-2.0 — Details →
v0.1.2 29 Dec 2019 none Apache-2.0 — Details →
v0.1.1 29 Dec 2019 none Apache-2.0 — Details →
v0.1.0 29 Dec 2019 none Apache-2.0 — Details →
v0.0.0 29 Dec 2019 none Apache-2.0 — Details →

All 46 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/theckman/yacspin

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/theckman/yacspin

Is github.com/theckman/yacspin safe to use?

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

Vulert scores github.com/theckman/yacspin 49/100, which reads as risky. 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/theckman/yacspin affected?

No. v0.13.12, 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/theckman/yacspin should I use?

v0.13.12 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/theckman/yacspin have?

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

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

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