Vulnerability Database · Go · Package report
github.com/knadh/koanf/providers/confmap: vulnerability history, versions and safety
github.com/knadh/koanf/providers/confmap 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.
See all github.com/knadh/koanf/providers/confmap vulnerabilities
Vulert verdict on github.com/knadh/koanf/providers/confmap v1.0.1 i
Updated on 23 Oct 2026
Good news: v1.0.1, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Sustainable
- Popularity Key ecosystem project
- Community Quiet
What to do: Stay on v1.0.1 or newer. This can change: a vulnerability disclosed tomorrow can affect v1.0.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v1.0.1 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 4,219 i
- OpenSSF scorecard 3/10 i
- Last release 2 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/knadh/koanf/providers/confmap, 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.
- v1.0.2-0.20261018063300-05e9d6b18307 18 Oct 2026
- v1.0.2-0.20261006055353-05a17ccff92f 06 Oct 2026
- v1.0.2-0.20260809180615-6ad56fee6a6b 09 Aug 2026
- v1.0.1 04 Aug 2026
- v1.0.1-0.20260708060242-31dd449122a1 08 Jul 2026
- v0.0.0-20260530172714-e09e4c87a068 30 May 2026
- v0.1.1-0.20260530172714-e09e4c87a068 30 May 2026
- v1.0.1-0.20260530172714-e09e4c87a068 30 May 2026
- v1.0.1-0.20251029173414-8818413a8bea 29 Oct 2025
- v1.0.1-0.20250831075656-cc80f4f873cd 31 Aug 2025
- v1.0.1-0.20250825170610-10448713406b 25 Aug 2025
- v1.0.1-0.20250801122439-d66cde5a8f91 01 Aug 2025
- v1.0.1-0.20250712164456-fc52a4f243ef 12 Jul 2025
- v1.0.1-0.20250421050809-de8b5dfc5667 21 Apr 2025
- v1.0.1-0.20250419182056-d183bdbca10c 19 Apr 2025
- v1.0.1-0.20250416092136-081e8b1228ce 16 Apr 2025
- v1.0.1-0.20250415105417-8a93024ce5e2 15 Apr 2025
- v1.0.0 15 Apr 2025
- v0.1.1-0.20250101080848-4a21f9b42785 01 Jan 2025
- v0.1.1-0.20241118123929-b7b57e2534bd 18 Nov 2024
- v0.1.1-0.20241106084820-f13d85e17c00 06 Nov 2024
- v0.1.1-0.20240829081007-ec1d17c8f97e 29 Aug 2024
- v0.1.1-0.20240701115533-5939c3903214 01 Jul 2024
- v0.1.1-0.20240507052311-54f7500258d9 07 May 2024
- v0.1.1-0.20240307094742-7addd6f13ee2 07 Mar 2024
- v0.1.1-0.20240206095648-6c6c498fb49b 06 Feb 2024
- v0.1.1-0.20240110174456-1d7909b70777 10 Jan 2024
- v0.1.1-0.20231117060048-5bf8db177398 17 Nov 2023
- v0.1.1-0.20231101053848-ebcaa5155f9f 01 Nov 2023
- v0.1.0 17 Feb 2023
- v0.0.0-20230209101954-51bb07050fa4 09 Feb 2023
- v0.1.0-dev0 09 Feb 2023
All 32 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/knadh/koanf/providers/confmap
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/knadh/koanf/providers/confmap
Is github.com/knadh/koanf/providers/confmap safe to use?
Vulert has no vulnerabilities on record for github.com/knadh/koanf/providers/confmap 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/knadh/koanf/providers/confmap's Vulert package health score?
Vulert scores github.com/knadh/koanf/providers/confmap 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/knadh/koanf/providers/confmap affected?
No. v1.0.1, 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/knadh/koanf/providers/confmap should I use?
v1.0.1 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/knadh/koanf/providers/confmap have?
0 vulnerabilities are recorded for github.com/knadh/koanf/providers/confmap 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/knadh/koanf/providers/confmap vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/knadh/koanf/providers/confmap 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/knadh/koanf/providers/confmap 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/knadh/koanf/providers/confmap for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/knadh/koanf/providers/confmap version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.