Vulnerability Database · npm · Package report

graphql-code-generator: vulnerability history, versions and safety

graphql-code-generator is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 1 release, first recorded in Sep 2020. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded H1
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.

Vulert verdict on graphql-code-generator 0.18.2 i

Updated on 23 Oct 2026

Good news: 0.18.2, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 1.

Package health score 71/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Widely used
  • Community Moderate

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

  • Current release 0.18.2 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 02 Sep 2020 i
  • Highest CVSS n/a i
  • With no published fix 0 i
  • Depended on by 21 packages i
  • Stars 11,261 i
  • OpenSSF scorecard 4/10 i
  • Last release 89 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 graphql-code-generator, 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
0.19.0-alpha.80ec87c7 16 May 2019 none MIT — Details →
0.18.2 16 May 2019 none MIT — Details →
0.19.0-alpha.964f7955 16 May 2019 none MIT — Details →
0.19.0-alpha.a49a2a96 16 Apr 2019 none MIT — Details →
0.18.1 16 Apr 2019 H1 MIT Yes Details →
0.19.0-alpha.7713bf54 16 Apr 2019 none MIT — Details →
0.19.0-alpha.ab0b68e0 19 Mar 2019 none MIT — Details →
0.19.0-alpha.fcb05664 19 Mar 2019 none MIT — Details →
0.19.0-alpha.dd5bacfd 19 Mar 2019 none MIT — Details →
0.19.0-alpha.3704b8b3 19 Mar 2019 none MIT — Details →
0.19.0-alpha.810be5e5 18 Mar 2019 none MIT — Details →
0.19.0-alpha.8785b963 18 Mar 2019 none MIT — Details →
0.19.0-alpha.4e974e44 18 Mar 2019 none MIT — Details →
0.19.0-alpha.1871b6a4 18 Mar 2019 none MIT — Details →
0.19.0-alpha.cb4c2258 18 Mar 2019 none MIT — Details →
0.19.0-alpha.5bed8416 18 Mar 2019 none MIT — Details →
0.19.0-alpha.a50faf1a 18 Mar 2019 none MIT — Details →
0.19.0-alpha.5c685b27 18 Mar 2019 none MIT — Details →
0.19.0-alpha.72ec7038 18 Mar 2019 none MIT — Details →
0.19.0-alpha.923f4f64 18 Mar 2019 none MIT — Details →
0.19.0-alpha.11e78159 18 Mar 2019 none MIT — Details →
0.19.0-alpha.eaab1dcc 18 Mar 2019 none MIT — Details →
0.19.0-alpha.bd75ee7b 18 Mar 2019 none MIT — Details →
0.19.0-alpha.e16a0d06 18 Mar 2019 none MIT — Details →
0.19.0-alpha.6eb3811a 18 Mar 2019 none MIT — Details →
0.19.0-alpha.f16a4a0e 18 Mar 2019 none MIT — Details →
0.19.0-alpha.2f3515aa 17 Mar 2019 none MIT — Details →
0.19.0-alpha.06ec81a4 16 Mar 2019 none MIT — Details →
0.19.0-alpha.14bf4dca 16 Mar 2019 none MIT — Details →
0.19.0-alpha.0ee2b047 16 Mar 2019 none MIT — Details →
0.19.0-alpha.56a58741 16 Mar 2019 none MIT — Details →
0.19.0-alpha.9ce4a2d1 16 Mar 2019 none MIT — Details →
0.19.0-alpha.c89797e6 16 Mar 2019 none MIT — Details →
0.19.0-alpha.8182d8a5 15 Mar 2019 none MIT — Details →
0.19.0-alpha.81e9e995 15 Mar 2019 none MIT — Details →
0.19.0-alpha.229b75b9 15 Mar 2019 none MIT — Details →
0.19.0-alpha.b1ef4e44 15 Mar 2019 none MIT — Details →
0.19.0-alpha.05ac61f3 15 Mar 2019 none MIT — Details →
0.19.0-alpha.c28da069 15 Mar 2019 none MIT — Details →
0.19.0-alpha.bc5d307d 15 Mar 2019 none MIT — Details →
0.19.0-alpha.8dbcd4c2 15 Mar 2019 none MIT — Details →
0.19.0-alpha.46ae99f4 15 Mar 2019 none MIT — Details →
0.19.0-alpha.59cd429f 15 Mar 2019 none MIT — Details →
0.19.0-alpha.d55c11db 15 Mar 2019 none MIT — Details →
0.19.0-alpha.96921348 15 Mar 2019 none MIT — Details →
0.19.0-alpha.d32dbce6 15 Mar 2019 none MIT — Details →
0.19.0-alpha.c65acecf 15 Mar 2019 none MIT — Details →
0.19.0-alpha.0b52d31c 15 Mar 2019 none MIT — Details →
0.19.0-alpha.ed857812 15 Mar 2019 none MIT — Details →
0.19.0-alpha.1027b874 15 Mar 2019 none MIT — Details →
0.19.0-alpha.2bf01486 15 Mar 2019 none MIT — Details →
0.19.0-alpha.a74ef9c7 15 Mar 2019 none MIT — Details →
0.19.0-alpha.4a5ef372 15 Mar 2019 none MIT — Details →
0.19.0-alpha.d20bb04b 15 Mar 2019 none MIT — Details →
0.19.0-alpha.2c737cc8 15 Mar 2019 none MIT — Details →
0.19.0-alpha.351a1f63 15 Mar 2019 none MIT — Details →
0.19.0-alpha.fdb0df6c 15 Mar 2019 none MIT — Details →
0.19.0-alpha.85ff402e 14 Mar 2019 none MIT — Details →
0.19.0-alpha.67274bd9 14 Mar 2019 none MIT — Details →
0.19.0-alpha.fe542283 14 Mar 2019 none MIT — Details →
0.19.0-alpha.e87c7ccf 14 Mar 2019 none MIT — Details →
0.19.0-alpha.ece75266 14 Mar 2019 none MIT — Details →
0.19.0-alpha.07841c6e 14 Mar 2019 none MIT — Details →
0.19.0-alpha.e10f14df 14 Mar 2019 none MIT — Details →
0.19.0-alpha.645c985c 14 Mar 2019 none MIT — Details →
0.19.0-alpha.f30ac657 14 Mar 2019 none MIT — Details →
0.19.0-alpha.fb3f63d6 14 Mar 2019 none MIT — Details →
0.19.0-alpha.28c537b2 14 Mar 2019 none MIT — Details →
0.19.0-alpha.58c6a93d 14 Mar 2019 none MIT — Details →
0.19.0-alpha.515e2e18 14 Mar 2019 none MIT — Details →
0.19.0-alpha.6f432573 14 Mar 2019 none MIT — Details →
0.19.0-alpha.63dff9f8 14 Mar 2019 none MIT — Details →
0.19.0-alpha.f30d6081 14 Mar 2019 none MIT — Details →
0.19.0-alpha.67e66c5f 14 Mar 2019 none MIT — Details →
0.19.0-alpha.ee93d1cd 14 Mar 2019 none MIT — Details →
0.19.0-alpha.73e75066 14 Mar 2019 none MIT — Details →
0.19.0-alpha.66950339 14 Mar 2019 none MIT — Details →
0.19.0-alpha.6f299999 14 Mar 2019 none MIT — Details →
0.19.0-alpha.8cc09fa8 14 Mar 2019 none MIT — Details →
0.19.0-alpha.16bda3d1 14 Mar 2019 none MIT — Details →
0.19.0-alpha.22df701b 14 Mar 2019 none MIT — Details →
0.19.0-alpha.85311445 14 Mar 2019 none MIT — Details →
0.19.0-alpha.cc52ac6e 14 Mar 2019 none MIT — Details →
0.19.0-alpha.5261323e 13 Mar 2019 none MIT — Details →
0.19.0-alpha.af1376cc 13 Mar 2019 none MIT — Details →
0.19.0-alpha.8e3376c3 13 Mar 2019 none MIT — Details →
0.19.0-alpha.10ac8723 13 Mar 2019 none MIT — Details →
0.19.0-alpha.e359e2c6 13 Mar 2019 none MIT — Details →
0.19.0-alpha.c92069bc 13 Mar 2019 none MIT — Details →
0.19.0-alpha.cbaa90b1 13 Mar 2019 none MIT — Details →
0.19.0-alpha.dfa96422 13 Mar 2019 none MIT — Details →
0.19.0-alpha.1198c408 13 Mar 2019 none MIT — Details →
0.19.0-alpha.48475fee 13 Mar 2019 none MIT — Details →
0.19.0-alpha.1865f150 13 Mar 2019 none MIT — Details →
0.19.0-alpha.100cdc59 12 Mar 2019 none MIT — Details →
0.19.0-alpha.52db8d29 12 Mar 2019 none MIT — Details →
0.19.0-alpha.5da81870 12 Mar 2019 none MIT — Details →
0.19.0-alpha.6f658f74 12 Mar 2019 none MIT — Details →
0.19.0-alpha.f77b20ca 12 Mar 2019 none MIT — Details →
0.19.0-alpha.b4479bfa 12 Mar 2019 none MIT — Details →
0.19.0-alpha.2e648156 12 Mar 2019 none — — Details →
0.19.0-alpha.4e578a05 12 Mar 2019 none — — Details →
0.19.0-alpha.d99a62e9 12 Mar 2019 none — — Details →
0.19.0-alpha.df8aa0d4 12 Mar 2019 none — — Details →
0.19.0-alpha.ecd17774 12 Mar 2019 none — — Details →
0.19.0-alpha.a3a6b268 12 Mar 2019 none — — Details →
0.19.0-alpha.82e27c41 12 Mar 2019 none — — Details →
0.19.0-alpha.02a522e7 12 Mar 2019 none — — Details →
0.19.0-alpha.813c8d3c 12 Mar 2019 none — — Details →
0.19.0-alpha.c95fd6a7 12 Mar 2019 none — — Details →
0.19.0-alpha.3f859ab8 11 Mar 2019 none — — Details →
0.19.0-alpha.e74eb07a 11 Mar 2019 none — — Details →
0.19.0-alpha.2d4a70fd 11 Mar 2019 none — — Details →
0.19.0-alpha.084e1254 11 Mar 2019 none — — Details →
0.19.0-alpha.d3a72027 11 Mar 2019 none — — Details →
0.19.0-alpha.aee3ac63 11 Mar 2019 none — — Details →
0.19.0-alpha.2da4f267 11 Mar 2019 none — — Details →
0.19.0-alpha.1275f653 11 Mar 2019 none — — Details →
0.19.0-alpha.0d1c696f 11 Mar 2019 none — — Details →
0.19.0-alpha.b8a815c8 11 Mar 2019 none — — Details →

The newest 120 of 1,616 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 1 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for graphql-code-generator

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →

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 graphql-code-generator

Is graphql-code-generator safe to use?

Vulert records 1 vulnerabilities for graphql-code-generator in npm: 0 critical, 1 high, 0 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is graphql-code-generator's Vulert package health score?

Vulert scores graphql-code-generator 71/100, which reads as in good shape. 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 graphql-code-generator affected?

No. 0.18.2, 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 graphql-code-generator should I use?

0.17.0 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 graphql-code-generator have?

1 vulnerability is recorded for graphql-code-generator in the npm ecosystem: 0 critical, 1 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 graphql-code-generator vulnerabilities disclosed?

0 vulnerabilities were recorded for graphql-code-generator in the last 12 months, and the oldest entry in this database dates to 02 Sep 2020. 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 graphql-code-generator 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 graphql-code-generator for upcoming vulnerabilities?

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