Vulnerability Database · Go · Package report
github.com/ipfs/go-ipfs-keystore: vulnerability history, versions and safety
github.com/ipfs/go-ipfs-keystore 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/ipfs/go-ipfs-keystore 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 Minor issues
- Maintenance Slowing
- 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 13 i
- OpenSSF scorecard 3/10 i
- Last release 40 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/ipfs/go-ipfs-keystore, 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-20230614111422-61ccc02181e4 14 Jun 2023
- v0.1.2-0.20230614111422-61ccc02181e4 14 Jun 2023
- v0.1.1 25 May 2023
- v0.1.0 09 Dec 2022
- v0.0.3-0.20221120211101-3b22462bc06a 20 Nov 2022
- v0.0.3-0.20220901100125-1dd9da250975 01 Sep 2022
- v0.0.3-0.20220406123743-7f18d9e559f8 06 Apr 2022
- v0.0.3-0.20211117132721-f5dede7af813 17 Nov 2021
- v0.0.3-0.20210616005322-867da36b33e7 16 Jun 2021
- v0.0.3-0.20210219170209-57e438e43d66 19 Feb 2021
- v0.0.3-0.20210218232841-26d3af14055c 18 Feb 2021
- v0.0.2 18 Feb 2021
- v0.0.0-20190329115745-104cf5bfc98d 29 Mar 2019
- v0.0.0-20190302171157-4802a8a5ff7f 02 Mar 2019
- v0.0.1 02 Mar 2019
- v0.0.0-20181204233654-a15b666ef5e9 04 Dec 2018
- v0.0.0-20181103041720-33935f4f62f6 03 Nov 2018
- v0.0.0-20180828214510-508c1e100900 28 Aug 2018
- v0.0.0-20180801054948-7e06c40863e0 01 Aug 2018
- v0.0.0-20180627001133-95a5cd3ebde8 27 Jun 2018
- v0.0.0-20180330074327-47fd52f3015f 30 Mar 2018
All 21 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/ipfs/go-ipfs-keystore
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/ipfs/go-ipfs-keystore
Is github.com/ipfs/go-ipfs-keystore safe to use?
Vulert has no vulnerabilities on record for github.com/ipfs/go-ipfs-keystore 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/ipfs/go-ipfs-keystore's Vulert package health score?
Vulert scores github.com/ipfs/go-ipfs-keystore 52/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/ipfs/go-ipfs-keystore 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/ipfs/go-ipfs-keystore 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/ipfs/go-ipfs-keystore have?
0 vulnerabilities are recorded for github.com/ipfs/go-ipfs-keystore 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/ipfs/go-ipfs-keystore vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/ipfs/go-ipfs-keystore 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/ipfs/go-ipfs-keystore 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/ipfs/go-ipfs-keystore for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/ipfs/go-ipfs-keystore version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.