Vulnerability Database · Go · Package report
github.com/r3labs/diff: vulnerability history, versions and safety
github.com/r3labs/diff 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/r3labs/diff v1.1.0 i
Updated on 23 Oct 2026
Good news: v1.1.0, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Unmaintained
- Popularity Widely used
- Community Quiet
What to do: Stay on v1.1.0 or newer. This can change: a vulnerability disclosed tomorrow can affect v1.1.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v1.1.0 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 981 i
- OpenSSF scorecard 2/10 i
- Last release 78 months ago i
- Licence MPL-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/r3labs/diff, 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-20201223155434-f54a0724e0a9 23 Dec 2020
- v1.1.1-0.20201223155434-f54a0724e0a9 23 Dec 2020
- v1.1.1-0.20201223122209-8d3cdfb727df 23 Dec 2020
- v1.1.1-0.20201019125002-d02c561d30fc 19 Oct 2020
- v1.1.1-0.20201019122428-110495df9638 19 Oct 2020
- v1.1.1-0.20201018215023-2fd0db941040 18 Oct 2020
- v1.1.1-0.20201018102724-87893d1927ab 18 Oct 2020
- v1.1.1-0.20201014202241-98c4992c432f 14 Oct 2020
- v1.1.1-0.20201014171810-1a39d9515358 14 Oct 2020
- v1.1.1-0.20200906151117-f39865c6bb0f 06 Sep 2020
- v0.0.0-20200820185415-03fadb475039 20 Aug 2020
- v1.1.1-0.20200820185415-03fadb475039 20 Aug 2020
- v0.0.0-20200819114611-484340b7972a 19 Aug 2020
- v1.1.1-0.20200819114611-484340b7972a 19 Aug 2020
- v0.0.0-20200719203008-5e75fbf0cd13 19 Jul 2020
- v1.1.1-0.20200719203008-5e75fbf0cd13 19 Jul 2020
- v1.1.1-0.20200719004510-f3d34884da4d 19 Jul 2020
- v1.1.1-0.20200716194542-c1941adb8ae8 16 Jul 2020
- v1.1.1-0.20200716193914-1b547005f918 16 Jul 2020
- v0.0.0-20200627101315-aecd9dd05dd2 27 Jun 2020
- v1.1.1-0.20200627101315-aecd9dd05dd2 27 Jun 2020
- v1.1.1-0.20200627101150-406746115cb7 27 Jun 2020
- v0.0.0-20200602081335-2448fc76135e 02 Jun 2020
- v1.1.1-0.20200602081335-2448fc76135e 02 Jun 2020
- v1.1.1-0.20200601142914-c09284b20b46 01 Jun 2020
- v0.0.0-20200601085409-6aab0e34361d 01 Jun 2020
- v1.1.1-0.20200601085409-6aab0e34361d 01 Jun 2020
- v1.0.2-0.20200430024035-8808485bb5b6 30 Apr 2020
- v0.0.0-20200418184821-14cbc684e8ca 18 Apr 2020
- v1.1.0 18 Apr 2020
- v1.0.2-0.20200418183431-f5748c02adbd 18 Apr 2020
- v1.0.2-0.20200418145320-e3d3ed6fbf7b 18 Apr 2020
- v1.0.1 07 Apr 2020
- v1.0.0 03 Apr 2020
- v0.0.0-20200317213837-7cb6232bcd79 17 Mar 2020
- v0.0.0-20191120142937-b4ed99a31f5a 20 Nov 2019
- v0.0.0-20191018104334-e3ae93f4edbb 18 Oct 2019
- v0.0.0-20190801153147-a71de73c46ad 01 Aug 2019
- v0.0.0-20190801111014-fff8c73fe1ac 01 Aug 2019
- v0.0.0-20190704173634-3658fe4f00f3 04 Jul 2019
- v0.0.0-20190618142250-fbe9de54bde7 18 Jun 2019
- v0.0.0-20190605140807-2d903a3e02e0 05 Jun 2019
- v0.0.0-20190423094808-10f39a916ff7 23 Apr 2019
- v0.0.0-20190408153613-004a429b1a9e 08 Apr 2019
- v0.0.0-20190117134156-85e103916027 17 Jan 2019
- v0.0.0-20181205174125-8b99cd0474d0 05 Dec 2018
- v0.0.0-20181022122403-f5177d8efc30 22 Oct 2018
- v0.0.0-20180924105150-6a8c93502ec3 24 Sep 2018
- v0.0.0-20180118113307-94f6e3434299 18 Jan 2018
All 49 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/r3labs/diff
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/r3labs/diff
Is github.com/r3labs/diff safe to use?
Vulert has no vulnerabilities on record for github.com/r3labs/diff 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/r3labs/diff's Vulert package health score?
Vulert scores github.com/r3labs/diff 55/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/r3labs/diff affected?
No. v1.1.0, 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/r3labs/diff should I use?
v1.1.0 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/r3labs/diff have?
0 vulnerabilities are recorded for github.com/r3labs/diff 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/r3labs/diff vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/r3labs/diff 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/r3labs/diff 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/r3labs/diff for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/r3labs/diff version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.