VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/templexxx/cpu: vulnerability history, versions and safety

github.com/templexxx/cpu 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/templexxx/cpu vulnerabilities

Vulert verdict on github.com/templexxx/cpu v0.1.1 i

Updated on 23 Oct 2026

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

Package health score 48/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Little adoption
  • Community Inactive

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

  • Current release v0.1.1 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 28 i
  • OpenSSF scorecard 1/10 i
  • Last release 31 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/templexxx/cpu, 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.1.1 03 Mar 2024 none BSD-3-Clause — Details →
v0.1.1-0.20240303154708-598a14b050c5 03 Mar 2024 none BSD-3-Clause — Details →
v0.1.1-0.20231108105306-42dcd23db6f4 08 Nov 2023 none BSD-3-Clause — Details →
v0.0.10-0.20221210144101-7587a738ad7d 10 Dec 2022 none BSD-3-Clause — Details →
v0.1.0 10 Dec 2022 none BSD-3-Clause — Details →
v0.0.10-0.20211111114238-98168dcec14a 11 Nov 2021 none BSD-3-Clause — Details →
v0.0.9 24 Oct 2021 none BSD-3-Clause — Details →
v0.0.8 14 Aug 2021 none BSD-3-Clause — Details →
v0.0.8-0.20210814062521-2ac619437c68 14 Aug 2021 none BSD-3-Clause — Details →
v0.0.8-0.20210423085042-1c810926b5dd 23 Apr 2021 none BSD-3-Clause — Details →
v0.0.8-0.20201106075209-6651b1c9ec29 06 Nov 2020 none BSD-3-Clause — Details →
v0.0.8-0.20200904080713-862a179c181c 04 Sep 2020 none BSD-3-Clause — Details →
v0.0.7 29 Jun 2020 none BSD-3-Clause — Details →
v0.0.6 28 Jun 2020 none BSD-3-Clause — Details →
v0.0.6-0.20200627032718-713168a7a581 27 Jun 2020 none BSD-3-Clause — Details →
v0.0.5 26 Jun 2020 none BSD-3-Clause — Details →
v0.0.4 25 Jun 2020 none BSD-3-Clause — Details →
v0.0.3 24 Jun 2020 none BSD-3-Clause — Details →
v0.0.2 24 Jun 2020 none BSD-3-Clause — Details →
v0.0.1 07 Dec 2019 none BSD-3-Clause — Details →
v0.0.0-20180724030738-8b437a7a2c87 24 Jul 2018 none BSD-3-Clause — Details →
v0.0.0-20180724005739-0678fc783b34 24 Jul 2018 none BSD-3-Clause — Details →

All 22 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/templexxx/cpu

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/templexxx/cpu

Is github.com/templexxx/cpu safe to use?

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

Vulert scores github.com/templexxx/cpu 48/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/templexxx/cpu affected?

No. v0.1.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/templexxx/cpu should I use?

v0.1.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/templexxx/cpu have?

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

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

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