@graphql-toolkit/apollo-engine-loader MIT 24 versions

@graphql-toolkit/apollo-engine-loader

npm Repository Homepage

A set of utils for faster development of GraphQL tools

24

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

ardatandotansimhaurigo

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): dotansimha is the listed author in package.json and has a strong track record (9543 approved packages). The ardatan→dotansimha transition is a known legitimate maintainer arrangement in the graphql-toolkit ecosystem.	ai	2026/04/23
phantom-deps	phantom-dep:tslib	AI (phantom-deps): tslib is a legitimate TypeScript runtime helper listed as a direct dependency; it is used implicitly by TypeScript-compiled output and is not a true phantom dependency for this package.	ai	2026/04/23

Versions (showing 24 of 24)

Version	Deps	Published
0.10.7	3 / 0	2020-05-18
0.10.6	3 / 0	2020-04-29
0.10.5	3 / 0	2020-04-24
0.10.4	3 / 0	2020-04-16
0.10.3	3 / 0	2020-04-07
0.10.2	3 / 0	2020-04-03
0.10.1	3 / 0	2020-04-03
0.9.12	3 / 0	2020-03-29
0.9.11	3 / 0	2020-03-29
0.9.10	3 / 0	2020-03-26
0.9.9	3 / 0	2020-03-17
0.9.8	3 / 0	2020-03-17
0.9.7	3 / 0	2020-01-28
0.9.6	3 / 0	2020-01-28
0.9.5	3 / 0	2020-01-27
0.9.4	3 / 0	2020-01-24
0.9.3	3 / 0	2020-01-24
0.9.2	3 / 0	2020-01-24
0.9.1	3 / 0	2020-01-16
0.9.0	3 / 0	2020-01-06
0.8.1	3 / 0	2020-01-01
0.8.0	3 / 0	2019-12-31
0.7.5	3 / 0	2019-12-23
0.7.4	3 / 6	2019-12-06

v0.10.7

2 findings

HIGH Publisher changed: ardatan → dotansimha (on 2020-05-18) provenance

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.

LOW No provenance attestation provenance

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

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

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: ardatan → dotansimha (on 2020-04-07) provenance

[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

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

1 finding

LOW No provenance attestation provenance

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

v0.9.11

1 finding

LOW No provenance attestation provenance

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

v0.9.10

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 → ardatan (on 2020-03-26) provenance

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

v0.9.9

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: ardatan → dotansimha (on 2020-03-17) provenance

[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

1 finding

LOW No provenance attestation provenance

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

v0.9.7

1 finding

LOW No provenance attestation provenance

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

v0.9.6

1 finding

LOW No provenance attestation provenance

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

v0.9.5

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

1 finding

LOW No provenance attestation provenance

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

v0.8.0

1 finding

LOW No provenance attestation provenance

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

v0.7.5

1 finding

LOW No provenance attestation provenance

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

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