apollo-link-batch-http MIT 29 versions

apollo-link-batch-http

npm Repository Homepage

Batch HTTP transport layer for GraphQL

29

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

apollo-botevanshauserjbaxleyiii

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
npm-metadata	suspicious-initial-version	AI (npm-metadata): 0.0.0 is a known pattern for Apollo Link monorepo placeholder releases; package is 3184 days old with 34.8k weekly downloads from a well-established publisher.	ai	2026/04/24
phantom-deps	phantom-dep:@types/graphql	AI (phantom-deps): @types/graphql is declared as an optional dependency for TypeScript type definitions, not a runtime import — standard practice for type packages.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): Publisher change from mdg to apollo-bot in 2018 reflects the well-known, legitimate Apollo/MDG organizational transition. Stable for this package.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): apollo-bot added as part of the documented 2018 MDG→Apollo organizational transition. apollo-bot has a strong track record (2469 approved packages).	ai	2026/04/24
maintainer-change	maintainer-removed	AI (maintainer-change): mdg removed as part of the documented 2018 MDG→Apollo organizational transition. Not a suspicious takeover.	ai	2026/04/24
provenance	no-provenance	AI (provenance): Package predates Sigstore provenance adoption; absence of attestation is expected for this era of publishing.	ai	2026/04/24

Versions (showing 29 of 29)

Version	Deps	Published
1.2.14	4 / 13	2020-04-09
1.2.13	4 / 13	2019-09-06
1.2.12	4 / 13	2019-06-14
1.2.11	4 / 13	2019-03-14
1.2.10	4 / 13	2019-03-14
1.2.9	4 / 13	2019-03-05
1.2.8	3 / 15	2019-02-01
1.2.7	3 / 15	2019-02-01
1.2.6	3 / 15	2018-12-15
1.2.5	3 / 15	2018-12-13
1.2.4	3 / 15	2018-11-21
1.2.3	3 / 15	2018-09-15
1.2.2	3 / 15	2018-04-12
1.2.1	3 / 15	2018-03-05
1.2.0	3 / 15	2018-02-27
1.1.1	3 / 15	2018-02-23
1.1.0	3 / 15	2018-02-21
1.0.5	4 / 14	2018-02-08
1.0.4	4 / 14	2017-12-18
1.0.3	4 / 14	2017-12-08
1.0.2	4 / 14	2017-11-30
1.0.1	3 / 15	2017-11-15
1.0.0	3 / 15	2017-10-24
0.4.0	3 / 15	2017-10-13
0.3.0	3 / 15	2017-10-03
0.1.4	4 / 19	2017-09-07
0.1.2	4 / 20	2017-09-07
0.1.0	4 / 19	2017-08-09
0.0.0	4 / 17	2017-08-04

v1.2.14

1 finding

LOW No provenance attestation provenance

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

v1.2.13

1 finding

LOW No provenance attestation provenance

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

v1.2.12

1 finding

LOW No provenance attestation provenance

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

v1.2.11

1 finding

LOW No provenance attestation provenance

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

v1.2.10

1 finding

LOW No provenance attestation provenance

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

v1.2.9

1 finding

LOW No provenance attestation provenance

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

v1.2.8

1 finding

LOW No provenance attestation provenance

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

v1.2.7

1 finding

LOW No provenance attestation provenance

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

v1.2.6

1 finding

LOW No provenance attestation provenance

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

v1.2.5

2 findings

HIGH Publisher changed: evanshauser → apollo-bot (on 2018-12-13) provenance

This version was published by a different npm account than previous versions on 2018-12-13. 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.

v1.2.4

2 findings

HIGH Publisher changed: mdg → apollo-bot (on 2018-11-21) provenance

This version was published by a different npm account than previous versions on 2018-11-21. 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.

v1.2.3

2 findings

HIGH Publisher changed: evanshauser → mdg (on 2018-09-15) provenance

This version was published by a different npm account than previous versions on 2018-09-15. 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.

v1.2.2

1 finding

LOW No provenance attestation provenance

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

v1.2.1

1 finding

LOW No provenance attestation provenance

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

v1.2.0

2 findings

HIGH Publisher changed: evanshauser → jbaxleyiii (on 2018-02-27) provenance

This version was published by a different npm account than previous versions on 2018-02-27. 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.

v1.1.1

1 finding

LOW No provenance attestation provenance

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

v1.1.0

2 findings

HIGH Publisher changed: jbaxleyiii → evanshauser (on 2018-02-21) provenance

This version was published by a different npm account than previous versions on 2018-02-21. 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.

v1.0.5

1 finding

LOW No provenance attestation provenance

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

v1.0.4

2 findings

HIGH Publisher changed: jbaxleyiii → mdg (on 2017-12-18) provenance

This version was published by a different npm account than previous versions on 2017-12-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.

v1.0.3

1 finding

LOW No provenance attestation provenance

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

v1.0.2

1 finding

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

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

INFO No provenance attestation provenance

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

v0.3.0

1 finding

INFO No provenance attestation provenance

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

v0.1.4

1 finding

INFO No provenance attestation provenance

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

v0.1.2

2 findings

INFO No provenance attestation provenance

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

INFO Publisher changed: evanshauser → jbaxleyiii (on 2017-09-07) provenance

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

v0.1.0

1 finding

INFO No provenance attestation provenance

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

v0.0.0

1 finding

INFO No provenance attestation provenance

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