VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/kunwardeep/paralleltest: vulnerability history, versions and safety

github.com/kunwardeep/paralleltest 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/kunwardeep/paralleltest vulnerabilities

Vulert verdict on github.com/kunwardeep/paralleltest v1.0.16 i

Updated on 23 Oct 2026

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

Package health score 70/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Inactive

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

  • Current release v1.0.16 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 61 i
  • OpenSSF scorecard 2/10 i
  • Last release this month 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/kunwardeep/paralleltest, 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
v1.0.16 08 Oct 2026 none MIT — Details →
v1.0.15 14 Oct 2025 none MIT — Details →
v1.0.15-0.20250328070408-2b63d5b2816c 28 Mar 2025 none MIT — Details →
v1.0.15-0.20250327054701-ac6fc96c1cdd 27 Mar 2025 none MIT — Details →
v1.0.15-0.20250327051411-2818d516d76a 27 Mar 2025 none MIT — Details →
v1.0.14 27 Mar 2025 none MIT — Details →
v1.0.13 26 Mar 2025 none MIT — Details →
v1.0.12 25 Mar 2025 none MIT — Details →
v1.0.11 25 Mar 2025 none MIT — Details →
v1.0.10 15 Feb 2024 none MIT — Details →
v1.0.10-0.20240215232007-2ac0c2f5ca31 15 Feb 2024 none MIT — Details →
v1.0.9 15 Dec 2023 none MIT — Details →
v1.0.9-0.20231215061507-2ff338aad4fb 15 Dec 2023 none MIT — Details →
v1.0.8 03 Aug 2023 none MIT — Details →
v1.0.8-0.20230803000436-1adbbc8698ff 03 Aug 2023 none MIT — Details →
v1.0.8-0.20230531004602-27cc4b5900d4 31 May 2023 none MIT — Details →
v1.0.7 30 May 2023 none MIT — Details →
v1.0.7-0.20230530042852-9b08fd2dc1be 30 May 2023 none MIT — Details →
v1.0.7-0.20230530042557-b922006d1ee7 30 May 2023 none MIT — Details →
v1.0.7-0.20230329123107-316e4477ce1b 29 Mar 2023 none MIT — Details →
v1.0.7-0.20230323075318-dd6f90fcd3e7 23 Mar 2023 none MIT — Details →
v1.0.6 07 Jun 2022 none MIT — Details →
v1.0.5 07 Jun 2022 none MIT — Details →
v1.0.5-0.20220607045810-bc8013766af0 07 Jun 2022 none MIT — Details →
v1.0.5-0.20220607022720-c59622a7ff8f 07 Jun 2022 none MIT — Details →
v1.0.5-0.20220607013843-705a44eea6e1 07 Jun 2022 none MIT — Details →
v1.0.5-0.20220607013026-8da1323054fe 07 Jun 2022 none MIT — Details →
v1.0.5-0.20220607010317-004da053fd20 07 Jun 2022 none MIT — Details →
v1.0.4 03 Jun 2022 none MIT — Details →
v1.0.4-0.20220524194026-0fabdff00ea2 24 May 2022 none MIT — Details →
v1.0.4-0.20220524183444-3c6bd1fb8dc8 24 May 2022 none MIT — Details →
v1.0.3 17 Sep 2021 none MIT — Details →
v1.0.3-0.20210528031633-ba645ccca7ab 28 May 2021 none MIT — Details →
v1.0.3-0.20210425033120-afb4be075f10 25 Apr 2021 none MIT — Details →
v1.0.2 15 Nov 2020 none MIT — Details →
v0.0.0-20201112114244-7adadff1631a 12 Nov 2020 none MIT — Details →
v1.0.1 12 Nov 2020 none MIT — Details →
v0.0.0-20201102045811-8baaa34d96b9 02 Nov 2020 none MIT — Details →
v0.0.0-20201102045442-db8265575033 02 Nov 2020 none MIT — Details →
v0.0.0-20201101233638-0656b5926465 01 Nov 2020 none MIT — Details →

All 40 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/kunwardeep/paralleltest

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/kunwardeep/paralleltest

Is github.com/kunwardeep/paralleltest safe to use?

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

Vulert scores github.com/kunwardeep/paralleltest 70/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/kunwardeep/paralleltest affected?

No. v1.0.16, 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/kunwardeep/paralleltest should I use?

v1.0.16 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/kunwardeep/paralleltest have?

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

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

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