apollo-server-errors — Greenflagged

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

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
maintainer-change	maintainer-takeover	AI (maintainer-change): MDG → apollo-bot is the documented Apollo GraphQL org transition; apollo-bot is the official publishing account with 2329 approved versions.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): Publisher change from mdg to apollo-bot reflects legitimate Apollo org transition circa 2018.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): apollo-bot is the official Apollo GraphQL automation account; addition is expected.	ai	2026/04/24
maintainer-change	maintainer-removed	AI (maintainer-change): mdg removal coincides with Apollo org restructuring; not suspicious in this context.	ai	2026/04/24

Versions (showing 20 of 20)

Version	Deps	Published
3.3.1	0 / 0	2022-01-18
3.3.0	0 / 0	2021-11-05
3.2.0	0 / 0	2021-10-11
3.1.0	0 / 0	2021-08-23
3.0.1	0 / 0	2021-07-16
3.0.0	0 / 0	2021-07-07
2.5.0	0 / 0	2021-04-14
2.4.2	0 / 0	2020-06-30
2.4.1	0 / 0	2020-04-07
2.4.0	0 / 0	2020-03-03
2.3.4	0 / 0	2019-10-21
2.3.3	0 / 0	2019-08-30
2.3.2	0 / 0	2019-08-28
2.3.1	0 / 0	2019-07-11
2.3.0	0 / 0	2019-05-07
2.2.1	0 / 0	2019-02-21
2.2.0	0 / 0	2018-11-07
2.0.2	0 / 0	2018-08-14
2.0.1	0 / 0	2018-08-14
2.0.0	0 / 3	2018-07-19

v3.3.0

1 finding

LOW No provenance attestation provenance

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

v3.2.0

1 finding

LOW No provenance attestation provenance

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

v3.1.0

1 finding

LOW No provenance attestation provenance

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

v3.0.1

1 finding

LOW No provenance attestation provenance

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

v3.0.0

1 finding

LOW No provenance attestation provenance

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

v2.5.0

1 finding

LOW No provenance attestation provenance

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

v2.4.2

1 finding

LOW No provenance attestation provenance

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

v2.4.1

1 finding

LOW No provenance attestation provenance

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

v2.4.0

1 finding

LOW No provenance attestation provenance

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

v2.3.4

1 finding

LOW No provenance attestation provenance

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

v2.3.3

1 finding

LOW No provenance attestation provenance

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

v2.3.2

1 finding

LOW No provenance attestation provenance

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

v2.3.1

1 finding

LOW No provenance attestation provenance

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

v2.3.0

1 finding

LOW No provenance attestation provenance

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

v2.2.1

1 finding

LOW No provenance attestation provenance

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

v2.2.0

3 findings

HIGH Complete maintainer takeover detected maintainer-change

All previous maintainers (mdg) were replaced by new maintainers (apollo-bot). This is a strong signal of a potential package hijack and requires careful review.

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

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

v2.0.2

1 finding

LOW No provenance attestation provenance

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

v2.0.1

1 finding

LOW No provenance attestation provenance

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

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