Vulnerability Database · Go · Package report
github.com/peterbourgon/diskv: vulnerability history, versions and safety
github.com/peterbourgon/diskv 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/peterbourgon/diskv v2.0.1+incompatible i
Updated on 23 Oct 2026
Good news: v2.0.1+incompatible, 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 v2.0.1+incompatible or newer. This can change: a vulnerability disclosed tomorrow can affect v2.0.1+incompatible too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v2.0.1+incompatible — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 1,458 i
- OpenSSF scorecard 2/10 i
- Last release 110 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/peterbourgon/diskv, 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-20180312054125-0646ccaebea1 12 Mar 2018
- v1.0.1-0.20180312054125-0646ccaebea1 12 Mar 2018
- v2.0.2-0.20180312054125-0646ccaebea1+incompatible 12 Mar 2018
- v0.0.0-20180307003307-ea7c67b6c85b 07 Mar 2018
- v2.0.2-0.20180307003307-ea7c67b6c85b+incompatible 07 Mar 2018
- v2.0.2-0.20180306213700-6ef93c4d298f+incompatible 06 Mar 2018
- v2.0.2-0.20180306213545-03c5bce8e8c3+incompatible 06 Mar 2018
- v2.0.2-0.20180306212602-48f14fa387bc+incompatible 06 Mar 2018
- v2.0.2-0.20180306165114-d36d2a24e0a5+incompatible 06 Mar 2018
- v0.0.0-20171120014656-2973218375c3 20 Nov 2017
- v1.0.1-0.20171120014656-2973218375c3 20 Nov 2017
- v2.0.2-0.20171120014656-2973218375c3+incompatible 20 Nov 2017
- v2.0.2-0.20171120004735-f97d4d4afa4a+incompatible 20 Nov 2017
- v0.0.0-20171025114034-53ef9e43a0bc 25 Oct 2017
- v2.0.2-0.20171025114034-53ef9e43a0bc+incompatible 25 Oct 2017
- v2.0.2-0.20171025024020-c295f7ac105d+incompatible 25 Oct 2017
- v0.0.0-20170814173558-5f041e8faa00 14 Aug 2017
- v1.0.1-0.20170814173558-5f041e8faa00 14 Aug 2017
- v2.0.1+incompatible 14 Aug 2017
- v2.0.1-0.20170814172900-40ecb11adeba+incompatible 14 Aug 2017
- v2.0.1-0.20170810204945-6226bdba888d+incompatible 10 Aug 2017
- v2.0.1-0.20170808154727-37d830f501c2+incompatible 08 Aug 2017
- v2.0.1-0.20170807205917-12dadeb8a280+incompatible 07 Aug 2017
- v0.0.0-20160404093648-5dfcb07a075a 04 Apr 2016
- v1.0.1-0.20160404093648-5dfcb07a075a 04 Apr 2016
- v2.0.1-0.20160404093648-5dfcb07a075a+incompatible 04 Apr 2016
- v2.0.1-0.20160401155539-f1d7d833cf8c+incompatible 01 Apr 2016
- v2.0.0+incompatible 30 Mar 2016
- v1.0.1-0.20160330210706-9605b456faaf 30 Mar 2016
- v1.0.0 13 Nov 2015
- v0.0.0-20150905192411-f726c97c7c2b 05 Sep 2015
- v0.0.0-20150421033610-0cf225ba947b 21 Apr 2015
- v0.0.0-20141231140851-72aa5da9f7d1 31 Dec 2014
- v0.0.0-20141230201951-aacbe665b4fd 30 Dec 2014
- v0.0.0-20141212230639-508f5671a72e 12 Dec 2014
- v0.0.0-20141211233842-0488445c740e 11 Dec 2014
- v0.0.0-20141211195217-129c9e4ad4cd 11 Dec 2014
- v0.0.0-20141209214215-1c1dd9875b3a 09 Dec 2014
- v0.0.0-20141208140826-531da2bc9b5e 08 Dec 2014
- v0.0.0-20141206102028-ccff65dc8ecb 06 Dec 2014
- v0.0.0-20140709161028-fbec614921b1 09 Jul 2014
- v0.0.0-20140707133509-15db82dfcd11 07 Jul 2014
- v0.0.0-20131120162855-76403dd2469f 20 Nov 2013
- v0.0.0-20130610094050-98e4a892fb32 10 Jun 2013
- v0.0.0-20130519211242-307640feeeaa 19 May 2013
- v0.0.0-20130313092028-643b99af8329 13 Mar 2013
- v0.0.0-20130304173518-b4041305b96e 04 Mar 2013
- v0.0.0-20130303084218-94f66c083bcd 03 Mar 2013
- v0.0.0-20130301123804-2c84b9d54efa 01 Mar 2013
- v0.0.0-20130227230406-440e4c615fdd 27 Feb 2013
- v0.0.0-20130227223154-e8bbf390fbf2 27 Feb 2013
- v0.0.0-20130213161338-05b6e84a2e32 13 Feb 2013
- v0.0.0-20121021134231-a444aaf1cdd0 21 Oct 2012
- v0.0.0-20121013174143-0e48d8c7be1b 13 Oct 2012
- v0.0.0-20120820094818-ad8411a1b82b 20 Aug 2012
- v0.0.0-20120711075115-2d47b1411a23 11 Jul 2012
- v0.0.0-20120628214001-75099cbc40ab 28 Jun 2012
- v0.0.0-20120401135008-0670abc20bdb 01 Apr 2012
- v0.0.0-20120321232957-192b0ac756cd 21 Mar 2012
All 59 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/peterbourgon/diskv
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/peterbourgon/diskv
Is github.com/peterbourgon/diskv safe to use?
Vulert has no vulnerabilities on record for github.com/peterbourgon/diskv 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/peterbourgon/diskv's Vulert package health score?
Vulert scores github.com/peterbourgon/diskv 57/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/peterbourgon/diskv affected?
No. v2.0.1+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/peterbourgon/diskv should I use?
v2.0.1+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/peterbourgon/diskv have?
0 vulnerabilities are recorded for github.com/peterbourgon/diskv 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/peterbourgon/diskv vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/peterbourgon/diskv 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/peterbourgon/diskv 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/peterbourgon/diskv for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/peterbourgon/diskv version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.