Vulnerability Database · Go · Package report
github.com/caarlos0/env: vulnerability history, versions and safety
github.com/caarlos0/env 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/caarlos0/env v3.5.0+incompatible i
Updated on 23 Oct 2026
Good news: v3.5.0+incompatible, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Unmaintained
- Popularity Key ecosystem project
- Community Moderate
What to do: Stay on v3.5.0+incompatible or newer. This can change: a vulnerability disclosed tomorrow can affect v3.5.0+incompatible too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v3.5.0+incompatible — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 6,340 i
- OpenSSF scorecard 5/10 i
- Last release 96 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/caarlos0/env, 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-20190429120135-cdbb914ad684 29 Apr 2019
- v0.0.0-20190425105323-0abd7ea7648a 25 Apr 2019
- v0.0.0-20190425104329-eaa3c660a3b4 25 Apr 2019
- v0.0.0-20190422171146-ccc4466e2e82 22 Apr 2019
- v0.0.0-20190317132158-240f8632d3d1 17 Mar 2019
- v0.0.0-20190310005739-80af6745ae2d 10 Mar 2019
- v0.0.0-20190308142353-9a320ffe30f7 08 Mar 2019
- v0.0.0-20181024121956-515df9e9ee27 24 Oct 2018
- v3.5.1-0.20181024121956-515df9e9ee27+incompatible 24 Oct 2018
- v0.0.0-20181020014622-518fcfb94325 20 Oct 2018
- v3.5.0+incompatible 20 Oct 2018
- v3.4.0+incompatible 19 Sep 2018
- v0.0.0-20180702195640-bc122c26dc2d 02 Jul 2018
- v3.3.1-0.20180702195640-bc122c26dc2d+incompatible 02 Jul 2018
- v0.0.0-20180521112546-3e0f30cbf50b 21 May 2018
- v3.3.1-0.20180521112546-3e0f30cbf50b+incompatible 21 May 2018
- v3.3.0+incompatible 01 May 2018
- v0.0.0-20180316125529-9b2b3076ca0c 16 Mar 2018
- v3.2.1-0.20180316125529-9b2b3076ca0c+incompatible 16 Mar 2018
- v3.2.1-0.20171220171456-1696c10618d3+incompatible 20 Dec 2017
- v3.2.1-0.20171220170655-480053bfe5bc+incompatible 20 Dec 2017
- v3.2.1-0.20171220165817-abbc6360f72c+incompatible 20 Dec 2017
- v3.2.1-0.20171220165217-f3cbaa5ef778+incompatible 20 Dec 2017
- v3.2.1-0.20171220163616-2b8bd173dcd7+incompatible 20 Dec 2017
- v3.2.1-0.20171220163417-dbbebc487501+incompatible 20 Dec 2017
- v0.0.0-20171213100219-7cd7992b3bc8 13 Dec 2017
- v3.2.0+incompatible 13 Dec 2017
- v3.1.2-0.20171213065314-161b6fb40327+incompatible 13 Dec 2017
- v3.1.2-0.20171211053208-fca070c8fa18+incompatible 11 Dec 2017
- v3.1.2-0.20171211051234-558d449280f3+incompatible 11 Dec 2017
- v3.1.2-0.20171201112155-2eb62c9a3111+incompatible 01 Dec 2017
- v3.1.2-0.20171201110440-887ea123c0b8+incompatible 01 Dec 2017
- v3.1.1+incompatible 30 Oct 2017
- v0.0.0-20171030192619-cb3993aef19f 30 Oct 2017
- v0.0.0-20171025202010-d29d8d23e95a 25 Oct 2017
- v0.0.0-20170615153731-0cf029d5748c 15 Jun 2017
- v0.0.0-20170430215205-7110c4e2f569 30 Apr 2017
- v0.0.0-20170203211707-9474f19b515f 03 Feb 2017
- v0.0.0-20161013201842-d0de832ed2fb 13 Oct 2016
- v0.0.0-20160706172553-8030fe5519ec 06 Jul 2016
- v0.0.0-20160415155319-636ad281b72c 15 Apr 2016
- v0.0.0-20160118112052-65331f179c42 18 Jan 2016
- v0.0.0-20160118000015-b2d60175526f 18 Jan 2016
- v0.0.0-20150804134327-1e5b9d9d2f22 04 Aug 2015
All 44 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/caarlos0/env
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/caarlos0/env
Is github.com/caarlos0/env safe to use?
Vulert has no vulnerabilities on record for github.com/caarlos0/env 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/caarlos0/env's Vulert package health score?
Vulert scores github.com/caarlos0/env 65/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/caarlos0/env affected?
No. v3.5.0+incompatible, 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/caarlos0/env should I use?
v3.5.0+incompatible 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/caarlos0/env have?
0 vulnerabilities are recorded for github.com/caarlos0/env 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/caarlos0/env vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/caarlos0/env 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/caarlos0/env 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/caarlos0/env for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/caarlos0/env version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.