apollo-server-env
This package is used internally by Apollo Server and not meant to be consumed directly.
Supply chain provenance
Status for the latest visible version.
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
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 transition is Apollo GraphQL's documented org rebranding (~2018); apollo-bot is the official Apollo org publishing account with 1436 approved packages. | ai | |
| provenance | publisher-changed | AI (provenance): Publisher change from mdg to apollo-bot reflects Apollo GraphQL's organizational rebranding; apollo-bot is the legitimate Apollo org bot account. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): apollo-bot is Apollo GraphQL's official publishing bot; addition is part of the documented org transition from MDG. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): mdg removal is part of Apollo GraphQL's org rebranding; not indicative of a hostile takeover. | ai | |
| bogus-package | bogus-package | AI (bogus-package): apollo-server-env is a legitimate Apollo monorepo utility package; inflated semver reflects the Apollo Server release train, not spam behavior. Short README and no keywords are consistent with an internal utility package. | ai | |
| dependencies | unvetted-dep:node-fetch | AI (dependencies): node-fetch is a well-known, widely-used HTTP library; its use in an Apollo server environment polyfill package is expected and appropriate. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 4.2.1 | 1 / 0 | |
| 4.2.0 | 1 / 0 | |
| 4.1.0 | 1 / 0 | |
| 4.0.3 | 1 / 0 | |
| 4.0.2 | 1 / 0 | |
| 4.0.1 | 2 / 0 | |
| 4.0.0 | 2 / 0 | |
| 3.2.0 | 2 / 0 | |
| 3.1.0 | 2 / 0 | |
| 3.0.0 | 2 / 0 | |
| 2.4.5 | 2 / 0 | |
| 2.4.4 | 2 / 0 | |
| 2.4.3 | 2 / 0 | |
| 2.4.2 | 2 / 0 | |
| 2.4.1 | 2 / 0 | |
| 2.4.0 | 2 / 0 | |
| 2.3.0 | 2 / 0 | |
| 2.2.0 | 2 / 0 | |
| 2.0.3 | 2 / 0 | |
| 2.0.2 | 2 / 0 | |
| 2.0.1 | 2 / 0 | |
| 2.0.0 | 2 / 0 |
v4.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.0
3 findingsAll previous maintainers (mdg) were replaced by new maintainers (apollo-bot). This is a strong signal of a potential package hijack and requires careful review.
This version was published by a different npm account than previous versions on 2019-05-31. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
3 findingsAll previous maintainers (mdg) were replaced by new maintainers (apollo-bot). This is a strong signal of a potential package hijack and requires careful review.
This version was published by a different npm account than previous versions on 2019-05-07. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
3 findingsAll previous maintainers (mdg) were replaced by new maintainers (apollo-bot). This is a strong signal of a potential package hijack and requires careful review.
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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.