Vulnerability Database · Go · Package report

github.com/ipfs/go-ipfs-exchange-interface: vulnerability history, versions and safety

github.com/ipfs/go-ipfs-exchange-interface is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the Go ecosystem.

i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on github.com/ipfs/go-ipfs-exchange-interface v0.2.1 i

Updated on 23 Oct 2026

Good news: v0.2.1, the version you would install today, has no known vulnerabilities.

Package health score 52/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Little adoption
  • Community Inactive

What to do: Stay on v0.2.1 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.2.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release v0.2.1 — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 9 i
  • OpenSSF scorecard 3/10 i
  • Last release 41 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/ipfs/go-ipfs-exchange-interface, 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.

i
Version Released Vulert vulnerabilities Licence Fix published Details
v0.2.2-0.20230614111411-8e6c4f0736f3 14 Jun 2023 none MIT — Details →
v0.2.1 23 May 2023 none MIT — Details →
v0.2.1-0.20230208150215-e5d1ab4d5956 08 Feb 2023 none MIT — Details →
v0.2.1-0.20220823165145-27f6dcaa37c2 23 Aug 2022 none MIT — Details →
v0.2.1-0.20220805175521-7604dcd563e1 05 Aug 2022 none MIT — Details →
v0.2.0 27 Jul 2022 none MIT — Details →
v0.1.1-0.20220721095523-16d8b99a4321 21 Jul 2022 none MIT — Details →
v0.0.2-0.20220713142804-1181846dc171 13 Jul 2022 none MIT — Details →
v0.1.1-0.20220627104606-da62575dc2f1 27 Jun 2022 none MIT — Details →
v0.1.1-0.20220613125036-b719fe0bd52f 13 Jun 2022 none MIT — Details →
v0.1.1-0.20220404162859-8c4da7eab594 04 Apr 2022 none MIT — Details →
v0.1.1-0.20211210142015-c4d743c61765 10 Dec 2021 none MIT — Details →
v0.1.0 29 Oct 2021 none MIT — Details →
v0.0.2-0.20211029111511-6e2392165d65 29 Oct 2021 none MIT — Details →
v0.0.2-0.20211028142157-09692a6b268b 28 Oct 2021 none MIT — Details →
v0.0.2-0.20211014020636-09b81e768d27 14 Oct 2021 none MIT — Details →
v0.0.0-20210817145420-877d0e0b9117 17 Aug 2021 none MIT — Details →
v0.0.2-0.20210817145420-877d0e0b9117 17 Aug 2021 none MIT — Details →
v0.0.2-0.20210601174418-5b5b20de27b3 01 Jun 2021 none MIT — Details →
v0.0.2-0.20210423112629-fe9d20f99b6b 23 Apr 2021 none MIT — Details →
v0.0.0-20200504101317-90f3c93befbf 04 May 2020 none MIT — Details →
v0.0.2-0.20200504101317-90f3c93befbf 04 May 2020 none MIT — Details →
v0.0.2-0.20200423055703-2e8ddd22ab43 23 Apr 2020 none MIT — Details →
v0.0.2-0.20200423051052-ccb5de3a8346 23 Apr 2020 none MIT — Details →
v0.0.2-0.20200423025342-0a603647b40e 23 Apr 2020 none MIT — Details →
v0.0.2-0.20200211182839-a30d3ce7a91e 11 Feb 2020 none MIT — Details →
v0.0.0-20191220150722-7fc9151f685a 20 Dec 2019 none MIT — Details →
v0.0.0-20190924231634-3f798b753b4c 24 Sep 2019 none MIT — Details →
v0.0.0-20190919051742-aab2e33aa212 19 Sep 2019 none MIT — Details →
v0.0.0-20190302181529-8f85ecf2ed19 02 Mar 2019 none MIT — Details →
v0.0.2-0.20190302181529-8f85ecf2ed19 02 Mar 2019 none MIT — Details →
v0.0.0-20190302171052-b6e882607724 02 Mar 2019 none MIT — Details →
v0.0.1 02 Mar 2019 none MIT — Details →
v0.0.0-20190221041640-969e1b68e192 21 Feb 2019 none MIT — Details →
v0.0.0-20181102235302-9ba3cfba8a23 02 Nov 2018 none MIT — Details →
v0.0.0-20180919213516-615ac03eb55d 19 Sep 2018 none MIT — Details →
v0.0.0-20180911234836-a84aed89e778 11 Sep 2018 none MIT — Details →
v0.0.0-20180822000945-d3f680651104 22 Aug 2018 none MIT — Details →
v0.0.0-20180815152720-3a2a0aeada09 15 Aug 2018 none MIT — Details →
v0.0.0-20180811010459-667c0cfcd4c0 11 Aug 2018 none MIT — Details →
v0.0.0-20180712082735-535c7a3c9465 12 Jul 2018 none MIT — Details →
v0.0.0-20180609032838-62d74ecd98f0 09 Jun 2018 none MIT — Details →
v0.0.0-20180403123328-c54770addb01 03 Apr 2018 none MIT — Details →
v0.0.0-20180124235844-51df926aeeeb 24 Jan 2018 none — — Details →

All 44 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-exchange-interface

No vulnerability write-ups match this view

Search all 0 in the database →

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

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About github.com/ipfs/go-ipfs-exchange-interface

Is github.com/ipfs/go-ipfs-exchange-interface safe to use?

Vulert has no vulnerabilities on record for github.com/ipfs/go-ipfs-exchange-interface 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-exchange-interface's Vulert package health score?

Vulert scores github.com/ipfs/go-ipfs-exchange-interface 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-exchange-interface affected?

No. v0.2.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-exchange-interface should I use?

v0.2.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-exchange-interface have?

0 vulnerabilities are recorded for github.com/ipfs/go-ipfs-exchange-interface 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-exchange-interface vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/ipfs/go-ipfs-exchange-interface 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-exchange-interface 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-exchange-interface 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-exchange-interface version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.