graphql-import MIT 30 versions

graphql-import

npm Repository

[![CircleCI](https://circleci.com/gh/prisma/graphql-import.svg?style=shield)](https://circleci.com/gh/prisma/graphql-import) [![npm version](https://badge.fury.io/js/graphql-import.svg)](https://badge.fury.io/js/graphql-import)

30

Versions

MIT

License

No

Install Scripts

Missing

Provenance

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

ardatandotansimhakamilkisielakbrandwijkschicklingtimsuchanekurigo

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Legitimate transfer from Prisma (timsuchanek) to The Guild (ardatan), a well-documented GraphQL ecosystem transition.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): New maintainers are all known members of The Guild (ardatan, dotansimha, kamilkisiela, urigo), the established GraphQL tooling org.	ai	2026/04/24
publish-pattern	new-deps-added	AI (publish-pattern): All new deps are @graphql-toolkit/* packages from The Guild; refactor to use their own toolkit replacing lodash/resolve-from.	ai	2026/04/24
semgrep	semgrep:child-process-import	AI (semgrep): child_process usage is in a build utility script (bump.js) that only runs 'git rev-parse' to get a commit hash. This is a benign build-time tool, not a runtime or install-time risk.	ai	2026/04/23

Versions (showing 30 of 30)

Version	Deps	Published
1.0.2	6 / 10	2020-04-08
1.0.1	10 / 11	2020-03-20
1.0.0	10 / 11	2020-03-17
0.7.1	2 / 14	2018-09-12
0.7.0	2 / 14	2018-09-07
0.6.0	1 / 13	2018-05-22
0.5.3	1 / 13	2018-05-22
0.5.2	1 / 13	2018-04-26
0.5.1	1 / 13	2018-04-26
0.5.0	1 / 13	2018-03-23
0.4.5	1 / 13	2018-02-27
0.4.4	1 / 13	2018-02-23
0.4.3	2 / 12	2018-02-07
0.4.2	2 / 12	2018-01-30
0.4.1	2 / 12	2018-01-15
0.4.0	2 / 12	2018-01-12
0.3.1	2 / 12	2018-01-06
0.3.0	2 / 12	2018-01-06
0.2.1	2 / 12	2018-01-05
0.2.0	4 / 10	2018-01-04
0.1.9	4 / 6	2017-12-29
0.1.8	4 / 6	2017-12-19
0.1.7	4 / 6	2017-12-19
0.1.6	4 / 6	2017-12-19
0.1.5	4 / 5	2017-12-07
0.1.4	4 / 5	2017-12-04
0.1.3	4 / 5	2017-11-22
0.1.2	4 / 5	2017-11-22
0.1.1	4 / 5	2017-11-22
0.1.0	4 / 5	2017-11-22

v1.0.2

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: ardatan.

LOW No provenance attestation provenance

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

v1.0.1

1 finding

LOW No provenance attestation provenance

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

v1.0.0

2 findings

HIGH Publisher changed: timsuchanek → ardatan (on 2020-03-17) provenance

This version was published by a different npm account than previous versions on 2020-03-17. 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.7.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: schickling → timsuchanek (on 2018-09-07) provenance

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

v0.6.0

1 finding

LOW No provenance attestation provenance

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

v0.5.3

1 finding

LOW No provenance attestation provenance

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

v0.5.2

1 finding

LOW No provenance attestation provenance

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

v0.5.1

1 finding

LOW No provenance attestation provenance

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

v0.5.0

1 finding

LOW No provenance attestation provenance

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

v0.4.5

1 finding

LOW No provenance attestation provenance

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

v0.4.4

1 finding

LOW No provenance attestation provenance

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

v0.4.3

1 finding

LOW No provenance attestation provenance

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

v0.4.2

1 finding

LOW No provenance attestation provenance

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

v0.4.1

1 finding

LOW No provenance attestation provenance

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

v0.4.0

1 finding

LOW No provenance attestation provenance

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

v0.3.1

1 finding

LOW No provenance attestation provenance

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

v0.3.0

1 finding

LOW No provenance attestation provenance

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

v0.2.1

1 finding

LOW No provenance attestation provenance

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

v0.2.0

1 finding

LOW No provenance attestation provenance

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

v0.1.9

1 finding

LOW No provenance attestation provenance

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

v0.1.8

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: kbrandwijk → schickling (on 2017-12-19) provenance

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

v0.1.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: schickling → kbrandwijk (on 2017-12-19) provenance

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

v0.1.6

1 finding

LOW No provenance attestation provenance

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

v0.1.5

1 finding

LOW No provenance attestation provenance

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

v0.1.4

1 finding

LOW No provenance attestation provenance

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

v0.1.3

1 finding

LOW No provenance attestation provenance

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

v0.1.2

1 finding

LOW No provenance attestation provenance

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

v0.1.1

1 finding

LOW No provenance attestation provenance

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

v0.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.