apollo-datasource — 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
npm-metadata	url-dep:apollo-server-caching	AI (npm-metadata): File-path dependency is a monorepo development artifact for apollo-server; standard pattern for Apollo packages, not a security risk.	ai	2026/04/23
npm-metadata	url-dep:apollo-server-env	AI (npm-metadata): File-path dependency is a monorepo development artifact for apollo-server; standard pattern for Apollo packages, not a security risk.	ai	2026/04/23
provenance	publisher-changed	AI (provenance): Publisher change from mdg to apollo-bot reflects Apollo's organizational account migration.	ai	2026/04/23
maintainer-change	maintainer-removed	AI (maintainer-change): mdg removal is part of the legitimate org transition to apollo-bot.	ai	2026/04/23
phantom-deps	phantom-dep:apollo-server-env	AI (phantom-deps): Common monorepo pattern; dependency used at type/re-export level.	ai	2026/04/23
maintainer-change	maintainer-added	AI (maintainer-change): apollo-bot is Apollo GraphQL's official automation account.	ai	2026/04/23
maintainer-change	maintainer-takeover	AI (maintainer-change): mdg → apollo-bot is a known legitimate Apollo GraphQL org transition, not a hijack.	ai	2026/04/23
npm-metadata	no-description	AI (npm-metadata): Apollo monorepo sub-package; missing description is typical for internal utility modules in this ecosystem.	ai	2026/04/21
bogus-package	bogus-package	AI (bogus-package): Inflated semver is expected — this is a monorepo sub-package versioned with the parent. Publisher is the official Apollo bot.	ai	2026/04/21

Versions (showing 32 of 32)

Version	Deps	Published
3.3.2	2 / 0	2022-06-15
3.3.1	2 / 0	2022-01-18
3.3.0	2 / 0	2021-11-05
3.2.0	2 / 0	2021-10-11
3.1.0	2 / 0	2021-08-23
3.0.3	2 / 0	2021-07-26
3.0.2	2 / 0	2021-07-20
3.0.1	2 / 0	2021-07-16
3.0.0	2 / 0	2021-07-07
0.10.0	2 / 0	2022-08-18
0.9.0	2 / 0	2021-04-30
0.8.0	2 / 0	2021-03-26
0.7.3	2 / 0	2021-01-14
0.7.2	2 / 0	2020-06-30
0.7.1	2 / 0	2020-05-27
0.7.0	2 / 0	2020-02-06
0.6.4	2 / 0	2019-12-27
0.6.3	2 / 0	2019-08-30
0.6.2	2 / 0	2019-08-28
0.6.1	2 / 0	2019-07-25
0.6.0	2 / 0	2019-07-16
0.5.0	2 / 0	2019-05-31
0.4.0	2 / 0	2019-05-07
0.3.1	2 / 0	2019-02-14
0.3.0	2 / 0	2019-02-07
0.2.2	2 / 0	2019-01-25
0.2.1	2 / 0	2018-11-26
0.2.0	2 / 0	2018-11-07
0.1.3	2 / 0	2018-09-03
0.1.2	2 / 0	2018-08-14
0.1.1	2 / 0	2018-08-14
0.1.0	2 / 3	2018-07-19

v3.3.1

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 2022-01-18) provenance

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

v3.3.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 2021-11-05) provenance

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

v3.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 2021-10-11) provenance

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

v3.1.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 2021-08-23) provenance

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

v3.0.3

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 2021-07-26) provenance

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

v3.0.2

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 2021-07-20) provenance

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

v3.0.1

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 2021-07-16) provenance

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

v3.0.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 2021-07-07) provenance

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

v0.10.0

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

1 finding

LOW No provenance attestation provenance

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

v0.7.2

1 finding

LOW No provenance attestation provenance

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

v0.7.1

1 finding

LOW No provenance attestation provenance

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

v0.7.0

1 finding

LOW No provenance attestation provenance

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

v0.6.4

1 finding

LOW No provenance attestation provenance

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

v0.6.3

1 finding

LOW No provenance attestation provenance

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

v0.6.2

1 finding

LOW No provenance attestation provenance

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

v0.6.1

1 finding

LOW No provenance attestation provenance

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

v0.6.0

1 finding

LOW No provenance attestation provenance

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

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

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

1 finding

LOW No provenance attestation provenance

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

v0.2.1

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-26) provenance

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

v0.2.0

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-07) provenance

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

v0.1.3

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

1 finding

LOW No provenance attestation provenance

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

v0.1.1

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