Vulnerability Database · Go · Package report
github.com/cloudfoundry/noaa: vulnerability history, versions and safety
github.com/cloudfoundry/noaa 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/cloudfoundry/noaa v2.1.0+incompatible i
Updated on 23 Oct 2026
Good news: v2.1.0+incompatible, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Unmaintained
- Popularity Little adoption
- Community Quiet
What to do: Stay on v2.1.0+incompatible or newer. This can change: a vulnerability disclosed tomorrow can affect v2.1.0+incompatible too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v2.1.0+incompatible — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 23 i
- OpenSSF scorecard 3/10 i
- Last release 112 months ago i
- Licence Apache-2.0 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/cloudfoundry/noaa, 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-20220729172553-0ea1a327751e 29 Jul 2022
- v0.0.0-20220729172017-74832b3a3f13 29 Jul 2022
- v0.0.0-20220729170757-6fdf6e6d717d 29 Jul 2022
- v2.1.1-0.20220601183050-c6a7713cf5f9+incompatible 01 Jun 2022
- v0.0.0-20211215183044-35b16831d452 15 Dec 2021
- v2.1.1-0.20211215183044-35b16831d452+incompatible 15 Dec 2021
- v0.0.0-20211215161705-2c16a3c08a20 15 Dec 2021
- v0.0.0-20190110210640-5ce49363dfa6 10 Jan 2019
- v2.1.1-0.20190110210640-5ce49363dfa6+incompatible 10 Jan 2019
- v0.0.0-20180126195231-5beab4261046 26 Jan 2018
- v2.1.1-0.20180126195231-5beab4261046+incompatible 26 Jan 2018
- v0.0.0-20171030182453-9d59e2b25abb 30 Oct 2017
- v2.1.1-0.20171030182453-9d59e2b25abb+incompatible 30 Oct 2017
- v0.0.0-20170830200006-7704643fe84d 30 Aug 2017
- v2.1.1-0.20170830200006-7704643fe84d+incompatible 30 Aug 2017
- v0.0.0-20170612155045-a1d4a94e2be6 12 Jun 2017
- v2.1.0+incompatible 12 Jun 2017
- v0.0.0-20170526203936-ea8759ba3628 26 May 2017
- v2.0.1-0.20170526203936-ea8759ba3628+incompatible 26 May 2017
- v2.0.1-0.20170509041928-89f0843d0ab5+incompatible 09 May 2017
- v0.0.0-20170403205344-dd6ec6bd0a01 03 Apr 2017
- v2.0.1-0.20170403205344-dd6ec6bd0a01+incompatible 03 Apr 2017
- v0.0.0-20170301204500-a658db22c62e 01 Mar 2017
- v2.0.1-0.20170301204500-a658db22c62e+incompatible 01 Mar 2017
- v0.0.0-20170131060151-9e087230f2fe 31 Jan 2017
- v2.0.1-0.20170131060151-9e087230f2fe+incompatible 31 Jan 2017
- v0.0.0-20170113180124-5a1ef880e4cc 13 Jan 2017
- v2.0.1-0.20170113180124-5a1ef880e4cc+incompatible 13 Jan 2017
- v2.0.0+incompatible 07 Dec 2016
- v0.0.0-20161116223510-1939b6e4d6d7 16 Nov 2016
- v0.0.0-20161010152720-b427932415f2 10 Oct 2016
- v0.0.0-20161006215546-c18e6928cef4 06 Oct 2016
- v0.0.0-20160908160702-80008a261d9c 08 Sep 2016
- v0.0.0-20160906200453-c2c343ac099f 06 Sep 2016
- v0.0.0-20160902053145-1ead9c9f094e 02 Sep 2016
- v0.0.0-20160723201743-0ca0d30d65c7 23 Jul 2016
- v0.0.0-20160630172011-a4c517a96b01 30 Jun 2016
- v0.0.0-20160607223449-75f17396a977 07 Jun 2016
- v0.0.0-20160503153424-8c9fd92c47a3 03 May 2016
- v0.0.0-20160501201943-d8bd17db3760 01 May 2016
- v0.0.0-20160408200720-ece624d29c30 08 Apr 2016
- v0.0.0-20160401204031-bb28530a73e4 01 Apr 2016
- v0.0.0-20160312184952-87a5a9673cf6 12 Mar 2016
- v0.0.0-20151112215522-d641e2005492 12 Nov 2015
- v0.0.0-20150902204103-26f4f663999e 02 Sep 2015
- v0.0.0-20150820203657-add844f5f6a6 20 Aug 2015
- v0.0.0-20150720190722-280497e4cd65 20 Jul 2015
- v0.0.0-20150618225033-7f3b03afe00e 18 Jun 2015
- v0.0.0-20150612170120-3c78d4555842 12 Jun 2015
- v0.0.0-20150605205340-f46a73b80ef8 05 Jun 2015
- v0.0.0-20150515173136-f8b6ee8f2667 15 May 2015
- v0.0.0-20150515172259-4f20c9fdf29b 15 May 2015
- v0.0.0-20150416171343-9e379db26bbd 16 Apr 2015
- v0.0.0-20150316210154-92d89517244c 16 Mar 2015
- v0.0.0-20150213235831-7ec5b0dce4f8 13 Feb 2015
All 55 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/cloudfoundry/noaa
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/cloudfoundry/noaa
Is github.com/cloudfoundry/noaa safe to use?
Vulert has no vulnerabilities on record for github.com/cloudfoundry/noaa 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/cloudfoundry/noaa's Vulert package health score?
Vulert scores github.com/cloudfoundry/noaa 47/100, which reads as risky. 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/cloudfoundry/noaa affected?
No. v2.1.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/cloudfoundry/noaa should I use?
v2.1.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/cloudfoundry/noaa have?
0 vulnerabilities are recorded for github.com/cloudfoundry/noaa 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/cloudfoundry/noaa vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/cloudfoundry/noaa 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/cloudfoundry/noaa 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/cloudfoundry/noaa for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/cloudfoundry/noaa version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.