Vulnerability Database · npm · Package report
@urql/core: vulnerability history, versions and safety
@urql/core is a package in the npm ecosystem. Vulert holds no vulnerabilities for it yet.
Nothing recorded for this package in the npm ecosystem.
Every vulnerability has a patched version to move to.
No published version shipped hostile code.
Vulert verdict on @urql/core 6.0.3 i
Updated on 23 Oct 2026
Good news: 6.0.3, the version you would install today, has no known vulnerabilities.
- Security No known security issues
- Maintenance Sustainable
- Popularity Widely used
- Community Moderate
What to do: Stay on 6.0.3 or newer. This can change: a vulnerability disclosed tomorrow can affect 6.0.3 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release 6.0.3 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Depended on by 125 packages i
- Stars 8,980 i
- Last release 4 months ago i
- Licence MIT i
Version list, release dates, licence and dependants published by the npm registry, 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 @urql/core, 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.
- 6.0.3 22 Jun 2026
- 6.0.2 15 Jun 2026
- 6.0.1 11 Aug 2025
- 6.0.1-canary-cddc86dd6b17faed7fd5c91ccb4b49aa2acdd91e 11 Aug 2025
- 6.0.0 09 Aug 2025
- 6.0.0-canary-b981b388ee9ed0066399a632aad6b84559f014a6 09 Aug 2025
- 6.0.0-canary-d3b019d51905c1c8b22be9ea1d9fe9ca4335a46c 09 Aug 2025
- 5.3.0-canary-230febcc145a095d1111a82b5993c3e8ab4b490b 09 Aug 2025
- 5.3.0-canary-b757332b0d05a9a79fea180dbd6e7942d27419a2 09 Aug 2025
- 5.2.0 29 Jun 2025
- 5.2.0-canary-b31d5cbfd18c24789f248c2c0494a693a75b06a9 29 Jun 2025
- 6.0.0-canary-b2d8b993af4abb0ffc5c5284b90aca56c527f045 29 Jun 2025
- 5.1.2 27 Jun 2025
- 5.1.2-canary-92f5c477b6d5de6fa77d6c37aafafff3c306b293 03 Apr 2025
- 5.1.2-canary-48f433a4cc61940b94ca49e5735ea56caf351994 02 Apr 2025
- 5.1.2-canary-53b822bc06e8af454b33cb48e59cb25e15fad2d5 01 Apr 2025
- 5.1.1 03 Mar 2025
- 5.1.1-canary-573944cea80f766668d3b9d8aa1afd2c50d744a4 03 Mar 2025
- 5.1.0 09 Dec 2024
- 5.1.0-canary-07397cf11b4b6a64bf8fff9a8ea2e23b81d83067 09 Dec 2024
- 5.0.8 21 Oct 2024
- 5.0.8-canary-e452d6f1e21844a19b63cd86e5867cbaeeb79119 21 Oct 2024
- 5.0.7 19 Oct 2024
- 5.0.7-canary-36a07165f45ab743e8938ee814378199fbc9cf89 19 Oct 2024
- 5.0.6 12 Aug 2024
- 5.0.6-canary-a620d153 05 Aug 2024
- 5.0.5 29 Jul 2024
- 5.0.5-canary-c73d0e2a 29 Jul 2024
- 5.0.4 06 Jun 2024
- 5.0.4-canary-befdf48d 06 Jun 2024
- 5.0.4-canary-d07602d2 06 Jun 2024
- 5.0.4-canary-bf01d6b4 05 Jun 2024
- 5.0.4-canary-ff1fd76a 05 Jun 2024
- 5.0.3 01 May 2024
- 5.0.2 24 Apr 2024
- 5.0.2-canary-0f3c5c01 24 Apr 2024
- 5.0.1 18 Apr 2024
- 5.0.1-canary-1805b920 18 Apr 2024
- 5.0.0 02 Apr 2024
- 5.0.0-canary-fe47189d 02 Apr 2024
- 5.0.0-canary-a6f51628 02 Apr 2024
- 5.0.0-canary-6bd4c90f 02 Apr 2024
- 5.0.0-canary-9405b3d8 02 Apr 2024
- 5.0.0-canary-564929ef 28 Mar 2024
- 5.0.0-canary-a938b342 27 Mar 2024
- 5.0.0-canary-3692842e 26 Mar 2024
- 5.0.0-canary-431b64b4 22 Mar 2024
- 5.0.0-canary-be9c72ab 16 Mar 2024
- 4.3.0 03 Mar 2024
- 4.3.0-canary-eb1286c7 02 Mar 2024
- 4.3.0-canary-e9b476b6 02 Mar 2024
- 4.3.0-canary-ceeb73bb 02 Mar 2024
- 4.3.0-canary-973da7ff 02 Mar 2024
- 4.3.0-canary-492af087 02 Mar 2024
- 4.3.0-canary-969935c6 02 Mar 2024
- 4.3.0-canary-56c1544b 02 Mar 2024
- 4.3.0-canary-614c7326 02 Mar 2024
- 4.3.0-canary-e8e16bba 02 Mar 2024
- 4.2.4-canary-dc509cc2 10 Feb 2024
- 4.2.3 17 Jan 2024
- 4.2.3-canary-1fabe358 17 Jan 2024
- 4.2.3-canary-93d7256a 17 Jan 2024
- 4.2.2 12 Dec 2023
- 4.2.2-canary-d5d3c97a 12 Dec 2023
- 4.2.1 10 Dec 2023
- 4.2.1-canary-993a017b 10 Dec 2023
- 4.2.1-canary-1d6be509 10 Dec 2023
- 4.2.0 14 Nov 2023
- 4.2.0-canary-94e0c310 14 Nov 2023
- 4.1.4 19 Oct 2023
- 4.1.4-canary-812385d4 19 Oct 2023
- 4.1.4-canary-423897f9 19 Oct 2023
- 4.1.4-canary-f66de5be 19 Oct 2023
- 4.1.4-canary-c35e7a98 09 Oct 2023
- 4.1.4-canary-052d5f49 26 Sep 2023
- 4.1.3 18 Sep 2023
- 4.1.3-canary-643f426a 18 Sep 2023
- 4.1.2 31 Aug 2023
- 4.1.2-canary-7ee36788 31 Aug 2023
- 4.1.2-canary-64315114 30 Aug 2023
- 4.1.1 30 Jul 2023
- 4.1.1-canary-f9ea1db4 30 Jul 2023
- 4.1.0 21 Jul 2023
- 4.1.0-canary-d6bdd72e 21 Jul 2023
- 4.1.0-canary-889ca4db 21 Jul 2023
- 4.1.0-canary-aeb6b44c 21 Jul 2023
- 4.1.0-canary-2acc6298 21 Jul 2023
- 4.1.0-canary-c37a0fc3 19 Jul 2023
- 4.1.0-canary-d3eb256d 19 Jul 2023
- 4.0.12-canary-7ddccc13 19 Jul 2023
- 4.0.11 12 Jul 2023
- 4.0.11-canary-657bd0c6 12 Jul 2023
- 4.0.11-canary-1cf2e2ff 12 Jul 2023
- 4.0.11-canary-caa029e0 08 Jul 2023
- 4.0.11-canary-8b8cf54a 30 Jun 2023
- 4.0.11-canary-19d26748 28 Jun 2023
- 4.0.11-canary-c074a504 27 Jun 2023
- 4.0.10 01 Jun 2023
- 0.0.0-canary-20230601225031 01 Jun 2023
- 4.0.9 01 Jun 2023
- 0.0.0-canary-20230601114104 01 Jun 2023
- 4.0.8 31 May 2023
- 0.0.0-canary-20230531112256 31 May 2023
- 0.0.0-canary-20230531101109 31 May 2023
- 0.0.0-canary-20230531095716 31 May 2023
- 0.0.0-canary-20230531092237 31 May 2023
- 0.0.0-canary-20230531092221 31 May 2023
- 0.0.0-canary-20230531092207 31 May 2023
- 0.0.0-canary-20230530205112 30 May 2023
- 0.0.0-canary-20230530201758 30 May 2023
- 0.0.0-canary-20230528121951 28 May 2023
- 0.0.0-canary-20230525143453 25 May 2023
- 0.0.0-canary-20230525140750 25 May 2023
- 0.0.0-canary-20230504153855 04 May 2023
- 0.0.0-canary-20230503132020 03 May 2023
- 0.0.0-canary-20230429141303 29 Apr 2023
- 0.0.0-canary-20230429140656 29 Apr 2023
- 4.0.7 25 Apr 2023
- 0.0.0-canary-20230425131626 25 Apr 2023
- 4.0.6 20 Apr 2023
The newest 120 of 283 versions Vulert tracks. 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.
Other ways into the data
03 Vulnerabilities
Recorded vulnerabilities for @urql/core
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 @urql/core
Is @urql/core safe to use?
Vulert has no vulnerabilities on record for @urql/core in npm 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 @urql/core's Vulert package health score?
Vulert scores @urql/core 89/100, which reads as healthy. 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 @urql/core affected?
No. 6.0.3, 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 @urql/core should I use?
6.0.3 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 @urql/core have?
0 vulnerabilities are recorded for @urql/core in the npm 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 @urql/core vulnerabilities disclosed?
0 vulnerabilities were recorded for @urql/core 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 @urql/core 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 @urql/core for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the @urql/core version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.