VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/VividCortex/ewma: vulnerability history, versions and safety

github.com/VividCortex/ewma 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/VividCortex/ewma vulnerabilities

Vulert verdict on github.com/VividCortex/ewma v1.2.0 i

Updated on 23 Oct 2026

Good news: v1.2.0, the version you would install today, has no known vulnerabilities.

Package health score 52/100
  • Security Minor issues
  • Maintenance Unmaintained
  • Popularity Niche
  • Community Quiet

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

  • Current release v1.2.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 447 i
  • OpenSSF scorecard 3/10 i
  • Last release 65 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/VividCortex/ewma, 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-20210426205039-487e8c9fe1e2 26 Apr 2021 none MIT — Details →
v1.1.2-0.20210426205039-487e8c9fe1e2 26 Apr 2021 none MIT — Details →
v1.2.0 26 Apr 2021 none MIT — Details →
v0.0.0-20201215173432-507017d748aa 15 Dec 2020 none MIT — Details →
v1.1.2-0.20201215173432-507017d748aa 15 Dec 2020 none MIT — Details →
v1.1.2-0.20201029192457-41f1bc0f7cb2 29 Oct 2020 none MIT — Details →
v1.1.2-0.20200731194011-1fe55baea2ee 31 Jul 2020 none MIT — Details →
v1.1.2-0.20200629145621-0dc67b516bf9 29 Jun 2020 none MIT — Details →
v1.1.2-0.20200624141145-57ed08fc6bde 24 Jun 2020 none MIT — Details →
v0.0.0-20191025014947-5c04cd146b30 25 Oct 2019 none MIT — Details →
v1.1.2-0.20191025014947-5c04cd146b30 25 Oct 2019 none MIT — Details →
v0.0.0-20190522153706-0173b1dbcfaa 22 May 2019 none MIT — Details →
v1.1.2-0.20190522153706-0173b1dbcfaa 22 May 2019 none MIT — Details →
v1.1.2-0.20190522144429-0522762ae918 22 May 2019 none MIT — Details →
v1.1.2-0.20190522143258-45bf0232a70b 22 May 2019 none MIT — Details →
v0.0.0-20170804035156-43880d236f69 04 Aug 2017 none MIT — Details →
v1.1.2-0.20170804035156-43880d236f69 04 Aug 2017 none MIT — Details →
v0.0.0-20170727163023-b24eb346a94c 27 Jul 2017 none MIT — Details →
v1.1.1 27 Jul 2017 none MIT — Details →
v0.0.0-20170715231042-4cc8cc5a2a44 15 Jul 2017 none MIT — Details →
v0.0.0-20160822184503-c595cd886c22 22 Aug 2016 none MIT — Details →
v0.0.0-20160822184255-12f985407c05 22 Aug 2016 none MIT — Details →
v0.0.0-20160629123229-8b9f1311551e 29 Jun 2016 none MIT — Details →
v0.0.0-20160627130248-054d1ae5d7b0 27 Jun 2016 none MIT — Details →
v0.0.0-20160624093736-8b987647695a 24 Jun 2016 none MIT — Details →
v0.0.0-20150512184822-c34099b489e4 12 May 2015 none MIT — Details →
v0.0.0-20131001195006-7394084dd6e0 01 Oct 2013 none MIT — Details →
v0.0.0-20130904125210-a46680db5abe 04 Sep 2013 none MIT — Details →
v0.0.0-20130902141345-d3d8d186ff8b 02 Sep 2013 none MIT — Details →
v0.0.0-20130731193710-a4d14fa85be5 31 Jul 2013 none MIT — Details →
v0.0.0-20130724125515-3c6f36c784c3 24 Jul 2013 none MIT — Details →
v0.0.0-20130723175334-bb913d3856ef 23 Jul 2013 none MIT — Details →
v0.0.0-20130710203116-3a3aa7f89949 10 Jul 2013 none MIT — Details →
v0.0.0-20130709162406-2f8aa9741ab4 09 Jul 2013 none MIT — Details →
v0.0.0-20130708140311-a4792d654612 08 Jul 2013 none MIT — Details →

All 35 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/VividCortex/ewma

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/VividCortex/ewma

Is github.com/VividCortex/ewma safe to use?

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

Vulert scores github.com/VividCortex/ewma 52/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/VividCortex/ewma affected?

No. v1.2.0, 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/VividCortex/ewma should I use?

v1.2.0 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/VividCortex/ewma have?

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

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

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