Vulnerability Database · Go · Package report
github.com/multiformats/go-multiaddr-fmt: vulnerability history, versions and safety
github.com/multiformats/go-multiaddr-fmt 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.
See all github.com/multiformats/go-multiaddr-fmt vulnerabilities
Vulert verdict on github.com/multiformats/go-multiaddr-fmt v0.1.0 i
Updated on 23 Oct 2026
Good news: v0.1.0, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Unmaintained
- Popularity Little adoption
- Community Inactive
What to do: Stay on v0.1.0 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.1.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.1.0 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 6 i
- OpenSSF scorecard 2/10 i
- Last release 85 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/multiformats/go-multiaddr-fmt, 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-0.20260222154706-45a463e2f4fc 22 Feb 2026
- v0.1.1-0.20250821073151-feb320402e23 21 Aug 2025
- v0.1.1-0.20250328130631-575e9ff5f516 28 Mar 2025
- v0.1.1-0.20250216200138-cec4c42dc6f8 16 Feb 2025
- v0.1.1-0.20240826102642-6e713d075822 26 Aug 2024
- v0.1.1-0.20240322071710-e8bb7518c2c6 22 Mar 2024
- v0.1.1-0.20240317044316-238036a861f0 17 Mar 2024
- v0.1.1-0.20240314112554-e8647c61b361 14 Mar 2024
- v0.1.1-0.20230814133614-1457e13eefe9 14 Aug 2023
- v0.1.1-0.20230814062021-ec6324f5343e 14 Aug 2023
- v0.1.1-0.20230208151124-dcb8b40e1bb4 08 Feb 2023
- v0.1.1-0.20221116033724-67a6360719c6 16 Nov 2022
- v0.1.1-0.20220823161852-e7121444d93e 23 Aug 2022
- v0.1.1-0.20220404162916-5c00ae249392 04 Apr 2022
- v0.1.1-0.20211210143258-bf10b009a5f1 10 Dec 2021
- v0.1.1-0.20210817134340-27ca9c197f45 17 Aug 2021
- v0.1.1-0.20210601170115-3fa7c01e3b3b 01 Jun 2021
- v0.1.1-0.20210520194523-b185ff62a1fa 20 May 2021
- v0.1.1-0.20200403051113-09029a4b39dd 03 Apr 2020
- v0.0.0-20190919013545-113ed87ed03c 19 Sep 2019
- v0.1.0 19 Sep 2019
- v0.0.0-20190401213333-7d8102a98552 01 Apr 2019
- v0.0.1 01 Apr 2019
- v0.0.0-20181024170628-3b86bcbec8cb 24 Oct 2018
- v0.0.0-20181024164435-7aa7fad2ede4 24 Oct 2018
- v0.0.0-20180626232321-1a649ab46728 26 Jun 2018
- v0.0.0-20180609032312-92400d2b7006 09 Jun 2018
- v0.0.0-20180120182116-ab6a47300c1d 20 Jan 2018
- v0.0.0-20180120045108-f3af1767b1d5 20 Jan 2018
- v0.0.0-20171204234110-75e85e871bd7 04 Dec 2017
- v0.0.0-20171204043704-eb83a9b122d2 04 Dec 2017
- v0.0.0-20170711173933-8eaabeb0013f 11 Jul 2017
- v0.0.0-20170324014733-15300f9d3a2d 24 Mar 2017
- v0.0.0-20170319001608-1f80f6f6bc1c 19 Mar 2017
- v0.0.0-20170319001137-dad8a900d383 19 Mar 2017
- v0.0.0-20170202044019-f052f16d5bc5 02 Feb 2017
- v0.0.0-20170202044017-765480a29c5d 02 Feb 2017
- v0.0.0-20161005001737-a3d8d9c3218b 05 Oct 2016
- v0.0.0-20160510184450-8f444fbd67b3 10 May 2016
- v0.0.0-20160419223439-be76be8a6d4c 19 Apr 2016
- v0.0.0-20160419223405-b66d7ec57de1 19 Apr 2016
- v0.0.0-20160412041245-28a00a35effd 12 Apr 2016
- v0.0.0-20160118113946-61db816b9963 18 Jan 2016
All 43 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/multiformats/go-multiaddr-fmt
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/multiformats/go-multiaddr-fmt
Is github.com/multiformats/go-multiaddr-fmt safe to use?
Vulert has no vulnerabilities on record for github.com/multiformats/go-multiaddr-fmt 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/multiformats/go-multiaddr-fmt's Vulert package health score?
Vulert scores github.com/multiformats/go-multiaddr-fmt 44/100, which reads as risky. 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/multiformats/go-multiaddr-fmt affected?
No. v0.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/multiformats/go-multiaddr-fmt should I use?
v0.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/multiformats/go-multiaddr-fmt have?
0 vulnerabilities are recorded for github.com/multiformats/go-multiaddr-fmt 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/multiformats/go-multiaddr-fmt vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/multiformats/go-multiaddr-fmt 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/multiformats/go-multiaddr-fmt 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/multiformats/go-multiaddr-fmt for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/multiformats/go-multiaddr-fmt version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.