apollo-link-batch — Greenflagged

Apollo Link that performs batching and operation on batched Operations

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 Apollo Link monorepo convention for initial package publication; this package has 3181 days of history and 36k weekly downloads — not a throwaway malicious package.	ai	2026/04/24
phantom-deps	phantom-dep:@types/graphql	AI (phantom-deps): @types/graphql is declared as an optional dependency for TypeScript type support, loaded by convention. Not a real phantom dependency risk.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): Publisher change from mdg to jbaxleyiii in 2018 reflects the well-known legitimate transition of Apollo project from Meteor Development Group to the Apollo team; jbaxleyiii is a core Apollo contributor with strong track record.	ai	2026/04/24

Versions (showing 28 of 28)

Version	Deps	Published
1.1.15	2 / 12	2020-04-09
1.1.14	2 / 12	2019-09-06
1.1.13	2 / 12	2019-06-14
1.1.12	2 / 12	2019-03-14
1.1.11	2 / 12	2019-03-14
1.1.10	2 / 12	2019-03-05
1.1.9	1 / 14	2019-02-01
1.1.8	1 / 14	2019-02-01
1.1.7	1 / 14	2018-12-15
1.1.6	1 / 14	2018-12-13
1.1.5	1 / 14	2018-11-21
1.1.4	1 / 14	2018-09-15
1.1.3	1 / 14	2018-04-12
1.1.2	1 / 14	2018-03-05
1.1.1	1 / 14	2018-02-23
1.1.0	1 / 14	2018-02-21
1.0.5	1 / 14	2018-02-08
1.0.4	1 / 14	2017-12-18
1.0.3	1 / 14	2017-12-08
1.0.2	1 / 14	2017-11-30
1.0.1	0 / 15	2017-11-15
1.0.0	0 / 15	2017-10-24
0.4.0	0 / 15	2017-10-13
0.3.0	0 / 15	2017-10-03
0.1.4	3 / 18	2017-09-07
0.1.2	3 / 19	2017-09-07
0.1.0	3 / 18	2017-08-09
0.0.0	4 / 17	2017-08-07

v1.1.15

1 finding

LOW No provenance attestation provenance

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

v1.1.14

1 finding

LOW No provenance attestation provenance

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

v1.1.13

1 finding

LOW No provenance attestation provenance

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

v1.1.12

1 finding

LOW No provenance attestation provenance

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

v1.1.11

1 finding

LOW No provenance attestation provenance

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

v1.1.10

1 finding

LOW No provenance attestation provenance

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

v1.1.9

1 finding

LOW No provenance attestation provenance

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

v1.1.8

1 finding

LOW No provenance attestation provenance

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

v1.1.7

1 finding

LOW No provenance attestation provenance

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

v1.1.6

1 finding

LOW No provenance attestation provenance

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

v1.1.5

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: mdg → apollo-bot (on 2018-11-21) provenance

[Accepted risk] 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.

v1.1.4

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

1 finding

LOW No provenance attestation provenance

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

v1.1.2

1 finding

LOW No provenance attestation provenance

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

v1.1.1

2 findings

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

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

2 findings

HIGH Publisher changed: mdg → jbaxleyiii (on 2018-02-08) provenance

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

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

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

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.

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