Vulnerability Database · Go · Package report
github.com/ipfs/go-fs-lock: vulnerability history, versions and safety
github.com/ipfs/go-fs-lock 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-fs-lock 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 Maintaining
- 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 4 i
- OpenSSF scorecard 3/10 i
- Last release 17 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-fs-lock, 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.2-0.20260222154757-ffc4c1e4ae10 22 Feb 2026
- v0.1.2-0.20250821073301-c9179a856faa 21 Aug 2025
- v0.1.2-0.20250815102807-1eed384e2187 15 Aug 2025
- v0.1.2-0.20250710220238-3b79972294da 10 Jul 2025
- v0.1.2-0.20250710215819-18a60ce31f59 10 Jul 2025
- v0.1.1 06 May 2025
- v0.1.0 02 May 2025
- v0.0.8-0.20250328130847-197dac0df066 28 Mar 2025
- v0.0.8-0.20250216200253-e711ad5c9fcb 16 Feb 2025
- v0.0.8-0.20240826102729-85b9fe25a6ac 26 Aug 2024
- v0.0.8-0.20240322071837-9f2b744511b0 22 Mar 2024
- v0.0.8-0.20240314112709-93f4acc92501 14 Mar 2024
- v0.0.8-0.20240131173403-813800df6001 31 Jan 2024
- v0.0.8-0.20230814133715-d715b68aea26 14 Aug 2023
- v0.0.8-0.20230814075316-9be6a087b104 14 Aug 2023
- v0.0.8-0.20230628085226-5879239d23f9 28 Jun 2023
- v0.0.8-0.20230614111636-b3f9f6940335 14 Jun 2023
- v0.0.8-0.20230302125750-d74081ae85b1 02 Mar 2023
- v0.0.8-0.20220721095640-67ecbd955c19 21 Jul 2022
- v0.0.8-0.20220627104814-8402f5b4b85b 27 Jun 2022
- v0.0.8-0.20211210145009-62106fd9a9f0 10 Dec 2021
- v0.0.8-0.20210817150739-45ea93f2c0ea 17 Aug 2021
- v0.0.7 21 Jul 2021
- v0.0.7-0.20210429202453-e4deb1530655 29 Apr 2021
- v0.0.7-0.20210125082851-589884c5a58c 25 Jan 2021
- v0.0.6 26 Jul 2020
- v0.0.6-0.20200726161253-c10b9068b241 26 Jul 2020
- v0.0.5 26 May 2020
- v0.0.5-0.20200504101138-3f12a5e96416 04 May 2020
- v0.0.5-0.20200210153231-47c2f18922b6 10 Feb 2020
- v0.0.4 16 Jan 2020
- v0.0.3 14 Oct 2019
- v0.0.2 13 Oct 2019
- v0.0.0-20190710120703-5ab4a142bd90 10 Jul 2019
- v0.0.0-20190302173853-8eef3eacd4ce 02 Mar 2019
- v0.0.2-0.20190302173853-8eef3eacd4ce 02 Mar 2019
- v0.0.1 02 Mar 2019
- v0.0.0-20190218152535-18b750cab122 18 Feb 2019
- v0.0.0-20181218225445-65a5116e54cf 18 Dec 2018
- v0.0.0-20181102235300-daf41f275111 02 Nov 2018
- v0.0.0-20180924121153-2984d231a4e4 24 Sep 2018
- v0.0.0-20180809015104-3b1925c1904c 09 Aug 2018
- v0.0.0-20180626002419-3c98465668f6 26 Jun 2018
- v0.0.0-20180609053217-c4dcaad54f16 09 Jun 2018
- v0.0.0-20180609032836-cdc0fe9433ba 09 Jun 2018
- v0.0.0-20180504042045-0df4d3da5d58 04 May 2018
- v0.0.0-20180329184429-e2feeb3bc32c 29 Mar 2018
- v0.0.0-20180313173931-b0fe4e4032be 13 Mar 2018
- v0.0.0-20180206212847-42e4adcd1f01 06 Feb 2018
- v0.0.0-20180131181507-af989a9cc799 31 Jan 2018
All 50 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-fs-lock
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-fs-lock
Is github.com/ipfs/go-fs-lock safe to use?
Vulert has no vulnerabilities on record for github.com/ipfs/go-fs-lock 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-fs-lock's Vulert package health score?
Vulert scores github.com/ipfs/go-fs-lock 58/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-fs-lock 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-fs-lock 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-fs-lock have?
0 vulnerabilities are recorded for github.com/ipfs/go-fs-lock 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-fs-lock vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/ipfs/go-fs-lock 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-fs-lock 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-fs-lock for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/ipfs/go-fs-lock version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.