VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/catenacyber/perfsprint: vulnerability history, versions and safety

github.com/catenacyber/perfsprint 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/catenacyber/perfsprint vulnerabilities

Vulert verdict on github.com/catenacyber/perfsprint v0.10.1 i

Updated on 23 Oct 2026

Good news: v0.10.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.10.1 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.10.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release v0.10.1 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 46 i
  • OpenSSF scorecard 2/10 i
  • Last release 11 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/catenacyber/perfsprint, 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.10.2-0.20260929170517-69da4b30c27b 29 Sep 2026 none MIT — Details →
v0.10.2-0.20251107105523-f5cd7f60a6f7 07 Nov 2025 none MIT — Details →
v0.10.1 07 Nov 2025 none MIT — Details →
v0.10.1-0.20251018192701-109aa9915300 18 Oct 2025 none MIT — Details →
v0.10.1-0.20251015195431-44c6a96eca8d 15 Oct 2025 none MIT — Details →
v0.10.0 12 Oct 2025 none MIT — Details →
v0.9.1 12 Mar 2025 none MIT — Details →
v0.9.0 26 Feb 2025 none MIT — Details →
v0.8.2 18 Feb 2025 none MIT — Details →
v0.8.2-0.20250217152738-3d785f02a667 17 Feb 2025 none MIT — Details →
v0.8.2-0.20250211155749-31fa92210a56 11 Feb 2025 none MIT — Details →
v0.8.1 08 Feb 2025 none MIT — Details →
v0.8.1-0.20250208104057-adcb7c6be5bd 08 Feb 2025 none MIT — Details →
v0.8.0 05 Feb 2025 none MIT — Details →
v0.7.2-0.20241126214028-d9131b0576a8 26 Nov 2024 none MIT — Details →
v0.7.2-0.20241121165602-a34cbe326a6b 21 Nov 2024 none MIT — Details →
v0.7.2-0.20241120124319-f7c1bb995dbb 20 Nov 2024 none MIT — Details →
v0.7.2-0.20241119200724-7f3ce4e8ba59 19 Nov 2024 none MIT — Details →
v0.7.2-0.20241023200257-e84fb820eee9 23 Oct 2024 none MIT — Details →
v0.7.1 19 Feb 2024 none MIT — Details →
v0.7.1-0.20240219151652-9d2eaecf6b18 19 Feb 2024 none MIT — Details →
v0.6.1-0.20240214092219-5dbf3ce6a74f 14 Feb 2024 none MIT — Details →
v0.7.0 14 Feb 2024 none MIT — Details →
v0.6.1-0.20240208204918-b66013fa8dbd 08 Feb 2024 none MIT — Details →
v0.5.1-0.20240202211535-94b53d906abe 02 Feb 2024 none MIT — Details →
v0.6.0 02 Feb 2024 none MIT — Details →
v0.5.1-0.20240108125810-fae648ae9587 08 Jan 2024 none MIT — Details →
v0.4.2-0.20231213213602-c553de90c979 13 Dec 2023 none MIT — Details →
v0.5.0 13 Dec 2023 none MIT — Details →
v0.4.1 13 Dec 2023 none MIT — Details →
v0.3.2-0.20231129142821-d3ce5b23ea3a 29 Nov 2023 none MIT — Details →
v0.4.0 29 Nov 2023 none MIT — Details →
v0.3.1 25 Oct 2023 none MIT — Details →
v0.3.1-0.20231025152556-9cd4cff6be2c 25 Oct 2023 none MIT — Details →
v0.2.3-0.20231024190411-fc24f10e1bd9 24 Oct 2023 none MIT — Details →
v0.3.0 24 Oct 2023 none MIT — Details →
v0.2.2 24 Oct 2023 none MIT — Details →
v0.2.1 24 Oct 2023 none MIT — Details →
v0.2.1-0.20231020132138-e95837062d16 20 Oct 2023 none MIT — Details →
v0.1.1-0.20231018190405-cc7513178a22 18 Oct 2023 none MIT — Details →
v0.2.0 18 Oct 2023 none MIT — Details →
v0.1.1-0.20231018185310-e3acf8104fab 18 Oct 2023 none MIT — 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/catenacyber/perfsprint

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/catenacyber/perfsprint

Is github.com/catenacyber/perfsprint safe to use?

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

Vulert scores github.com/catenacyber/perfsprint 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/catenacyber/perfsprint affected?

No. v0.10.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/catenacyber/perfsprint should I use?

v0.10.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/catenacyber/perfsprint have?

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

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

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