Vulnerability Database · Go · Package report
github.com/jjti/go-spancheck: vulnerability history, versions and safety
github.com/jjti/go-spancheck 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/jjti/go-spancheck v0.6.5 i
Updated on 23 Oct 2026
Good news: v0.6.5, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Maintaining
- Popularity Niche
- Community Inactive
What to do: Stay on v0.6.5 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.6.5 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.6.5 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 83 i
- OpenSSF scorecard 2/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/jjti/go-spancheck, 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.6.6-0.20260201012251-2306b02ddb5f 01 Feb 2026
- v0.6.6-0.20260101010355-ff28c3d2d7a1 01 Jan 2026
- v0.6.6-0.20251201011210-7d2fbb5b1ecd 01 Dec 2025
- v0.6.6-0.20251101010340-97291eb8e6ab 01 Nov 2025
- v0.6.6-0.20251001010409-58eb791c99a0 01 Oct 2025
- v0.6.6-0.20250901015939-88bc141fcd39 01 Sep 2025
- v0.6.6-0.20250801014927-e65a7831d7b2 01 Aug 2025
- v0.6.6-0.20250701045801-618b173cfc84 01 Jul 2025
- v0.6.6-0.20250601015643-268cb3f95776 01 Jun 2025
- v0.0.0-20250507181835-41460ddf876c 07 May 2025
- v0.6.6-0.20250507181835-41460ddf876c 07 May 2025
- v0.6.5 07 May 2025
- v0.6.5-0.20250507012232-1e1b740f3573 07 May 2025
- v0.6.5-0.20250501010834-273b3e54cd02 01 May 2025
- v0.6.5-0.20250401015253-a9cb5fd5ec47 01 Apr 2025
- v0.6.5-0.20250301012259-414b13970bca 01 Mar 2025
- v0.6.5-0.20250201015424-8c023f13415b 01 Feb 2025
- v0.6.5-0.20250109041136-4612a14b7326 09 Jan 2025
- v0.6.5-0.20250101012245-2ccd49dfde3c 01 Jan 2025
- v0.6.5-0.20241201014345-0e0826e9200c 01 Dec 2024
- v0.0.0-20241130082403-8cdddbe4b66a 30 Nov 2024
- v0.6.4 30 Nov 2024
- v0.6.4-0.20241130082403-8cdddbe4b66a 30 Nov 2024
- v0.6.3 30 Nov 2024
- v0.6.3-0.20241130051914-926dd069e0fc 30 Nov 2024
- v0.6.3-0.20241130051356-e234cf6dd572 30 Nov 2024
- v0.6.3-0.20240801012434-d7e3810429ff 01 Aug 2024
- v0.0.0-20240619001328-efe1f726d06b 19 Jun 2024
- v0.6.2 19 Jun 2024
- v0.6.2-0.20240619001328-efe1f726d06b 19 Jun 2024
- v0.6.2-0.20240619000034-93b73ef69e74 19 Jun 2024
- v0.6.2-0.20240601012841-675b623d3f50 01 Jun 2024
- v0.0.0-20240422231602-128847493f00 22 Apr 2024
- v0.6.1 22 Apr 2024
- v0.6.1-0.20240422231602-128847493f00 22 Apr 2024
- v0.6.1-0.20240422231453-6dfda67731d7 22 Apr 2024
- v0.6.1-0.20240421190831-ffa275269ac5 21 Apr 2024
- v0.6.1-0.20240421190820-70fbabf48942 21 Apr 2024
- v0.6.1-0.20240421190528-f5e089df8e9f 21 Apr 2024
- v0.0.0-20240421190125-34d21b472924 21 Apr 2024
- v0.5.4-0.20240421190125-34d21b472924 21 Apr 2024
- v0.6.0 21 Apr 2024
- v0.5.4-0.20240420221118-41d395c64a37 20 Apr 2024
- v0.5.4-0.20240401014039-f3bf678f69ff 01 Apr 2024
- v0.0.0-20240301015242-e803c7a6b9ad 01 Mar 2024
- v0.5.4-0.20240301015242-e803c7a6b9ad 01 Mar 2024
- v0.5.4-0.20240301011055-0a0b88dac25d 01 Mar 2024
- v0.5.3 23 Feb 2024
- v0.5.3-0.20240223033856-9c61e039604e 23 Feb 2024
- v0.5.3-0.20240223033646-8d09c2c57a3e 23 Feb 2024
- v0.0.0-20240213171222-0bf80bcef92c 13 Feb 2024
- v0.5.3-0.20240213171222-0bf80bcef92c 13 Feb 2024
- v0.5.3-0.20240213171127-c1911ad04065 13 Feb 2024
- v0.0.0-20240208145207-cae4511a7dd5 08 Feb 2024
- v0.5.3-0.20240208145207-cae4511a7dd5 08 Feb 2024
- v0.5.3-0.20240208144953-9cab7e90d1e1 08 Feb 2024
- v0.5.3-0.20240201012014-900e48bbbf9f 01 Feb 2024
- v0.0.0-20240112144801-1536a9c8c528 12 Jan 2024
- v0.5.2 12 Jan 2024
- v0.5.2-0.20240112144801-1536a9c8c528 12 Jan 2024
- v0.5.1 12 Jan 2024
- v0.4.4-0.20240112134927-93d8c02c66ff 12 Jan 2024
- v0.5.0 12 Jan 2024
- v0.4.3 09 Jan 2024
- v0.4.3-0.20240109161622-54ed04d36213 09 Jan 2024
- v0.4.3-0.20240109154952-6b201efcd9a1 09 Jan 2024
- v0.4.3-0.20240104174953-d5e9b8d6d0f0 04 Jan 2024
- v0.4.3-0.20240104093825-38e83a35d15b 04 Jan 2024
- v0.0.0-20240103031404-7cdaf5e1ebce 03 Jan 2024
- v0.4.3-0.20240103031404-7cdaf5e1ebce 03 Jan 2024
- v0.4.2 03 Jan 2024
- v0.4.2-0.20240103030814-40b71645c36e 03 Jan 2024
- v0.4.1 02 Jan 2024
- v0.4.1-0.20240102225825-e6faa1d972f2 02 Jan 2024
- v0.4.0 02 Jan 2024
- v0.3.4-0.20240102214527-06f109e034cc 02 Jan 2024
- v0.3.3 02 Jan 2024
- v0.3.3-0.20240102182711-4b9fde77d88c 02 Jan 2024
- v0.3.3-0.20240102012430-b8640eff725d 02 Jan 2024
- v0.3.3-0.20231230232511-882acc200297 30 Dec 2023
- v0.3.3-0.20231230232343-5c9f10e1319e 30 Dec 2023
- v0.3.2 30 Dec 2023
- v0.3.2-0.20231230173657-6f797fe93ef6 30 Dec 2023
- v0.3.1 30 Dec 2023
- v0.3.1-0.20231230162453-9fab87bda35e 30 Dec 2023
- v0.2.1-0.20231228230654-5ede281617f0 28 Dec 2023
- v0.3.0 28 Dec 2023
- v0.2.1-0.20231228214010-9695870335cb 28 Dec 2023
- v0.2.1-0.20231228201847-c9bda40592d8 28 Dec 2023
- v0.0.0-20231228200948-45c93d529908 28 Dec 2023
- v0.2.0 28 Dec 2023
- v0.0.3-0.20231228194909-fd857b540a49 28 Dec 2023
- v0.0.0-20231226035850-114b684bd7be 26 Dec 2023
- v0.0.1 26 Dec 2023
- v0.0.0-20231226034034-6a74242f4b11 26 Dec 2023
All 95 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/jjti/go-spancheck
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/jjti/go-spancheck
Is github.com/jjti/go-spancheck safe to use?
Vulert has no vulnerabilities on record for github.com/jjti/go-spancheck 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/jjti/go-spancheck's Vulert package health score?
Vulert scores github.com/jjti/go-spancheck 61/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/jjti/go-spancheck affected?
No. v0.6.5, 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/jjti/go-spancheck should I use?
v0.6.5 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/jjti/go-spancheck have?
0 vulnerabilities are recorded for github.com/jjti/go-spancheck 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/jjti/go-spancheck vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/jjti/go-spancheck 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/jjti/go-spancheck 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/jjti/go-spancheck for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/jjti/go-spancheck version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.