@graphql-toolkit/code-file-loader
A set of utils for faster development of GraphQL tools
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Established publisher ardatan with strong track record; no material code changes vs prior version; missing gitHead reflects publish environment change, not a compromise indicator. | ai | |
| provenance | publisher-changed | AI (provenance): Historical transition (2019) from dotansimha to ardatan, a well-established publisher with 97 approved packages. Legitimate ecosystem stewardship transfer. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): ardatan is a trusted, long-standing npm publisher with strong approval history. Addition reflects the known graphql-toolkit project transfer. | ai | |
| provenance | no-provenance | AI (provenance): Package was published in 2019, before Sigstore provenance was available in the npm ecosystem. Expected for packages of this age. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a declared dependency used implicitly by compiled TypeScript output; phantom-dep false positive for this package. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require is a core feature of this GraphQL file loader — it must dynamically import user-provided schema files at runtime. This pattern is intentional and stable for this package. | ai |
Versions (showing 36 of 36)
| Version | Deps | Published |
|---|---|---|
| 0.10.7 | 3 / 0 | |
| 0.10.6 | 3 / 0 | |
| 0.10.5 | 3 / 0 | |
| 0.10.4 | 3 / 0 | |
| 0.10.3 | 3 / 0 | |
| 0.10.2 | 3 / 0 | |
| 0.10.1 | 3 / 0 | |
| 0.9.12 | 3 / 0 | |
| 0.9.11 | 3 / 0 | |
| 0.9.10 | 3 / 0 | |
| 0.9.9 | 3 / 0 | |
| 0.9.8 | 3 / 0 | |
| 0.9.7 | 3 / 0 | |
| 0.9.6 | 3 / 0 | |
| 0.9.5 | 3 / 0 | |
| 0.9.4 | 3 / 0 | |
| 0.9.3 | 3 / 0 | |
| 0.9.2 | 3 / 0 | |
| 0.9.1 | 3 / 0 | |
| 0.9.0 | 3 / 0 | |
| 0.8.1 | 3 / 0 | |
| 0.8.0 | 3 / 0 | |
| 0.7.5 | 3 / 0 | |
| 0.7.4 | 4 / 0 | |
| 0.7.3 | 4 / 0 | |
| 0.7.2 | 4 / 5 | |
| 0.7.1 | 4 / 5 | |
| 0.7.0 | 4 / 5 | |
| 0.6.8 | 4 / 5 | |
| 0.6.7 | 2 / 5 | |
| 0.6.6 | 2 / 5 | |
| 0.6.5 | 2 / 5 | |
| 0.6.4 | 2 / 5 | |
| 0.6.3 | 2 / 5 | |
| 0.6.2 | 2 / 5 | |
| 0.6.0 | 2 / 5 |
v0.10.7
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: dotansimha.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-05-18. This could indicate a legitimate maintainer transition or an account compromise.
v0.10.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.4
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-04-16. This could indicate a legitimate maintainer transition or an account compromise.
v0.10.3
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: dotansimha.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2020-04-07. This could indicate a legitimate maintainer transition or an account compromise.
v0.10.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.12
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ardatan.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.11
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ardatan.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.10
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ardatan.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.9
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: dotansimha.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] 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.
v0.9.8
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ardatan.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.7
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ardatan.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.6
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ardatan.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.5
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ardatan.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ardatan.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.3
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ardatan.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ardatan.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ardatan.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ardatan.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ardatan.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ardatan.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.