Vulnerability Database · Go · Package report

github.com/3th1nk/cidr: vulnerability history, versions and safety

Q: How do I monitor github.com/3th1nk/cidr for upcoming vulnerabilities?

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

github.com/3th1nk/cidr is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.

0 vulnerabilities recorded

Nothing recorded for this package in the Go ecosystem.

0 with no fix published

Every vulnerability has a patched version to move to.

0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →

0 malicious-package vulnerabilities

No published version shipped hostile code.

See all github.com/3th1nk/cidr vulnerabilities

Vulert verdict on github.com/3th1nk/cidr v0.4.0 i

Updated on 23 Oct 2026

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

Package health score 68/100

Security Minor issues
Maintenance Sustainable
Popularity Niche
Community Inactive

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

Current release v0.4.0 — unaffected i
Vulnerabilities on record 0 i
Highest CVSS n/a i
With no published fix 0 i
Stars 95 i
OpenSSF scorecard 1/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.

Scan your app free →

01 Versions

Which versions are affected

Every version Vulert tracks for github.com/3th1nk/cidr, 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.

Version	Released	Vulert vulnerabilities	Licence	Fix published	Details
v0.4.0	29 Sep 2026	none	MIT	—	Details →
v0.2.1-0.20250820044631-8c0041700a5e	20 Aug 2025	none	MIT	—	Details →
v0.3.0	20 Aug 2025	none	MIT	—	Details →
v0.2.1-0.20250325063059-1b493cfc1892	25 Mar 2025	none	MIT	—	Details →
v0.2.1-0.20231014175352-807b61e4acd1	14 Oct 2023	none	MIT	—	Details →
v0.2.0	15 Dec 2022	none	MIT	—	Details →
v0.0.0-20220718125058-47306b78b56c	18 Jul 2022	none	MIT	—	Details →
v0.1.0	18 Jul 2022	none	MIT	—	Details →
v0.0.0-20210818063431-caa3bf6ce590	18 Aug 2021	none	MIT	—	Details →
v0.0.0-20200222033026-ac57bd3ad921	22 Feb 2020	none	MIT	—	Details →
v0.0.0-20190917115846-f42315b62315	17 Sep 2019	none	MIT	—	Details →

All 11 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.

Other ways into the data

03 Vulnerabilities

Recorded vulnerabilities for github.com/3th1nk/cidr

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/3th1nk/cidr

Is github.com/3th1nk/cidr safe to use?

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

Vulert scores github.com/3th1nk/cidr 68/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/3th1nk/cidr affected?

No. v0.4.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/3th1nk/cidr should I use?

v0.4.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/3th1nk/cidr have?

0 vulnerabilities are recorded for github.com/3th1nk/cidr 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/3th1nk/cidr vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/3th1nk/cidr 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/3th1nk/cidr 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/3th1nk/cidr for upcoming vulnerabilities?

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