VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/tsenart/vegeta/v12: vulnerability history, versions and safety

github.com/tsenart/vegeta/v12 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/tsenart/vegeta/v12 vulnerabilities

Vulert verdict on github.com/tsenart/vegeta/v12 v12.13.0 i

Updated on 23 Oct 2026

Good news: v12.13.0, the version you would install today, has no known vulnerabilities.

Package health score 83/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

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

  • Current release v12.13.0 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 25,224 i
  • OpenSSF scorecard 3/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/tsenart/vegeta/v12, 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
v12.13.1-0.20260216140701-cf5811269046 16 Feb 2026 none MIT — Details →
v12.12.1-0.20251031110154-4b240c3089fa 31 Oct 2025 none MIT — Details →
v12.13.0 31 Oct 2025 none MIT — Details →
v12.0.0-20240729173344-03ca49e9b419 29 Jul 2024 none MIT — Details →
v12.11.4-0.20240729173344-03ca49e9b419 29 Jul 2024 none MIT — Details →
v12.12.0 29 Jul 2024 none MIT — Details →
v12.11.3 27 Jul 2024 none MIT — Details →
v12.11.3-0.20240727180900-ce93cd84160a 27 Jul 2024 none MIT — Details →
v12.11.2 27 Jul 2024 none MIT — Details →
v12.11.2-0.20240727103934-9bcc0e0b1b5a 27 Jul 2024 none MIT — Details →
v12.11.2-0.20240727103405-0ef413510bd1 27 Jul 2024 none MIT — Details →
v12.11.2-0.20231017094318-61f64b715904 17 Oct 2023 none MIT — Details →
v12.11.1 02 Oct 2023 none MIT — Details →
v12.11.1-0.20231002090339-6fbe391628ee 02 Oct 2023 none MIT — Details →
v12.11.1-0.20230818113100-712ff2e55f42 18 Aug 2023 none MIT — Details →
v12.11.1-0.20230816143456-40632542b0b6 16 Aug 2023 none MIT — Details →
v12.11.1-0.20230808103753-b4b20af16e4f 08 Aug 2023 none MIT — Details →
v12.10.1-0.20230724182032-e49c367a0149 24 Jul 2023 none MIT — Details →
v12.11.0 24 Jul 2023 none MIT — Details →
v12.10.1-0.20230719131258-73d929f41758 19 Jul 2023 none MIT — Details →
v12.10.1-0.20230718212123-ca2362d5485e 18 Jul 2023 none MIT — Details →
v12.10.1-0.20230717074211-225b7d7bfe10 17 Jul 2023 none MIT — Details →
v12.10.1-0.20230716180456-9fba76955e42 16 Jul 2023 none MIT — Details →
v12.10.0 16 Jul 2023 none MIT — Details →
v12.9.1-0.20230715171117-8bd8a188529d 15 Jul 2023 none MIT — Details →
v12.9.1-0.20230715163850-dd4d39fe5f85 15 Jul 2023 none MIT — Details →
v12.9.1-0.20230715163518-8ccf2ae9fbd4 15 Jul 2023 none MIT — Details →
v12.9.1-0.20230715163226-9151f61820eb 15 Jul 2023 none MIT — Details →
v12.9.1-0.20230714174511-3e67d019e620 14 Jul 2023 none MIT — Details →
v12.9.0 14 Jul 2023 none MIT — Details →
v12.8.5-0.20230714130611-c03ddd996567 14 Jul 2023 none MIT — Details →
v12.8.5-0.20230411134101-27f553fe0911 11 Apr 2023 none MIT — Details →
v12.8.5-0.20230117154658-5ff6414d283a 17 Jan 2023 none MIT — Details →
v12.8.5-0.20220920092046-ead49901f855 20 Sep 2022 none MIT — Details →
v12.8.4-0.20201011104648-d73edf2bc266 11 Oct 2020 none MIT — Details →
v12.8.5-0.20201011104648-d73edf2bc266 11 Oct 2020 none MIT — Details →
v12.0.0-20201011103733-e04d9c0df817 11 Oct 2020 none MIT — Details →
v12.8.4 11 Oct 2020 none MIT — Details →
v12.8.4-0.20200716082530-83a3ce91dbff 16 Jul 2020 none MIT — Details →
v12.8.4-0.20200326094346-fc06a063e19c 26 Mar 2020 none MIT — Details →
v12.8.3 25 Mar 2020 none MIT — Details →
v12.8.2 24 Mar 2020 none MIT — Details →
v12.8.1 14 Mar 2020 none MIT — Details →

All 43 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/tsenart/vegeta/v12

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/tsenart/vegeta/v12

Is github.com/tsenart/vegeta/v12 safe to use?

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

Vulert scores github.com/tsenart/vegeta/v12 83/100, which reads as in good shape. 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/tsenart/vegeta/v12 affected?

No. v12.13.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/tsenart/vegeta/v12 should I use?

v12.13.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/tsenart/vegeta/v12 have?

0 vulnerabilities are recorded for github.com/tsenart/vegeta/v12 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/tsenart/vegeta/v12 vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/tsenart/vegeta/v12 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/tsenart/vegeta/v12 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/tsenart/vegeta/v12 for upcoming vulnerabilities?

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