graphql-codegen-core — Greenflagged

GraphQL types and code generator based on schema

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

dotansimha

Keywords

gqlgeneratorcodetypesinterfacesgraphqlcodegenapollonodetypescripttsflowtypesd.tstypings

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	missing-githead	AI (provenance): Established package with 1651 versions from a trusted publisher; missing gitHead is a process/environment change, not a security indicator for this package.	ai	2026/04/24
phantom-deps	phantom-dep:chalk	AI (phantom-deps): chalk is a declared runtime dependency; phantom-dep finding is a benign false positive for this package — likely used in code paths not detected by static analysis.	ai	2026/04/24
phantom-deps	phantom-dep:winston	AI (phantom-deps): winston is a declared runtime dependency; phantom-dep finding is a benign false positive for this package — likely used in code paths not detected by static analysis.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): dotansimha is the original project author (repo is under their GitHub org); the change from kamilkisiela back to dotansimha is a legitimate maintainer transition, not a takeover.	ai	2026/04/24
publish-pattern	new-deps-added	AI (publish-pattern): chalk, change-case, and common-tags are well-known utility packages; their addition to a code generation tool is expected and benign.	ai	2026/04/24

Versions (showing 59 of 59)

Version	Deps	Published
0.18.2	8 / 0	2019-05-16
0.18.1	8 / 0	2019-04-16
0.18.0	8 / 0	2019-03-01
0.17.0	8 / 0	2019-02-21
0.16.1	8 / 0	2019-02-03
0.16.0	7 / 0	2019-01-20
0.15.2	7 / 0	2018-12-24
0.15.1	7 / 0	2018-12-18
0.15.0	7 / 0	2018-12-13
0.14.5	7 / 0	2018-11-29
0.14.4	7 / 0	2018-11-28
0.14.3	7 / 0	2018-11-26
0.14.2	7 / 0	2018-11-25
0.14.1	7 / 1	2018-11-17
0.14.0	7 / 1	2018-11-16
0.13.0	7 / 1	2018-10-31
0.12.6	4 / 0	2018-09-25
0.12.5	4 / 0	2018-09-18
0.12.4	4 / 0	2018-09-18
0.12.3	4 / 0	2018-09-17
0.12.2	4 / 0	2018-09-14
0.12.1	4 / 0	2018-09-13
0.12.0	4 / 0	2018-09-13
0.11.0	3 / 0	2018-08-21
0.10.7	3 / 0	2018-08-08
0.10.6	3 / 0	2018-08-05
0.10.5	3 / 0	2018-07-30
0.10.4	3 / 0	2018-07-27
0.10.3	3 / 0	2018-07-12
0.10.2	3 / 0	2018-07-12
0.10.1	3 / 0	2018-07-03
0.10.0	3 / 0	2018-07-03
0.9.4	3 / 0	2018-06-25
0.9.3	3 / 0	2018-06-18
0.9.2	3 / 0	2018-06-10
0.9.1	2 / 0	2018-05-08
0.9.0	2 / 0	2018-05-07
0.8.21	2 / 0	2018-03-17
0.8.20	2 / 0	2018-03-14
0.8.19	2 / 10	2018-03-13
0.8.18	2 / 10	2018-03-13
0.8.17	2 / 10	2018-03-13
0.8.16	2 / 10	2018-03-13
0.8.15	2 / 10	2018-03-13
0.8.14	2 / 8	2017-10-29
0.8.13	2 / 8	2017-09-21
0.8.12	2 / 8	2017-09-21
0.8.11	2 / 8	2017-09-20
0.8.10	2 / 8	2017-07-24
0.8.9	2 / 8	2017-07-24
0.8.8	2 / 8	2017-07-24
0.8.7	2 / 8	2017-07-23
0.8.6	2 / 8	2017-07-20
0.8.5	4 / 6	2017-07-19
0.8.4	4 / 6	2017-07-18
0.8.3	4 / 6	2017-07-18
0.8.2	4 / 6	2017-07-18
0.8.1	3 / 7	2017-07-18
0.8.0	3 / 7	2017-07-17

v0.18.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.18.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.18.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.17.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.16.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.16.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.15.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.15.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.15.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.14.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.14.4

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: kamilkisiela → dotansimha (on 2018-11-28) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2018-11-28. This could indicate a legitimate maintainer transition or an account compromise.

v0.14.3

3 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: kamilkisiela.

INFO Publisher changed: dotansimha → kamilkisiela (on 2018-11-26) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2018-11-26. This could indicate a legitimate maintainer transition or an account compromise.

v0.14.2

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: dotansimha.

v0.14.1

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: dotansimha.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.14.0

2 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: dotansimha.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.13.0

3 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: dotansimha.

HIGH Publisher changed: kamilkisiela → dotansimha (on 2018-10-31) provenance

This version was published by a different npm account than previous versions on 2018-10-31. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.12.6

3 findings

HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: kamilkisiela.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: dotansimha → kamilkisiela (on 2018-09-25) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2018-09-25. This could indicate a legitimate maintainer transition or an account compromise.

v0.12.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.12.4

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: kamilkisiela → dotansimha (on 2018-09-18) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2018-09-18. This could indicate a legitimate maintainer transition or an account compromise.

v0.12.3

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: dotansimha → kamilkisiela (on 2018-09-17) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2018-09-17. This could indicate a legitimate maintainer transition or an account compromise.

v0.12.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.12.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.12.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.11.0

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: kamilkisiela → dotansimha (on 2018-08-21) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2018-08-21. This could indicate a legitimate maintainer transition or an account compromise.

v0.10.7

2 findings

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: dotansimha → kamilkisiela (on 2018-08-08) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2018-08-08. This could indicate a legitimate maintainer transition or an account compromise.

v0.10.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.10.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.10.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.10.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.10.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.10.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.10.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.9.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.21

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.20

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.19

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.18

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.17

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.16

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.15

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.14

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.13

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.12

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.11

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.10

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.9

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.8.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.8.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.8.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.8.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.8.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.8.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.8.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.8.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.