Vulnerability Database · Go · Package report
github.com/oasdiff/yaml: vulnerability history, versions and safety
github.com/oasdiff/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/oasdiff/yaml v0.1.1 i
Updated on 23 Oct 2026
Good news: v0.1.1, the version you would install today, has no known vulnerabilities.
- Security No known security issues
- Maintenance Sustainable
- Popularity Little adoption
- Community Inactive
What to do: Stay on v0.1.1 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.1.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.1.1 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 1 i
- Last release 3 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/oasdiff/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.1.1 25 Jun 2026
- v0.1.0 12 May 2026
- v0.0.9 06 Apr 2026
- v0.0.8 05 Apr 2026
- v0.0.7 02 Apr 2026
- v0.0.6 02 Apr 2026
- v0.0.5-beta.1 31 Mar 2026
- v0.0.4 31 Mar 2026
- v0.0.3 30 Mar 2026
- v0.0.3-0.20260330192622-8721577fe530 30 Mar 2026
- v0.0.2 30 Mar 2026
- v0.0.0-20260316172607-c776e543fb77 16 Mar 2026
- v0.0.1 16 Mar 2026
- v0.0.0-20260316 16 Mar 2026
- v0.0.0-20260316170935-40d32a4ab404 16 Mar 2026
- v0.0.0-20260316160413-530022a25b2e 16 Mar 2026
- v0.0.0-20260313112342-a3ea61cb4d4c 13 Mar 2026
- v0.0.0-20260219140331-2c8a4d8a2666 19 Feb 2026
- v0.0.0-20260217201108-4f1c3d02ddd4 17 Feb 2026
- v0.0.0-20250309154309-f31be36b4037 09 Mar 2025
- v0.0.0-20241214135536-5f7845c759c8 14 Dec 2024
- v0.0.0-20241210131133-6b86fb107d80 10 Dec 2024
- v0.0.0-20241210131047-14880769d034 10 Dec 2024
- v0.0.0-20240818090434-54d3544f652c 18 Aug 2024
- v0.0.0-20240818085823-0840111ccb54 18 Aug 2024
- v0.0.0-20240818083818-05f5b8ffb4d5 18 Aug 2024
- v0.0.0-20240818073638-03633ab6ccde 18 Aug 2024
- v0.0.0-20240816155429-7de7a40360c5 16 Aug 2024
- v0.0.0-20190201101102-308cf166d268 01 Feb 2019
All 29 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/oasdiff/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/oasdiff/yaml
Is github.com/oasdiff/yaml safe to use?
Vulert has no vulnerabilities on record for github.com/oasdiff/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/oasdiff/yaml's Vulert package health score?
Vulert scores github.com/oasdiff/yaml 74/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/oasdiff/yaml affected?
No. v0.1.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/oasdiff/yaml should I use?
v0.1.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/oasdiff/yaml have?
0 vulnerabilities are recorded for github.com/oasdiff/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/oasdiff/yaml vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/oasdiff/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/oasdiff/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/oasdiff/yaml for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/oasdiff/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.