Vulnerability Database · Go · Package report
github.com/anaskhan96/soup: vulnerability history, versions and safety
github.com/anaskhan96/soup 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/anaskhan96/soup v1.2.5 i
Updated on 23 Oct 2026
Good news: v1.2.5, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Unmaintained
- Popularity Key ecosystem project
- Community Quiet
What to do: Stay on v1.2.5 or newer. This can change: a vulnerability disclosed tomorrow can affect v1.2.5 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v1.2.5 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 2,298 i
- OpenSSF scorecard 4/10 i
- Last release 57 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/anaskhan96/soup, 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.6-0.20260801142441-260263cac6a1 01 Aug 2026
- v0.0.0-20220116143516-fd2b5f70c1dd 16 Jan 2022
- v1.2.5 16 Jan 2022
- v1.2.5-0.20220116143516-fd2b5f70c1dd 16 Jan 2022
- v1.2.5-0.20220116130500-62fe4ff125d1 16 Jan 2022
- v1.1.2-0.20200924100242-cb47551b3781 24 Sep 2020
- v1.2.4 24 Sep 2020
- v1.1.2-0.20200924064638-aabbbdd9f8e5 24 Sep 2020
- v1.2.3 23 Sep 2020
- v1.2.2 22 Sep 2020
- v1.1.2-0.20200922221925-09f279635b9e 22 Sep 2020
- v1.2.1 22 Sep 2020
- v1.1.2-0.20200817121540-5e46fcffa8b1 17 Aug 2020
- v1.1.2-0.20200220101040-0abf2cdad74b 20 Feb 2020
- v1.1.2-0.20200127214805-1e693e5a645d 27 Jan 2020
- v1.1.2-0.20191117193415-7276eee1f260 17 Nov 2019
- v1.1.2-0.20191117192206-2dc040128ecb 17 Nov 2019
- v0.0.0-20190517160040-b32d4fb0aaab 17 May 2019
- v1.1.2-0.20190517160040-b32d4fb0aaab 17 May 2019
- v1.1.2-0.20190516214245-38228baa104e 16 May 2019
- v1.1.1 28 Nov 2018
- v0.0.0-20180622125956-00be3d730c89 22 Jun 2018
- v1.0.2-0.20180622125956-00be3d730c89 22 Jun 2018
- v0.0.0-20180328123631-cd07662ec930 28 Mar 2018
- v1.0.2-0.20180328123631-cd07662ec930 28 Mar 2018
- v1.0.2-0.20180222140640-583d5ee80dd8 22 Feb 2018
- v1.0.2-0.20171218203125-df81beb8204e 18 Dec 2017
- v1.0.1 07 Oct 2017
- v1.0.1-0.20171003150001-ad448eafe76e 03 Oct 2017
- v1.0.0 29 Mar 2017
All 30 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/anaskhan96/soup
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/anaskhan96/soup
Is github.com/anaskhan96/soup safe to use?
Vulert has no vulnerabilities on record for github.com/anaskhan96/soup 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/anaskhan96/soup's Vulert package health score?
Vulert scores github.com/anaskhan96/soup 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/anaskhan96/soup affected?
No. v1.2.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/anaskhan96/soup should I use?
v1.2.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/anaskhan96/soup have?
0 vulnerabilities are recorded for github.com/anaskhan96/soup 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/anaskhan96/soup vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/anaskhan96/soup 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/anaskhan96/soup 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/anaskhan96/soup for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/anaskhan96/soup version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.