apollo-engine-reporting
Send reports about your GraphQL services to Apollo Graph Manager (previously known as Apollo Engine)
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 |
|---|---|---|---|---|
| semgrep | semgrep:hex-decode | AI (semgrep): The hex decode is part of GraphQL query signature normalization — converting hex-encoded string literals back to UTF-8 for readability. No malicious payload; stable false positive for this package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established Apollo GraphQL package from the official mdg publisher org. Short README and missing keywords are cosmetic issues, not spam indicators. | ai |
Versions (showing 60 of 60)
| Version | Deps | Published |
|---|---|---|
| 2.3.0 | 9 / 0 | |
| 2.2.1 | 9 / 0 | |
| 2.2.0 | 9 / 0 | |
| 2.1.0 | 9 / 0 | |
| 2.0.1 | 9 / 0 | |
| 2.0.0 | 9 / 0 | |
| 1.8.0 | 8 / 0 | |
| 1.7.1 | 8 / 0 | |
| 1.7.0 | 8 / 0 | |
| 1.6.0 | 8 / 0 | |
| 1.5.0 | 8 / 0 | |
| 1.4.14 | 8 / 0 | |
| 1.4.13 | 8 / 0 | |
| 1.4.12 | 7 / 0 | |
| 1.4.11 | 7 / 0 | |
| 1.4.10 | 7 / 0 | |
| 1.4.9 | 7 / 0 | |
| 1.4.8 | 7 / 0 | |
| 1.4.7 | 7 / 0 | |
| 1.4.6 | 7 / 0 | |
| 1.4.5 | 7 / 0 | |
| 1.4.4 | 7 / 0 | |
| 1.4.3 | 7 / 0 | |
| 1.4.2 | 6 / 0 | |
| 1.4.1 | 6 / 0 | |
| 1.4.0 | 6 / 0 | |
| 1.3.6 | 6 / 0 | |
| 1.3.5 | 6 / 0 | |
| 1.3.4 | 6 / 0 | |
| 1.3.3 | 6 / 0 | |
| 1.3.2 | 6 / 0 | |
| 1.3.1 | 6 / 0 | |
| 1.3.0 | 6 / 0 | |
| 1.2.1 | 6 / 0 | |
| 1.2.0 | 6 / 0 | |
| 1.1.1 | 6 / 0 | |
| 1.1.0 | 6 / 0 | |
| 1.0.7 | 6 / 0 | |
| 1.0.6 | 6 / 0 | |
| 1.0.5 | 6 / 0 | |
| 1.0.4 | 6 / 0 | |
| 1.0.3 | 6 / 0 | |
| 1.0.2 | 6 / 0 | |
| 1.0.1 | 6 / 0 | |
| 1.0.0 | 6 / 0 | |
| 0.2.2 | 6 / 0 | |
| 0.2.1 | 5 / 0 | |
| 0.2.0 | 5 / 0 | |
| 0.1.4 | 5 / 0 | |
| 0.1.3 | 5 / 0 | |
| 0.1.2 | 5 / 0 | |
| 0.1.1 | 5 / 0 | |
| 0.1.0 | 5 / 0 | |
| 0.0.6 | 5 / 0 | |
| 0.0.5 | 5 / 0 | |
| 0.0.4 | 5 / 0 | |
| 0.0.3 | 5 / 0 | |
| 0.0.2 | 5 / 0 | |
| 0.0.1 | 5 / 0 | |
| 0.0.0 | 5 / 10 |
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
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. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.