Vulnerability Database · Go · Package report
github.com/yl2chen/cidranger: vulnerability history, versions and safety
github.com/yl2chen/cidranger is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.
Nothing recorded for this package in the Go ecosystem.
Every vulnerability has a patched version to move to.
No published version shipped hostile code.
Vulert verdict on github.com/yl2chen/cidranger v1.0.2 i
Updated on 23 Oct 2026
Good news: v1.0.2, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Unmaintained
- Popularity Widely used
- Community Quiet
What to do: Stay on v1.0.2 or newer. This can change: a vulnerability disclosed tomorrow can affect v1.0.2 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v1.0.2 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 967 i
- OpenSSF scorecard 1/10 i
- Last release 73 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/yl2chen/cidranger, 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.
- v0.0.0-20210928021809-d1cb2c52f37a 28 Sep 2021
- v1.0.3-0.20210928021809-d1cb2c52f37a 28 Sep 2021
- v1.0.2 21 Sep 2020
- v1.0.1 15 Aug 2020
- v0.0.0-20191223231341-e434ea71859d 23 Dec 2019
- v0.0.0-20191223120717-6402a47f9d8a 23 Dec 2019
- v0.0.0-20191223063343-81d435411dd9 23 Dec 2019
- v1.0.0 21 Dec 2019
- v0.0.0-20190806234802-fed7223fd934 06 Aug 2019
- v0.0.0-20190118162706-cf0421536ed5 18 Jan 2019
- v0.0.0-20180214081945-928b519e5268 14 Feb 2018
- v0.0.0-20180204210701-3e90dcc83e33 04 Feb 2018
- v0.0.0-20180201225327-bc6ed10625c9 01 Feb 2018
- v0.0.0-20171127194420-9a60958aefdb 27 Nov 2017
- v0.0.0-20170925183613-ebd5c6cd5ecb 25 Sep 2017
- v0.0.0-20170911232230-e27c5f9b6bbd 11 Sep 2017
- v0.0.0-20170829201630-0721a06f3960 29 Aug 2017
All 17 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/yl2chen/cidranger
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
Questions
About github.com/yl2chen/cidranger
Is github.com/yl2chen/cidranger safe to use?
Vulert has no vulnerabilities on record for github.com/yl2chen/cidranger 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/yl2chen/cidranger's Vulert package health score?
Vulert scores github.com/yl2chen/cidranger 55/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/yl2chen/cidranger affected?
No. v1.0.2, 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/yl2chen/cidranger should I use?
v1.0.2 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/yl2chen/cidranger have?
0 vulnerabilities are recorded for github.com/yl2chen/cidranger 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/yl2chen/cidranger vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/yl2chen/cidranger 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/yl2chen/cidranger 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/yl2chen/cidranger for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/yl2chen/cidranger version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.