Vulnerability Database · Go · Package report
github.com/fvbommel/sortorder: vulnerability history, versions and safety
github.com/fvbommel/sortorder 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/fvbommel/sortorder v1.2.1 i
Updated on 23 Oct 2026
Good news: v1.2.1, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Sustainable
- Popularity Little adoption
- Community Inactive
What to do: Stay on v1.2.1 or newer. This can change: a vulnerability disclosed tomorrow can affect v1.2.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v1.2.1 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 32 i
- OpenSSF scorecard 1/10 i
- Last release this month 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/fvbommel/sortorder, 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.
- v1.2.1 10 Oct 2026
- v1.2.0 01 Sep 2026
- v0.0.0-20230318202538-d2b6b6568524 18 Mar 2023
- v1.0.2-0.20230318202538-d2b6b6568524 18 Mar 2023
- v1.1.1-0.20230318202538-d2b6b6568524 18 Mar 2023
- v1.1.0 18 Mar 2023
- v1.0.3-0.20220821234150-42e2c37374b4 21 Aug 2022
- v0.0.0-20200925095916-26fad50c6b32 25 Sep 2020
- v1.0.2 25 Sep 2020
- v1.0.2-0.20200920220440-737e6f107ced 20 Sep 2020
- v1.0.1 28 Aug 2020
- v0.0.0-20200828045120-6b6b45a52fcc 28 Aug 2020
- v1.0.0 28 Aug 2020
- v0.0.0-20200828042635-3194d9ecce81 28 Aug 2020
- v0.0.0-20180919145318-efcd4e0f9787 19 Sep 2018
- v0.0.0-20180317150156-bafa06717c42 17 Mar 2018
- v0.0.0-20170409195630-256737ac55c4 09 Apr 2017
- v0.0.0-20160121211510-db5cfe13f5cc 21 Jan 2016
- v0.0.0-20151108152656-928aaa586d77 08 Nov 2015
- v0.0.0-20150409213349-0709f351e8e8 09 Apr 2015
- v0.0.0-20140724163532-f8d987e631c9 24 Jul 2014
- v0.0.0-20130620175044-84f323a0a986 20 Jun 2013
- v0.0.0-20130619215622-7a446fc14c15 19 Jun 2013
All 23 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/fvbommel/sortorder
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/fvbommel/sortorder
Is github.com/fvbommel/sortorder safe to use?
Vulert has no vulnerabilities on record for github.com/fvbommel/sortorder 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/fvbommel/sortorder's Vulert package health score?
Vulert scores github.com/fvbommel/sortorder 63/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/fvbommel/sortorder affected?
No. v1.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/fvbommel/sortorder should I use?
v1.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/fvbommel/sortorder have?
0 vulnerabilities are recorded for github.com/fvbommel/sortorder 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/fvbommel/sortorder vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/fvbommel/sortorder 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/fvbommel/sortorder 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/fvbommel/sortorder for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/fvbommel/sortorder version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.