VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/shurcooL/graphql: vulnerability history, versions and safety

github.com/shurcooL/graphql is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.

i
0 vulnerabilities recorded

Nothing recorded for this package in the Go ecosystem.

i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all github.com/shurcooL/graphql vulnerabilities

Vulert verdict on github.com/shurcooL/graphql v0.0.0-20240915155400-7ee5256398cf i

Updated on 23 Oct 2026

Good news: v0.0.0-20240915155400-7ee5256398cf, the version you would install today, has no known vulnerabilities.

Package health score 61/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Widely used
  • Community Quiet

What to do: Stay on v0.0.0-20240915155400-7ee5256398cf or newer. This can change: a vulnerability disclosed tomorrow can affect v0.0.0-20240915155400-7ee5256398cf too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release v0.0.0-20240915155400-7ee5256398cf — unaffected i
  • Vulnerabilities on record 0 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Stars 731 i
  • OpenSSF scorecard 1/10 i
  • Last release 25 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/shurcooL/graphql, 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.

i
Version Released Vulert vulnerabilities Licence Fix published Details
v0.0.0-20240915155400-7ee5256398cf 15 Sep 2024 none MIT — Details →
v0.0.0-20230722043721-ed46e5a46466 22 Jul 2023 none MIT — Details →
v0.0.0-20230714182844-3e04114ae69a 14 Jul 2023 none MIT — Details →
v0.0.0-20230714180036-7016eab9f755 14 Jul 2023 none MIT — Details →
v0.0.0-20230712132842-85bf0c3c277e 12 Jul 2023 none MIT — Details →
v0.0.0-20230704054941-24ceaa0402e4 04 Jul 2023 none MIT — Details →
v0.0.0-20230704052027-63a4f2adcc75 04 Jul 2023 none MIT — Details →
v0.0.0-20220606043923-3cf50f8a0a29 06 Jun 2022 none MIT — Details →
v0.0.0-20220520033453-bdb1221e171e 20 May 2022 none MIT — Details →
v0.0.0-20200928012149-18c5c3165e3a 28 Sep 2020 none MIT — Details →
v0.0.0-20200928012058-410806f8a482 28 Sep 2020 none MIT — Details →
v0.0.0-20181231061246-d48a9a75455f 31 Dec 2018 none MIT — Details →
v0.0.0-20181114023618-16b88644589a 14 Nov 2018 none MIT — Details →
v0.0.0-20180924043259-e4a3a37e6d42 24 Sep 2018 none MIT — Details →
v0.0.0-20180908223655-365899397c9a 08 Sep 2018 none MIT — Details →
v0.0.0-20180514000029-62c9ce094e75 14 May 2018 none MIT — Details →
v0.0.0-20180509032034-2feaaa7394a5 09 May 2018 none MIT — Details →
v0.0.0-20180302221403-3d276b9dcc6b 02 Mar 2018 none MIT — Details →
v0.0.0-20180223021221-8d3d310716de 23 Feb 2018 none MIT — Details →
v0.0.0-20171201140101-d0549edd16dc 01 Dec 2017 none MIT — Details →
v0.0.0-20171127233224-671b933639ae 27 Nov 2017 none MIT — Details →
v0.0.0-20171103022232-cf6db17b893a 03 Nov 2017 none MIT — Details →
v0.0.0-20171103021214-37c3d629db35 03 Nov 2017 none MIT — Details →
v0.0.0-20170916204736-d1a3e018e03c 16 Sep 2017 none MIT — Details →
v0.0.0-20170831224024-0fb09acdcc06 31 Aug 2017 none MIT — Details →
v0.0.0-20170831214129-1022d3b61cb8 31 Aug 2017 none MIT — Details →
v0.0.0-20170829215937-68e5b1b3ab56 29 Aug 2017 none MIT — Details →
v0.0.0-20170725162000-52ce28a2c9fd 25 Jul 2017 none MIT — Details →
v0.0.0-20170724082853-d2a75ff0ceef 24 Jul 2017 none MIT — Details →
v0.0.0-20170723205744-e6665b336694 23 Jul 2017 none MIT — Details →
v0.0.0-20170723203023-17b8e2b030a2 23 Jul 2017 none MIT — Details →
v0.0.0-20170723202956-5df213a39c08 23 Jul 2017 none MIT — Details →
v0.0.0-20170723200851-83343a21d62d 23 Jul 2017 none MIT — Details →
v0.0.0-20170723200057-60da1d1d5356 23 Jul 2017 none MIT — Details →
v0.0.0-20170712030414-6ac8ee219c8d 12 Jul 2017 none MIT — Details →

All 35 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/shurcooL/graphql

No vulnerability write-ups match this view

Search all 0 in the database →

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

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About github.com/shurcooL/graphql

Is github.com/shurcooL/graphql safe to use?

Vulert has no vulnerabilities on record for github.com/shurcooL/graphql 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/shurcooL/graphql's Vulert package health score?

Vulert scores github.com/shurcooL/graphql 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/shurcooL/graphql affected?

No. v0.0.0-20240915155400-7ee5256398cf, 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/shurcooL/graphql should I use?

v0.0.0-20240915155400-7ee5256398cf 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/shurcooL/graphql have?

0 vulnerabilities are recorded for github.com/shurcooL/graphql 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/shurcooL/graphql vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/shurcooL/graphql 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/shurcooL/graphql 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/shurcooL/graphql for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/shurcooL/graphql version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.