Vulnerability Database · Go · Package report
github.com/invopop/yaml: vulnerability history, versions and safety
github.com/invopop/yaml 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/invopop/yaml v0.3.1 i
Updated on 23 Oct 2026
Good news: v0.3.1, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Slowing
- Popularity Little adoption
- Community Inactive
What to do: Stay on v0.3.1 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.3.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.3.1 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 30 i
- OpenSSF scorecard 2/10 i
- Last release 30 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/invopop/yaml, 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.3.1 08 Apr 2024
- v0.3.1-0.20240408073906-57832ada4901 08 Apr 2024
- v0.3.0 08 Apr 2024
- v0.2.1-0.20230906162838-c20b81e8359f 06 Sep 2023
- v0.1.1-0.20220607220729-16b11cef0cfe 07 Jun 2022
- v0.2.0 07 Jun 2022
- v0.1.1-0.20220607214733-d474586d3417 07 Jun 2022
- v0.1.0 26 May 2022
- v0.1.0-beta.1.0.20220526175707-fcdfe43df339 26 May 2022
- v0.1.0-beta.2 26 May 2022
- v0.0.0-20220526161948-81f56934acba 26 May 2022
- v0.1.0-beta.1 26 May 2022
- v0.0.0-20220526160708-6b9e6a315272 26 May 2022
- v0.0.0-20220526124315-d991967b1bc0 26 May 2022
- v0.0.0-20220526124205-6ea89bbbe565 26 May 2022
- v0.0.0-20220526122359-538dab4adb5d 26 May 2022
- v0.0.0-20190206175653-d4115522f0fe 06 Feb 2019
- v0.0.0-20190201151733-5f9473ed4b90 01 Feb 2019
- v0.0.0-20190201101102-308cf166d268 01 Feb 2019
- v0.0.0-20180929183019-ba6ab5399d77 29 Sep 2018
- v0.0.0-20180820084758-c7ce16629ff4 20 Aug 2018
- v0.0.0-20180816174003-f5bccc04aa10 16 Aug 2018
- v0.0.0-20180503022059-e9ed3c6dfb39 03 May 2018
- v0.0.0-20180409062154-8aa042675dd6 09 Apr 2018
- v0.0.0-20170506092452-17e4fbe4c179 06 May 2017
- v0.0.0-20170327235444-0ca9ea5df545 27 Mar 2017
- v0.0.0-20170317033929-a4f8cbd2fd05 17 Mar 2017
- v0.0.0-20161207003320-04f313413ffd 07 Dec 2016
- v0.0.0-20161123022414-a54de18a0704 23 Nov 2016
- v0.0.0-20161020132952-b99c3b0f4de8 20 Oct 2016
- v0.0.0-20160603165239-2920f90c58f0 03 Jun 2016
- v0.0.0-20160503134653-a08de6fb0513 03 May 2016
- v0.0.0-20160307215205-1a6f06984155 07 Mar 2016
- v0.0.0-20151229033501-1fb2dc496920 29 Dec 2015
- v0.0.0-20151215054338-6b3727e29774 15 Dec 2015
- v0.0.0-20150928145621-e5cf5ca324f1 28 Sep 2015
- v0.0.0-20150909031657-73d445a93680 09 Sep 2015
- v0.0.0-20150328012544-c3eb24aeea63 28 Mar 2015
- v0.0.0-20150113222549-3bc1590d1607 13 Jan 2015
- v0.0.0-20141210015752-4fb5c728a37b 10 Dec 2014
- v0.0.0-20141201060212-a4ad25344bbd 01 Dec 2014
All 41 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/invopop/yaml
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/invopop/yaml
Is github.com/invopop/yaml safe to use?
Vulert has no vulnerabilities on record for github.com/invopop/yaml 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/invopop/yaml's Vulert package health score?
Vulert scores github.com/invopop/yaml 50/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/invopop/yaml affected?
No. v0.3.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/invopop/yaml should I use?
v0.3.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/invopop/yaml have?
0 vulnerabilities are recorded for github.com/invopop/yaml 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/invopop/yaml vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/invopop/yaml 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/invopop/yaml 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/invopop/yaml for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/invopop/yaml version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.