apollo-server-lambda
Production-ready Node.js GraphQL server for AWS Lambda
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decoding is standard AWS Lambda integration behavior — API Gateway sets isBase64Encoded for binary payloads; decoding before GraphQL processing is correct and expected for this package. | ai | |
| phantom-deps | phantom-dep:@types/aws-lambda | AI (phantom-deps): @types/aws-lambda is a TypeScript type definitions package used for compilation; not directly imported at runtime is normal for type-only packages. | ai |
Versions (showing 85 of 85)
| Version | Deps | Published |
|---|---|---|
| 3.13.0 | 5 / 1 | |
| 3.12.1 | 5 / 1 | |
| 3.12.0 | 5 / 1 | |
| 3.11.1 | 5 / 1 | |
| 3.11.0 | 5 / 1 | |
| 3.10.4 | 5 / 1 | |
| 3.10.3 | 5 / 1 | |
| 3.10.2 | 5 / 1 | |
| 3.10.1 | 5 / 1 | |
| 3.10.0 | 5 / 1 | |
| 3.9.0 | 5 / 1 | |
| 3.8.2 | 5 / 1 | |
| 3.8.1 | 5 / 1 | |
| 3.8.0 | 5 / 1 | |
| 3.7.0 | 5 / 1 | |
| 3.6.8 | 5 / 1 | |
| 3.6.7 | 5 / 1 | |
| 3.6.6 | 5 / 1 | |
| 3.6.5 | 5 / 1 | |
| 3.6.4 | 5 / 1 | |
| 3.6.3 | 5 / 1 | |
| 3.6.2 | 5 / 1 | |
| 3.6.1 | 5 / 1 | |
| 3.6.0 | 5 / 1 | |
| 3.5.0 | 5 / 1 | |
| 3.4.1 | 5 / 1 | |
| 3.4.0 | 5 / 1 | |
| 3.3.0 | 5 / 1 | |
| 3.2.0 | 5 / 1 | |
| 3.1.2 | 5 / 1 | |
| 3.1.1 | 5 / 1 | |
| 3.1.0 | 5 / 1 | |
| 3.0.2 | 5 / 1 | |
| 3.0.1 | 5 / 1 | |
| 3.0.0 | 5 / 1 | |
| 2.26.2 | 6 / 1 | |
| 2.26.1 | 6 / 1 | |
| 2.26.0 | 6 / 1 | |
| 2.25.4 | 6 / 1 | |
| 2.25.3 | 6 / 1 | |
| 2.25.2 | 6 / 1 | |
| 2.25.1 | 6 / 1 | |
| 2.25.0 | 6 / 1 | |
| 2.24.1 | 6 / 1 | |
| 2.24.0 | 6 / 1 | |
| 2.23.0 | 6 / 1 | |
| 2.22.2 | 6 / 1 | |
| 2.22.1 | 6 / 1 | |
| 2.22.0 | 6 / 1 | |
| 2.21.2 | 6 / 1 | |
| 2.21.1 | 6 / 1 | |
| 2.21.0 | 6 / 1 | |
| 2.20.0 | 6 / 1 | |
| 2.19.2 | 6 / 1 | |
| 2.19.1 | 6 / 1 | |
| 2.19.0 | 6 / 1 | |
| 2.18.2 | 6 / 1 | |
| 2.18.1 | 6 / 1 | |
| 2.18.0 | 6 / 1 | |
| 2.17.0 | 6 / 1 | |
| 2.16.1 | 6 / 1 | |
| 2.16.0 | 6 / 1 | |
| 2.15.1 | 6 / 1 | |
| 2.15.0 | 6 / 1 | |
| 2.14.5 | 6 / 1 | |
| 2.14.4 | 6 / 1 | |
| 2.14.3 | 6 / 1 | |
| 2.14.2 | 6 / 1 | |
| 1.4.0 | 2 / 3 | |
| 1.3.6 | 2 / 3 | |
| 1.3.5 | 2 / 3 | |
| 1.3.4 | 2 / 3 | |
| 1.3.3 | 2 / 3 | |
| 1.3.1 | 2 / 3 | |
| 1.3.0 | 2 / 3 | |
| 1.2.0 | 2 / 3 | |
| 1.1.7 | 2 / 3 | |
| 1.1.6 | 2 / 3 | |
| 1.1.5 | 2 / 3 | |
| 1.1.3 | 2 / 3 | |
| 1.1.2 | 2 / 3 | |
| 1.1.0 | 2 / 3 | |
| 1.0.5 | 2 / 3 | |
| 1.0.4 | 2 / 3 | |
| 1.0.2 | 2 / 3 |
v3.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.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.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
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.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
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.26.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.26.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.19.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.19.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.18.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.18.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.14.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.14.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.14.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.14.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.