← Home

@graphql-codegen/typescript

npm Repository

GraphQL Code Generator plugin for generating TypeScript types

100
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

dotansimhaardatankamilkisielaurigotheguild-bot

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition from theguild-bot to GitHub Actions CI; SLSA attestation confirms legitimate publish pipeline. ai
provenance missing-githead AI (provenance): CI migration dropped gitHead; SLSA provenance compensates as commit-linking signal. ai

Versions (showing 100 of 443)

Hide prereleases
Version Deps Published
6.0.2 5 / 0
6.0.1 5 / 0
6.0.0 5 / 0
5.0.10 5 / 0
5.0.9 5 / 0
5.0.8 5 / 0
5.0.7 5 / 0
5.0.6 5 / 0
5.0.5 5 / 0
5.0.4 5 / 0
5.0.3 5 / 0
5.0.2 5 / 0
5.0.1 5 / 0
5.0.0 5 / 0
4.1.6 5 / 0
4.1.5 5 / 0
4.1.4 5 / 0
4.1.3 5 / 0
4.1.2 5 / 0
4.1.1 5 / 0
4.1.0 5 / 0
4.0.9 5 / 0
4.0.8 5 / 0
4.0.7 5 / 0
4.0.6 5 / 0
4.0.5 5 / 0
4.0.4 5 / 0
4.0.3 5 / 0
4.0.2 5 / 0
4.0.1 5 / 0
4.0.0 5 / 0
3.0.4 5 / 0
3.0.3 5 / 0
3.0.2 5 / 0
3.0.1 5 / 0
3.0.0 5 / 0
2.8.8 5 / 0
2.8.7 5 / 0
2.8.6 5 / 0
2.8.5 5 / 0
2.8.4 5 / 0
2.8.3 5 / 0
2.8.2 5 / 0
2.8.1 5 / 0
2.8.0 5 / 0
2.7.5 5 / 0
2.7.4 5 / 0
2.7.3 5 / 0
2.7.2 5 / 0
2.7.1 5 / 0
2.7.0 5 / 0
2.6.0 5 / 0
2.5.1 5 / 0
2.5.0 5 / 0
2.4.11 5 / 0
2.4.10 5 / 0
2.4.9 5 / 0
2.4.8 5 / 0
2.4.7 5 / 0
2.4.6 5 / 0
2.4.5 5 / 0
2.4.4 5 / 0
2.4.3 5 / 0
2.4.2 5 / 0
2.4.1 5 / 0
2.4.0 5 / 0
2.3.1 5 / 0
2.3.0 4 / 0
2.2.4 4 / 0
2.2.3 4 / 0
2.2.2 4 / 0
2.2.1 4 / 0
2.2.0 4 / 0
2.1.2 4 / 0
2.1.1 4 / 0
2.1.0 4 / 0
2.0.0 4 / 0
1.23.0 4 / 0
1.22.4 4 / 0
1.22.3 4 / 0
1.22.2 4 / 0
1.22.1 4 / 0
1.22.0 4 / 0
1.21.1 4 / 0
1.21.0 4 / 0
1.20.2 4 / 0
1.20.1 4 / 0
1.20.0 4 / 0
1.19.0 4 / 0
1.18.1 4 / 0
1.18.0 4 / 0
1.17.11 4 / 0
1.17.10 4 / 0
1.17.9 4 / 0
1.17.8 4 / 0
1.17.7 4 / 0
1.17.6 4 / 0
1.17.5 4 / 0
1.17.4 4 / 0
1.17.3 4 / 0
Showing 100 of 443 Next page →

v6.0.2

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: GitHub Actions.

HIGH Publisher changed: theguild-bot → GitHub Actions (on unknown date) provenance

This version was published by a different npm account than previous versions on unknown date. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v6.0.1

1 finding
LOW No provenance attestation provenance

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

v6.0.0

1 finding
LOW No provenance attestation provenance

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

v5.0.10

1 finding
LOW No provenance attestation provenance

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

v5.0.9

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.

v5.0.8

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.

v5.0.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.

v5.0.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.

v5.0.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.

v5.0.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.

v5.0.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.

v5.0.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.

v5.0.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.

v5.0.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.

v4.1.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.

v4.1.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.

v4.1.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.

v4.1.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.

v4.1.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.

v4.1.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.

v4.1.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.

v4.0.9

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.

v4.0.8

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.

v4.0.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.

v4.0.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.

v4.0.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.

v4.0.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.

v4.0.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.

v4.0.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.

v4.0.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.

v4.0.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.