Vulnerability Database · Go · Package report

github.com/noql-net/certpool: vulnerability history, versions and safety

github.com/noql-net/certpool 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.

Vulert verdict on github.com/noql-net/certpool v0.0.0-20251124134124-4dca7a6632cb i

Updated on 23 Oct 2026

Good news: v0.0.0-20251124134124-4dca7a6632cb, the version you would install today, has no known vulnerabilities.

Package health score 70/100
  • Security No known security issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Inactive

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

  • Current release v0.0.0-20251124134124-4dca7a6632cb — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Last release 10 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/noql-net/certpool, 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-20251124134124-4dca7a6632cb 24 Nov 2025 none BSD-3-Clause — Details →
v0.0.0-20251031010508-a6d1add8fb9e 31 Oct 2025 none BSD-3-Clause — Details →
v0.0.0-20251014151119-4130eb627c08 14 Oct 2025 none BSD-3-Clause — Details →
v0.0.0-20251004005808-ffbc652faae4 04 Oct 2025 none BSD-3-Clause — Details →
v0.0.0-20250913163944-4da2967b72b2 13 Sep 2025 none BSD-3-Clause — Details →
v0.0.0-20250713011742-73291c48ecc1 13 Jul 2025 none BSD-3-Clause — Details →
v0.0.0-20250703123530-a751c7789414 03 Jul 2025 none BSD-3-Clause — Details →
v0.0.0-20250623181535-841f87c59c5f 23 Jun 2025 none BSD-3-Clause — Details →
v0.0.0-20250417123926-688b52c002ee 17 Apr 2025 none BSD-3-Clause — Details →
v0.0.0-20250128174907-b15afbea6eae 28 Jan 2025 none BSD-3-Clause — Details →
v0.0.0-20240829011701-581572c93b1a 29 Aug 2024 none BSD-3-Clause — Details →
v0.0.0-20240719060413-a5ed62ecc62a 19 Jul 2024 none BSD-3-Clause — Details →
v0.0.0-20240714121046-4a98fd4c57dc 14 Jul 2024 none BSD-3-Clause — Details →

All 13 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/noql-net/certpool

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/noql-net/certpool

Is github.com/noql-net/certpool safe to use?

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

Vulert scores github.com/noql-net/certpool 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/noql-net/certpool affected?

No. v0.0.0-20251124134124-4dca7a6632cb, 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/noql-net/certpool should I use?

v0.0.0-20251124134124-4dca7a6632cb 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/noql-net/certpool have?

0 vulnerabilities are recorded for github.com/noql-net/certpool 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/noql-net/certpool vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/noql-net/certpool 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/noql-net/certpool 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/noql-net/certpool for upcoming vulnerabilities?

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